We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This WKT parse and output is unexpected:
$ ./bin/geosop -a "MULTIPOINT ZM (0 0 4 3, 1 2 4 5)" -f wkt MULTIPOINT Z (0 0 4, 1 2 4)
The expected result is created with:
$ ./bin/geosop -a "MULTIPOINT ZM ((0 0 4 3), (1 2 4 5))" -f wkt MULTIPOINT ZM (0 0 4 3, 1 2 4 5)
This means than WKT does not round-trip:
$ ./bin/geosop -a "MULTIPOINT ZM ((0 0 4 3), (1 2 4 5))" -f wkt | ./bin/geosop -a stdin -f wkt MULTIPOINT Z (0 0 4, 1 2 4)
WKB seems to round-trip OK:
$ ./bin/geosop -a "MULTIPOINT ZM ((0 0 4 3), (1 2 4 5))" -f wkb | ./bin/geosop -a stdin.wkb -f wkt MULTIPOINT ZM (0 0 4 3, 1 2 4 5)
The text was updated successfully, but these errors were encountered:
Similar with MultiPoint M:
$ ./bin/geosop -a "MULTIPOINT M (0 0 3, 1 2 5)" -f wkt MULTIPOINT (0 0, 1 2) $ ./bin/geosop -a "MULTIPOINT M ((0 0 3), (1 2 5))" -f wkt MULTIPOINT M (0 0 3, 1 2 5)
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
This WKT parse and output is unexpected:
$ ./bin/geosop -a "MULTIPOINT ZM (0 0 4 3, 1 2 4 5)" -f wkt MULTIPOINT Z (0 0 4, 1 2 4)
The expected result is created with:
$ ./bin/geosop -a "MULTIPOINT ZM ((0 0 4 3), (1 2 4 5))" -f wkt MULTIPOINT ZM (0 0 4 3, 1 2 4 5)
This means than WKT does not round-trip:
WKB seems to round-trip OK:
The text was updated successfully, but these errors were encountered: