Description
When working with a network that uses Swiss LV95 coordinates (EPSG:2056, open in the new ui inp file from epanet 2.2),
saving the project causes the map view to become corrupted: all nodes
appear scattered across the entire world map instead of showing the
correct local network layout.
Steps to reproduce
- Open an .inp file containing LV95 coordinates (large values, e.g. Easting ~2,600,000 / Northing ~1,200,000)
- When prompted for the coordinate reference system, select/enter
EPSG:2056
- The network and map displays correctly, editing works fine
- Make an edit and click Save
- Click or scroll on the map
Actual result
The network appears torn apart / scattered across the entire world map (after click or scroll --> jumps away).
The map view becomes unusable and I cannot continue working in the same
session.
Expected result
The map should remain correctly georeferenced after saving, without
requiring the file to be closed and reopened.
Important note
The underlying .inp file itself is NOT corrupted. All coordinates and
edits are saved correctly - I verified this by inspecting the
[COORDINATES] section in a text editor and by closing and reopening the
file (re-entering EPSG:2056 on open restores the correct map view).
This appears to be a session/CRS-state bug in the map rendering after
Save, not a data integrity issue (due to the little network need after open - zoom a bit out).
Suspected cause (not confirmed)
Possibly the coordinate reference system context (EPSG:2056) selected
on file open is not being retained by the map/basemap component after
Save, causing it to fall back to a default projection (e.g. WGS84) and
misinterpret the large LV95 values as lat/lon degrees.
Workaround
Close and reopen the file (re-entering EPSG:2056) after every save.
Environment
- OS: Windows 11
- EPANET-UI version: 1.0.2
- Coordinate system: EPSG:2056 (Swiss LV95)
Test files
Export from Epanet 2.2 for importing in new ui (saved as .txt - .inp upload not allowed):
test_0.txt
Saved file from new ui (saved as .txt - .inp upload not allowed):
test_1.txt
Description
When working with a network that uses Swiss LV95 coordinates (EPSG:2056, open in the new ui inp file from epanet 2.2),
saving the project causes the map view to become corrupted: all nodes
appear scattered across the entire world map instead of showing the
correct local network layout.
Steps to reproduce
EPSG:2056
Actual result
The network appears torn apart / scattered across the entire world map (after click or scroll --> jumps away).
The map view becomes unusable and I cannot continue working in the same
session.
Expected result
The map should remain correctly georeferenced after saving, without
requiring the file to be closed and reopened.
Important note
The underlying .inp file itself is NOT corrupted. All coordinates and
edits are saved correctly - I verified this by inspecting the
[COORDINATES] section in a text editor and by closing and reopening the
file (re-entering EPSG:2056 on open restores the correct map view).
This appears to be a session/CRS-state bug in the map rendering after
Save, not a data integrity issue (due to the little network need after open - zoom a bit out).
Suspected cause (not confirmed)
Possibly the coordinate reference system context (EPSG:2056) selected
on file open is not being retained by the map/basemap component after
Save, causing it to fall back to a default projection (e.g. WGS84) and
misinterpret the large LV95 values as lat/lon degrees.
Workaround
Close and reopen the file (re-entering EPSG:2056) after every save.
Environment
Test files
Export from Epanet 2.2 for importing in new ui (saved as .txt - .inp upload not allowed):
test_0.txt
Saved file from new ui (saved as .txt - .inp upload not allowed):
test_1.txt