You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use wkx to validate and parse WKX strings coming as variables in HTTP requests.
We've noticed that it validates the general structure of the WKT when parsing but doesn't validate the numbers.
For example, wkx.Geometry.parse("POINTTTT(1 2)") will fail because there is no POINTTTT in WKT.
But, parsing wkx.Geometry.parse("POINT(a b)") will not fail, instead it will return a point with NaN for numbers:
We use
wkx
to validate and parse WKX strings coming as variables in HTTP requests.We've noticed that it validates the general structure of the WKT when parsing but doesn't validate the numbers.
For example,
wkx.Geometry.parse("POINTTTT(1 2)")
will fail because there is noPOINTTTT
in WKT.But, parsing
wkx.Geometry.parse("POINT(a b)")
will not fail, instead it will return a point with NaN for numbers:The text was updated successfully, but these errors were encountered: