In the current state of the application, when a jsondbk contains invalid geometries:
Printing fails.
Click feature info fails.
In my opinion, the queries that bring the data to the viewer should all have a postgis ST_IsValid check built in so the wrong geometries stay behind. Solving the invalid geometries is a matter of the creating application, not the viewer.
In the current state of the application, when a jsondbk contains invalid geometries:
In my opinion, the queries that bring the data to the viewer should all have a postgis ST_IsValid check built in so the wrong geometries stay behind. Solving the invalid geometries is a matter of the creating application, not the viewer.