Skip to content
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

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

Open
markfarrell opened this issue Apr 27, 2015 · 1 comment
Open

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

markfarrell opened this issue Apr 27, 2015 · 1 comment
Labels

Comments

@markfarrell
Copy link
Member

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.

@rwarren2
Copy link
Contributor

That's a reasonable thing to do for the moment, through later I would rather use a geosparql approach.

Think of this as making multiple passes on the data;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants