Hi all,
The issue is this:
While the WKT attribute of an arcgis.geometry.Geometry object returns me WKT geometry in this format: (for instance)
MULTIPOLYGON (((30, 20), (45, 40), (10, 40), (30, 20)),((15, 5), (40, 10), (10, 20), (5, 10), (15, 5)))<SPAN class="line-numbers-rows"><SPAN></SPAN></SPAN>
An OGC WKT string for the same geometry would look so:
MULTIPOLYGON (((30 20, 45 40, 10 40, 30 20)),((15 5, 40 10, 10 20, 5 10, 15 5)))<SPAN class="line-numbers-rows"><SPAN></SPAN></SPAN>
This, in my opinion, diminishes the usability of the WKT object. For instance, if I want to write this to a database in the database's native geometry data type, I cannot use methods that convert WKT to Geometry (like STAsText in MS SQL Server), as they will be expecting the data to be in OGC WKT format.
The questions are, hence,
- why does the arcgis.geometry.Geometry.WKT object not have the format specified in OGC specification for WKT representation?
- will this behaviour be changed, at all, to conform to the said standards in the future releases of ArcGIS API for Python?
