Skip to content
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

reading dfs2 with local coordinates: coordinates in ds.geometry wrong when #538

Closed
Snowthe opened this issue Jan 20, 2023 · 2 comments
Closed
Labels
duplicate This issue or pull request already exists

Comments

@Snowthe
Copy link

Snowthe commented Jan 20, 2023

When reading a dfs2 file, the ds.geometry.x and .y and .coordinates arrays of grid coordinates is wrong, whereas the rest of the information (dx, dy, origin, etc.) seems correct

To Reproduce
I only tried with a dfs2 file with "Local coordinates" which in fact are some UTM projected coordinates.

ds = mikeio.read('file.dfs2')
ds.geometry.coordinates
ds.geometry.origin

Expected behavior
ds.geometry.coordinates should show corner coordinates as in .origin. However, .coordinates shows values that seem to be exactly twice the correct values; .origin is correct.
This also affects subsequent use of ds.interp() etc.

System information:

  • python 3.8.11
  • MIKE IO 1.3.1
@Snowthe
Copy link
Author

Snowthe commented Jan 25, 2023

This actually is a duplicate of this issue here: #540 and can be closed.
Sorry for the confusion.

@jsmariegaard jsmariegaard added the duplicate This issue or pull request already exists label Jan 30, 2023
@jsmariegaard
Copy link
Member

Closed by #544

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants