You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 11, 2024. It is now read-only.
From user Fabien:
I wanted to give you some feedback by importance order for the tool :
could it be possible to add a step to request the sensor's type (thermometer...)
adding observations for several observed property (different sensor) doesn't work yet (but I think you know it as I saw it in code comment). It will only need to repeat some steps for each sensor/observed property like requesting sensor name, observed property and uom
for the unit of measure (step 6b), using '²' character causes an UTF8-error (added SOS log in attachment)
could the configuration file be applied to a fileset, for example I got 30 files for a mounth which only vary on the date. By setting a shortcut to the last step and only request a csv file and a config-file.xml or setting at first step a multiple target
Less important feedbacks :
append an other step for asking the user if he wants to add metadata which could be used in the client (like quality of the sensor, owner ...) with
could the tool be a little more connected by requesting first url of the SOS, for parsing throught the GetCapabilities, which FOI, procedures and unit of measure already exist to avoid misspelling
could the policy when a file already been read be less strict, because it needs to rename the file if you want to use it again when you got an error while feeding (skip lines but data haven't been yet inserted in the database)"
From user Fabien:
I wanted to give you some feedback by importance order for the tool :
Less important feedbacks :
for having a complete client as on http://sensorweb.demo.52north.org/sensorwebclient-webapp-stable/, when you click on a station provided by Pegelonline you got the river name for example which is set on the sensorML.
The text was updated successfully, but these errors were encountered: