muninn/elevation-spec

Software specification for our elevation service.

elevation-spec's Issues

Integrate the Canadian elevation data API

http://geogratis.gc.ca/site/eng/elevation

RDF and N3 format examples?

What should the response look like when rdf or n3 are selected as formats in a request?

Integrate NYC DEM into data

https://data.cityofnewyork.us/City-Government/1-foot-Digital-Elevation-Model-DEM-/dpc8-z3jc

Tempted to create a void record for this for provenance purposes that lists the original location of the dem.

Use PostGIS if we're still able to adjust scale?

I'd recommend using PostgreSQL/PostGIS, taking elevation data from all of those data sources, massaging the data and storing it all in a spatial table of points. We could even include the original data source as a feature of each of the points, as well as the publication date of the data source, useful for doing provenance. We'd basically then have just have a CGI script that queries our geospatial database for all of the points inside of a requested bounding box and serializes the result set of points in a requested format. But my concern is that we would not be able to set the distance in metres between points, the scale parameter in our requests, should we choose to do this. I don't believe this is possible with PostGIS, unless I'm mistaken.

Example of RDF provenance information for data source?

Provide an example of RDF provenance information being provided for a data source?

Minimum and maximum scale?

Should we have a range of valid scale values for the scale parameter, e.g. 1-90?

Integrate Nova Scotia elevation data

This may require a little bit more conversion work:
http://novascotia.ca/natr/meb/download/dp055.asp

What permanent metadata should hang off the endpoint http://.../about?

What permanent metadata should hang off the endpoint http://.../about?