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
Currently when user sends data file and tells him it's in EPSG:4326, but the file coordinates are in EPSG:5514, it ends up in nonsense extent and geometry coordinates that partially breaks database and partially GeoServer and therefore also Layman. Solution could be to detect such conflict in advance.
The text was updated successfully, but these errors were encountered:
Currently when user sends data file and tells him it's in EPSG:4326, but the file coordinates are in EPSG:5514, it ends up in nonsense extent and geometry coordinates that partially breaks database and partially GeoServer and therefore also Layman. Solution could be to detect such conflict in advance.
The text was updated successfully, but these errors were encountered: