Bug #5116
openadd lat/lon to sensor metadata and use during import
0%
Description
The site layout in engineering workflows can reflect the physical layout of sensors at a deployment site. If lat/lon metadata were stored on the sensor server, this location information could be used when importing a workflow into Kepler.
The tasks for this bug are:
1. see if SPAN allows lat/lon metadata per sensor
2. if not, try to add it
3. use lat/lon metadata during import
Updated by Matt Jones over 14 years ago
Ilkay's work on metadata also indicated this information might be present in the SensorML metadata or EML metadata -- so you might be able to get it from there.
Updated by Daniel Crawl about 14 years ago
I've updated the SPAN software to allow getting and setting lat/lon per sensor.
I also added lat/lon parameters the sensor simulator.
To close this bug, the lat/lon values need to be used to place the sensors on the canvas when importing a site.
Updated by Daniel Crawl about 14 years ago
Check for altitude metadata; if not there add it.
Updated by Derik Barseghian almost 14 years ago
changing bugs from REAP to Kepler product