[PROJ] comparing projstrings

[Thomas Knudsen]

Also remember to take pipeline globals into account: proj=pipeline
ellps=GRS80 step ... step... will set ellps=GRS80 for all steps due to the
definition being put before first step definition

tir. d. 1. jan. 2019 16.40 skrev Even Rouault <even.rouault at spatialys.com>:

> Idan,
>
> >
> > Is there any importance for the order of the parameters in a projstring
> CRS
> > definition?
>
> For a single step pipeline, no. But starting with PROJ 5, it you use a
> proj=pipeline, yes the order of steps matter.
>
> >
> > Is there a function that compares projstrings that takes into
> consideration
> > that two projstrings can be equal even if the strings are not exactly the
> > same?
>
> For single-step proj strings and currently released versions, using GDAL
> with
> OSRImportFromProj4() + OSRIsSame() will do
>
> If you use PROJ master, you can equivalently use
> proj_create_from_proj_string() + proj_is_equivalent_to(). Note that this
> will
> work as you mentionned only for single-step strings. (For multiple steps,
> this
> will mostly be equivalent to exact string comparisons)
>
> Even
>
> --
> Spatialys - Geospatial professional services
> http://www.spatialys.com
> _______________________________________________
> PROJ mailing list
> PROJ at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/proj
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/proj/attachments/20190101/de7608ba/attachment.html>