{"action":"created","issue":{"url":"https://api.github.com/repos/pyugrid/pyugrid/issues/145","repository_url":"https://api.github.com/repos/pyugrid/pyugrid","labels_url":"https://api.github.com/repos/pyugrid/pyugrid/issues/145/labels{/name}","comments_url":"https://api.github.com/repos/pyugrid/pyugrid/issues/145/comments","events_url":"https://api.github.com/repos/pyugrid/pyugrid/issues/145/events","html_url":"https://github.com/pyugrid/pyugrid/issues/145","id":180944182,"number":145,"title":"Support in pyugrid for node_coordinates other than latitude and longitude","user":{"login":"bhlevca","id":182494,"avatar_url":"https://avatars.githubusercontent.com/u/182494?v=3","gravatar_id":"","url":"https://api.github.com/users/bhlevca","html_url":"https://github.com/bhlevca","followers_url":"https://api.github.com/users/bhlevca/followers","following_url":"https://api.github.com/users/bhlevca/following{/other_user}","gists_url":"https://api.github.com/users/bhlevca/gists{/gist_id}","starred_url":"https://api.github.com/users/bhlevca/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bhlevca/subscriptions","organizations_url":"https://api.github.com/users/bhlevca/orgs","repos_url":"https://api.github.com/users/bhlevca/repos","events_url":"https://api.github.com/users/bhlevca/events{/privacy}","received_events_url":"https://api.github.com/users/bhlevca/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":12,"created_at":"2016-10-04T16:38:50Z","updated_at":"2016-10-04T20:13:34Z","closed_at":null,"body":"Hello,\r\n\r\nI am working on a project to bring Python post processing tools to \r\n[Delft3D-FM ](https://www.deltares.nl/en/software/delft3d-flexible-mesh-suite/), which will be part of the Open Source effort of the [Open Earth Tools](https://publicwiki.deltares.nl/display/OET/OpenEarth). \r\n\r\nI am not affiliated with Deltares, but I am a Python proponent and I am helping them out and integrating it into my preferred tools. \r\n\r\nI am using pyugrid for the map files and so far it is working great except two things:\r\n\r\n1. triangular cells only (but I create triangular meshes only at the moment so I am OK, but I hope for support for other shapes in the near future)\r\n2.  pyugrid requires \"latitude\" and \"longitude\" as coord_vars, thus grids with UTM coordinates are throwing an exception. I worked around this issue by subclassing pugrid.UGrid and 2 mehtods from red_netcdf.\r\n\r\nPerhaps issue 1 is harder to implement, but the second one may be worth while to consider addressing, I am passing along Deltares' request: \r\n         \r\n> The UGRID conventions document does NOT require the use of latitude longitude, see:\r\n> [UGRID conventions](http://ugrid-conventions.github.io/ugrid-conventions/#ugrid-conventions-v10)\r\n>\r\n> go to : “(latitude, longitude, and optional elevation or other coordinates)”\r\n> Any requirement of lat/lon comes from CF conventions (which UGRID will often be combined with, of course).\r\n> \r\n> ·As such, the lat/lon checking should not be a required/blocking part of the pyugrid code.\r\n> An idea could be to make the CF-checking in pyugrid configurable optional, or remove it altogether.\r\n\r\n Please let me know what you think.\r\n\r\nThanks\r\nBogdan\r\n"},"comment":{"url":"https://api.github.com/repos/pyugrid/pyugrid/issues/comments/251499402","html_url":"https://github.com/pyugrid/pyugrid/issues/145#issuecomment-251499402","issue_url":"https://api.github.com/repos/pyugrid/pyugrid/issues/145","id":251499402,"user":{"login":"ChrisBarker-NOAA","id":916576,"avatar_url":"https://avatars.githubusercontent.com/u/916576?v=3","gravatar_id":"","url":"https://api.github.com/users/ChrisBarker-NOAA","html_url":"https://github.com/ChrisBarker-NOAA","followers_url":"https://api.github.com/users/ChrisBarker-NOAA/followers","following_url":"https://api.github.com/users/ChrisBarker-NOAA/following{/other_user}","gists_url":"https://api.github.com/users/ChrisBarker-NOAA/gists{/gist_id}","starred_url":"https://api.github.com/users/ChrisBarker-NOAA/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ChrisBarker-NOAA/subscriptions","organizations_url":"https://api.github.com/users/ChrisBarker-NOAA/orgs","repos_url":"https://api.github.com/users/ChrisBarker-NOAA/repos","events_url":"https://api.github.com/users/ChrisBarker-NOAA/events{/privacy}","received_events_url":"https://api.github.com/users/ChrisBarker-NOAA/received_events","type":"User","site_admin":false},"created_at":"2016-10-04T20:13:34Z","updated_at":"2016-10-04T20:13:34Z","body":"> Requiring lat/lon coordinates has always been part of CF\r\n\r\nhmm -- I'm thinking that we may not want to extend this requirement to UGRID -- (and it's note there yet). And it pyugrid can be very useful with other coordinate systems.\r\n\r\nBut what does pyugrid do if both UTM (for example) AND lat-lon are given?\r\n\r\n\r\n\r\n"}}
{"actor":{"display_login":"ChrisBarker-NOAA"}}