Mechanism to manage non-standardized prj file #1312
Merged
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
…patialref_mecanism
…o import a geospatial file in H2GIS
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.
This PR adds a new mechanism to manage a prj that doesn't contain any EPSG authority code.
When a prj file doesn't contain any EPSG code, we read the prj and if the prj is valid we generate a default srid value.
The new srid value and prj information's are stored on a temporary table available for the current connection. The table is named USER_SPATIAL_REF_SYS.
The ST_Transform function has been updated to look in to USER_SPATIAL_REF_SYS when the SRID value is missing in the SPATIAL_REF_SYS.