Fix empty point behaviour in wkb, ewkb, and hexewkb formats #187
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.
Issue
When loading an empty point geometry encoded in one of the above formats, the coordinate doubles unpacked in
WKB.class#getPointare bothNANBecause of the
NANvalues, the empty point is able to bypass the safeguards in thePoint.classconstructor.This results in an invalid
Pointobject, where$point->isEmpty()is false.Observations
Postgres seems to implicitly encode
POINT EMPTYasPOINT(NAN, NAN), and by default returns the hexewkb representation.Postgres:
Verifying in PHP:
Problems
1. Reading the above empty point binary with
GeoPhp:2. Empty Point binary output representation is invalid.
Solutions
is_nanin thePoint.classconstructor and create an empty point in that case.*Note: this solution works for empty point geometries with different srid's as well.