Fix #184 #185 and add support for && in postgis + few other small things #186
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
…_pt. These functions does NOT exist in MySQL. Moved INSTALL.md to doc/configuration.md. Both contained redundant information. Added workaround functions geometry_overlaps, geography_overlaps to be able to use && operator in PostGIS.
This was referenced Nov 25, 2017
1 similar comment
…tput for Point type
|
I added toGeoJSON() function to abstract point... I only investigated Point type so if I ever use other types I can add them too. |
2 similar comments
1 similar comment
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.
…_pt. These functions does NOT exist in MySQL. Moved INSTALL.md to doc/configuration.md. Both contained redundant information. Added workaround functions geometry_overlaps, geography_overlaps to be able to use && operator in PostGIS.
Changed ArithmeticPrimary() to ArithmeticFactor() because most inputs may have negative/positive signs and ArithmeticPrimary() does not take this into consideration. See EBNF Arithmetic Expressions.