search

arthur-e / Wicket

A modest library for moving between Well-Known Text (WKT) and various framework geometries
https://arthur-e.github.io/Wicket/
Other
586 stars 226 forks source link

Gmap: Ring orientation problem #120

Closed BHare1985 closed 6 years ago

BHare1985 commented 6 years ago

The WKT spec cares about ring orientation and Wicket is incorrectly ordering the points from google maps.

See more about this issue here: https://stackoverflow.com/questions/48305408/sql-server-geography-polygon-is-inverse-of-wkt-srid-4326

BHare1985 commented 6 years ago

Seems related to https://github.com/arthur-e/Wicket/issues/33 -- I commented on this bug almost 2 years ago. I was expecting this to be fixed, so I am pretty sure its related.

arthur-e commented 6 years ago

The WKT string test cases are now correctly defined (see our correspondence in #33 from May 2016). However, last I checked, the Google Maps API does not provide tools for interrogating the ring orientation of existing Google Maps API objects, which means that Wicket can't distinguish between MULTIPOLYGONS with and without holes nor between MULTIPOLYGONS of any sort and POLYGONS with holes. I welcome pull requests to fix this!

arthur-e commented 6 years ago

I believe this has been fixed in #127. Let me know if that's not the case.