issue_comments

Agree about the documentation, so have vastly improved the documentation now, with a full list of examples for all functionality. Hopefully that makes it clearer how to use PyCRS and if it would be a good fit for your project. Have also added doctests of all the readme examples with Travis CI for both Py2 and 3. Appreciate all the issues raised and suggestions 👍 Thinking of releasing this as the first major stable version 1.0.0 on pypi for more reliablity, once the issues have been cleared up.

Also, please let me know about your ideas for features you would like to see in a crs library, either here or raise as an issue. Creating library specific objects might be a good idea, if you want to give some use cases and reasonings. In what ways are library soecific crs objects difficult to create? Don’t they provide shortcuts for creating from proj4 strings?

Hi. This project seems very interesting. Am i right in understanding it primarily provides a type of data structure/object that allows labelled access to gis raster data (plus additional dimensions, in most cases time i guess)? Maybe you could clarify which aspects of the concersation you wanted feedback on (it was impressingly long)? If youre thinking about how to represent crs in xarray, you’re right that PyCRS already does this. For a project that needs a container for crs objects from many possible sources, possibly with the option to modify the crs, plus flexibly converting to different representation formats, PyCRS does exactly that. Plus it’s as lightweight as it gets. It maps each parameter with an object, and all parameters and logical subgroupings can be accessed and changed from the toplevel CRS object. I need to add some more documentation on the structure of the CRS object, but just have a look at the code for now. One question: what types of sources/formats do xarray objects come from, is it primarily from netcdf files or also other ones? And what type of crs format does netcdf use? PyCRS can load from the main formats (proj4, esri/ogc wkt, various codes), but i have not yet added the geotiff specification. As for maintenance, it’s true that it hasnt been updated for a bit, though i just recently am trying to change that. However, for this particular project, most of my inactivity is honestly that it simply works. Crs format conversion should be a deterministic process, as they all refer to the same theoretical concepts. I’ve done some basic testing on converring between a variety of popular crs formats, and found that it gets most of them right. The downside is i’m not sure how widely it’s used so far, and i couldve gotten some of the parameter conversions wrong, so it may be that if you start using it users may find mistakes. The upside is that there are only so many parameters, and correcting mistakes should be an easy onetime fix.