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

Access to OSMLR segment geometries #2

Closed
drewda opened this issue Mar 8, 2017 · 3 comments
Closed

Access to OSMLR segment geometries #2

drewda opened this issue Mar 8, 2017 · 3 comments
Assignees

Comments

@drewda
Copy link
Contributor

drewda commented Mar 8, 2017

The OSMLR generator application generates geometries for each OSMLR segment as GeoJSON tiles. The Datastore will need to have access to these geometries in some form in order to respond to API queries for network statistics ( #1 ).

First, Datastore will need to be able to look up segments by bounding box. Second, Datastore will need to include geometries for the appropriate segments in API response.

//cc @kevinkreiser please edit or expand as you see fit!

@drewda
Copy link
Contributor Author

drewda commented Mar 8, 2017

OSMLR GeoJSON tiles are unprojected. On the other hand, this API will be powering a Leaflet "slippy map" interface. Should bounding box query parameters and geometry responses be projected into Web Mercator?

@kevinkreiser
Copy link
Contributor

my opinion is that if we support mercator, we do it through standard tilespec queries, so someone would ask for tile x/y/z and we'd convert that to a bbox, get the features intersected as normal but reproject their geoms and clip them to the mercator bounds before returning them

@drewda
Copy link
Contributor Author

drewda commented Mar 27, 2017

Closed by #3 ?

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

2 participants