Project

General

Profile

Bug #5116

add lat/lon to sensor metadata and use during import

Added by Daniel Crawl about 9 years ago. Updated over 8 years ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
sensor-view
Target version:
Start date:
08/02/2010
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5116

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

History

#1 Updated by Matt Jones about 9 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.

#2 Updated by Daniel Crawl almost 9 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.

#3 Updated by Daniel Crawl almost 9 years ago

Check for altitude metadata; if not there add it.

#4 Updated by Derik Barseghian over 8 years ago

changing bugs from REAP to Kepler product

#5 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 5116

Also available in: Atom PDF