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
The GeoJSON spec says that polygons should be counter clock wise (more info here).
We currently don't enforce this.
When a polygon is saved as clock wise, edited in a GeoJSON tool (like geojson.io) and imported back in the database, the polygon coordinates are changed although the polygon is essentially the same => this creates noise (which is especially visible in the import UI).
Solution: ensure polygons are counter clock wise for the Boulder model.
Previous attempt: 39cc8e6
=> let's make the code simpler / test it, or just wait for rgeo to support the feature out of the box.
The GeoJSON spec says that polygons should be counter clock wise (more info here).
We currently don't enforce this.
When a polygon is saved as clock wise, edited in a GeoJSON tool (like geojson.io) and imported back in the database, the polygon coordinates are changed although the polygon is essentially the same => this creates noise (which is especially visible in the import UI).
Solution: ensure polygons are counter clock wise for the
Boulder
model.Previous attempt: 39cc8e6
=> let's make the code simpler / test it, or just wait for rgeo to support the feature out of the box.
In the meantime we can run this query:
The text was updated successfully, but these errors were encountered: