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.

Sign up for GitHub

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

Jump to bottom

queryForGeoJSONFeaturesInTable should not assume the bounding box is 4326 #140

Open
danielbarela opened this issue Jan 16, 2020 · 0 comments
Open

queryForGeoJSONFeaturesInTable should not assume the bounding box is 4326 #140

danielbarela opened this issue Jan 16, 2020 · 0 comments

Comments

@danielbarela
Copy link
Member

The queryForGeoJSONFeaturesInTable should not assume that the projection is in 4326 especially if the FeatureDao projection is different. The projection should be optionally passed in. The projection could also potentially be included in the BoundingBox class which is returned from the FeatureDao.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@danielbarela