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
I do suggest the following change in forEachTriange (the version on the website does only provide one coordinate (and even the wrong one), this version returns both x and y coordinates:
Oh, yes, this is an issue but not sure what I should do about it — if you store points as nested [[x0,y0], [x1,y1], [x2,y2], …] then the helper code you need will be different than if you store the flat version [x0, y0, x1, y1, x2, y2, …]. Right now the guide is written for the nested point structure.
Hi Mapbox maintainer,
Thanks,
I did not consider the point of view you made in your mail.
But I started with the example in the README.md of your GitHub page, where
you give a no-nested example as a first start.
It may be an idea to make both consistent?
Anyhow: thanks for your swift answer,
Greetings from a misty and grey Netherlands,
Paul Torfs
I do suggest the following change in forEachTriange (the version on the website does only provide one coordinate (and even the wrong one), this version returns both x and y coordinates:
The text was updated successfully, but these errors were encountered: