-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wkt.fromObject() fails for POLYGON or MULTIPOLYGON #135
Comments
@chmelej seems wicket-leaflet uses the old format of getLatLngs() As a workaround, you could do something like:
|
@scottlepp Thanks for figuring this out! Could you fix this in a Pull Request? |
#135 leaflet 1.x getLatLng() now returns an array of arrays of coord…
Hi,
... returns
thank you |
@destus90 Oops, the version number in |
Still seems not to work for multipolygons or polygons with holes. The following hack-round seems to have dealt with this temporarily, for the purposes of creating a WKT string, and may (perhaps?) be helpful to others and/or provide some hints as to what's up:
|
Hi I have an example:
the polygon appears on the map but alert is triggered:
which is wrong :-(
I use a latest version of wicket.js, wicket-leaflet.js and leaflet.js 1.4.0
What am I doing wrong?
Thanks.
The text was updated successfully, but these errors were encountered: