-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
problem with x and y when reading dfs2 files from MikeShe with MIKE IO #540
Comments
Why is the projection: NON-UTM? |
It is intensional that the x-coordinate vector starts in x0 + origin[0]. In most cases, x0 will be zero. |
The problem is that the 2D x and y are wrong when reading with MikeIO (mikeio.read()) Tuse_aa_50m_cal_3DSZ.dfs3.txt |
[I'm a colleague of tad9876 also familiar with the issue] So that means that we are defining the coordinate systems wrong in our setups? The mentioned issue occurs with result files from MIKE SHE; not with dfs2 files that we create ourselves from scrartch via mikeio or similar. In the MIKE SHE setup (Model Domain and Grid), we usually just use "Local coordinates" as a map projection type (even though it most often is ETRS89 UTM32N we do not specify this there), and define a catchment origin X0 and Y0 (together with the rest, i.e. NX, NY, cell size).
I was not able to understand what is going on here from the manual - are you able to help? |
Thanks, Jesper. |
closed by #544 |
Describe the bug
When reading an dfs2 file dataset.geometry.origin is not the same as dataset.geometry.xy[0]. Actually dataset.geometry.xy[0] is exactly double of the origin.
dataset.geometry.xy
datase.geometry._xx
dataset.geometry._yy
is wrong
while;
dataset.geometry.dx
dataset.geometry.dy
dataset.geometry.nx
dataset.geometry.ny
datase.geometry._x0
dataset.geometry._y0
all seems right
Screenshots
System information:
The text was updated successfully, but these errors were encountered: