Handling of Z and/or M values by WKTShapeParser

[sibartlett]

WKTShapeParsers should be able to read WKT strings that contain:

• Z and/or M values
• optional Z/M/ZM flags (as defined by the latest OGC Simple Feature Access specification)

At present I have no requirement for the Z and M values to be used - they can be discarded.

[sibartlett]

FYI I have written a class for RavenDB which removes the Z and M dimensions from WKT strings, using regex, before passing them to spatial4n/NTS. This allows users to store 3D/4D shapes in RavenDB, but still be able to index and query them.

https://github.com/sibartlett/ravendb/blob/spatial/Raven.Abstractions/Spatial/WktSanitizer.cs

[dsmiley]

Ok, thanks. When I get back into Spatial4j in the near future, I'll address this since the WKT parser is the top priority of Spatial4j things.

On Fri, Mar 15, 2013 at 10:28 AM, Simon Bartlett notifications@github.comwrote:

FYI I have written a class for RavenDB which removes the Z and M dimensions from WKT strings, using regex, before passing them to spatial4n/NTS. This allows users to store 3D/4D shapes in RavenDB, but still be able to index and query them.

https://github.com/sibartlett/ravendb/blob/spatial/Raven.Abstractions/Spatial/WktSanitizer.cs

— Reply to this email directly or view it on GitHubhttps://github.com/spatial4j/spatial4j/issues/35#issuecomment-14963494 .

[dsmiley]

Closed via https://github.com/spatial4j/spatial4j/commit/88fe0e9c49f15cef1c9d29d9a947914a5c8ae644

The dimensionality is parsed and totally ignored.