issues: 403971686
This data as json
| id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 403971686 | MDU6SXNzdWU0MDM5NzE2ODY= | 2722 | [discussion] Use WKT or PROJ.4 string for CRS representation? | 8699967 | closed | 0 | 4 | 2019-01-28T19:31:01Z | 2019-01-28T22:45:52Z | 2019-01-28T22:45:52Z | CONTRIBUTOR | BackgroundPROJ.4 is a popular format for storing projection strings. It has a nice and simple interface that is easy to use. However, converting to the PROJ.4 format from other formats can cause loss of useful projection information (PROJ.4 contains a warning about it here and other users have had issues with losing information in the conversion, an example is here). A lossless, though more complex, alternative is the WKT string. The WKT string is also going through improvements and will include the WKT2 (2015 and 2018) versions with useful information. The rasterio project has already made the switch to use the WKT string. DiscussionThe issue is meant to be a place to discuss whether the xarray project should use the WKT or the PROJ.4 format moving forward for storing CRS strings. @fmaussion @sgillies @cratcliff @djhoese @rouault @kbevers Feel free to include others that you think would provide valuable information to this discussion. |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/2722/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
completed | 13221727 | issue |