I wonder if this could remain a useful fallback in the event that the CRS is not defined in CoordRefSystems
- perhaps generating a simple warning rather than an error. This way, users like me (prior to this thread) could continue to work in their use case, just without the added functions the update brings.
That was actually our fault, sorry. Fixed the issue and released a patch:
We are trying to write useful error messages so that users can contribute the CRSs that are missing. We prefer to deal with it as a serious error, instead of a warning.
1 Like
Tried with your shapefile and it is working again:
Now with the correct shifted TransverseMercator CRS.
1 Like
6 posts were split to a new topic: Troubles with GeoStats/GeoIO coordinates with units