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
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: