Conversation
| Coordinate Reference System. A system that maps spatial data coordinates to real-world locations, | ||
| combining a coordinate system with a reference surface like a projection or :term:`ellipsoid`. | ||
| Coordinate Reference System. Specifies how coordinates correspond to locations on Earth, | ||
| including the coordinate system, :term:`datum`, and, if applicable, a projection. |
There was a problem hiding this comment.
As many people exchange "coordinate reference system" and "coordinate system", if we use "coordinate system" we should also explain it. Otherwise people will not understand it.
Other option is to not mention "coordinate system" at all, but tell something else in the CRS definition.
There was a problem hiding this comment.
I've added a glossary entry for "coordinate system" as best I can, and linked to that
Co-authored-by: Javier Jimenez Shaw <j1@jimenezshaw.com>
|
I read through the rendered preview. Nice work. Thanks, this is a really good addition!
That definitely makes sense given the topic. The tutorial hits the right spot IMO. It's introductory and beginner friendly while still providing helpful info and interesting reading for more experienced users. I also like that several links to relevant information are incorporated into a concise tutorial. That gives me one good source I can go to even if I'm just looking for some linked info that I can't remember where it was. Keeping the intro tutorial relatively short makes it more digestible, but you condensed it well to the essentials. That seems like the right model. I would be interested to see it link to the "advanced" page at some point :) |
Co-authored-by: Even Rouault <even.rouault@spatialys.com>
Co-authored-by: Even Rouault <even.rouault@spatialys.com>
Co-authored-by: Even Rouault <even.rouault@spatialys.com>
Co-authored-by: Even Rouault <even.rouault@spatialys.com>
|
@jjimenezshaw @rouault @ctoney - thanks all for your reviews, and taking the time to read through this. I'll address the comments above in the next few days. |
|
Updated the tutorial to take into account the summary CRS information (added in #14303). A couple of questions while writing the docs: I presume I tried to explain the duplicated "Popular Visualisation Pseudo-Mercator" in the ouput as follows:
Is this correct? |
although that's clearly lazyness of mine. There are ancient times geographic CRS where the units is ... cough cough ... grads. But who cares about les-fromages-qui-puent ? Anyway most of the GDAL interface for such CRS communicates in degree, so let's shut up on those confusing details
yep, but the best documentation is the one you don't have to write. I'll tune that so we don't emit twice the same info |
|
This PR adds a new tutorial on working with CRSs in GDAL. It was hard to define the scope of the tutorial, and I have pages more of notes that may make it to a separate "advanced" page. I'm not 100% happy with it, so open to suggestions and feedback before merging.
Link to preview: https://gdal--14285.org.readthedocs.build/en/14285/tutorials/reprojecting_data.html
Several new examples are added to the various CLI tools. There is some overlap with the older tutorial, but the focus here is on the new CLI and reading the CRS info returned by GDAL.
There is also a fix in one of the parameters in
gdal_raster_reproject.rst.A few notes:
gdal infooutput. I'm guessing 90% of the time users just want to know the EPSG code. Having several EPSG codes included in the output (for example in the CONVERSION block) likely causes some confusion. Would only returning the EPSG code for known / unmodified CRSs be an option?Warning 1: A geometry of type MULTIPOLYGON is inserted into layer ne_10m_admin_0_countries_chn of geometry type POLYGON, which is not normally allowed by the GeoPackage specification, but the driver will however do it. To create a conformant GeoPackage, if using ogr2ogr, the -nlt option can be used to override the layer geometry type. This warning will no longer be emitted for this combination of layer and feature geometry type.Hopefully there are no inaccuracies in the tutorial - have at it @jjimenezshaw !