Allow pg source to perform the coordinate transformation/projection #117
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…rmation/projection
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently hakunapi handles all coordinate transformations inside Java code. While this is originally by-design (when the amount of calculation doesn't change, do it in application level instead of db) some might prefer postgis handle them for you (for precision etc).
This is also a step towards dropping
hakunapi-proj-gtfrom .war files generated byhakunapi-simple-webapp-*projects for smaller war packages and startup time.This partially handles #58 as all geometries in Filters are still transformed to storage SRID by hakunapi itself. Changing that in the future shouldn't be a big deal.