Open brucecrevensten opened 2 years ago
If we fix #92 that would make it so that all polygons are limited to the following extent:
{'minx': -178.225139,
'miny': 51.34921302,
'maxx': 179.7607474,
'maxy': 71.3907203}
And so that fix may partly address this issue. Changing the actual coordinates of the polygon vertices could have some consequences for how data is retrieved via the API and for whether or not the geometries are valid. It could also create issues where vertices are no longer within the bounds of the desired CRS which could make the API fall over.
The polygons as they are now are geographically and geometrically sound, so my instinct is to let them be (but address #92) and if there are remaining rendering issues to either address them on the client and/or supply the app with a custom, local, copy of the polygons that are failing to render properly to use for visualization.
Right now we've got code in the client app that adjusts points that are west of the antemeridian (i.e. 175 becomes -185) but could/should that be done on this end, not in the client?