Skip to content

Clean up geospatial information and sensor metadata ... #99

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dlebauer opened this issue Nov 16, 2016 · 8 comments
Closed

Clean up geospatial information and sensor metadata ... #99

dlebauer opened this issue Nov 16, 2016 · 8 comments
Assignees
Milestone

Comments

@dlebauer
Copy link
Member

dlebauer commented Nov 16, 2016

This page seems to confound geospatial information and sensor metadata:

https://terraref.gitbooks.io/terraref-documentation/content/user/geospatial-information.html

needs to be separated, and aimed at end users


Use cases for such documentation:

  • how can a robot operator specify their metadata?: (moved from Use case: how should my sensor write out metadata?  sensor-metadata#3)
    • the terraref/sensor-metadata repository has information about the sensor fixed metadata that overlaps with the above documentation
    • But it isn't clear how someone with a new sensor (and sensor platform, e.g. a robot) can specify their metadata.
    • Some additional fields: latitude, longitude, time, velocity (x, y, z), pitch, roll ...
  • what is required
    • to insert this metadata into Clowder?
    • to extract these metadata and do a geospatial join with sites (plots) in BETYdb
@craig-willis
Copy link
Contributor

It looks like we should add some of this information to the gantry fixed metadata:

@ghost ghost assigned max-zilla Jan 19, 2017
@ghost
Copy link

ghost commented Jan 19, 2017

Have Geo extractor feed to geostream dataset

@ghost
Copy link

ghost commented Feb 9, 2017

right now we have met data w/ time series. can also add to canopy cover/height

@max-zilla
Copy link
Contributor

I've started adding geostreams API support to pyclowder2:
https://opensource.ncsa.illinois.edu/bitbucket/projects/CATS/repos/pyclowder2/browse/pyclowder/geostreams.py

This means any extractor can pull geolocation form metadata and:

  • query plots to find nearest one to that point
  • push datapoint w/ any values to the correct plot/stream
  • query by radius, polygon, or (less often) plot name

@ghost ghost removed the help wanted label Feb 23, 2017
@max-zilla max-zilla added this to the March 2017 milestone Mar 8, 2017
@max-zilla
Copy link
Contributor

Document to track this effort here:
https://docs.google.com/spreadsheets/d/117n1gOWpiMoXFGWNeYCeI-J1VzSwIwG2uSJcNIFhcRg/edit?usp=sharing

Getting there.

@max-zilla
Copy link
Contributor

@craig-willis and I have been in discussions in pursuit of this, including how the format of these metadata influence the type of faceted searches we can support.

@ghost
Copy link

ghost commented May 17, 2017

@craig-willis - can this issue be closed?

@max-zilla
Copy link
Contributor

This is being implemented in TERRAutils. we are defining these 'cleaned up' outputs but I don't think we can close yet.

@ghost ghost removed the help wanted label May 25, 2017
@ghost ghost modified the milestones: June 2017, March 2017 May 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants