[PROJ] Use of EPSG codes in proj_create()
Paul Ramsey
pramsey at cleverelephant.ca
Tue Apr 2 11:15:54 PDT 2019
:) life is grand. So every downstream project will have an #ifdef’d implementation for version 6.0 ;)
P
> On Apr 2, 2019, at 11:13 AM, Even Rouault <even.rouault at spatialys.com> wrote:
>
> On mardi 2 avril 2019 20:08:46 CEST Oliver Eichler wrote:
>> Thanks for the answer! :D
>>
>> But I still wonder what is the best way to get the same functionality as
>> with pj_transform(). It might not have been the most standard conform
>> thing but it did the job quite good and consistent. Now it seems to be
>> that everyone needs to write a beast that analyzes the axis ordering,
>> analyzes the coordinate format, fix all input to match requirements, do
>> the conversion and normalize all output.
>
> PROJ master (future 6.1.0) has a new proj_normalize_for_visualization()
> function that takes a pedantic-axis-order compliant PJ object (returned by
> proj_create_crs_to_crs()) and add the needed axis swapping to get the
> traditional GIS friendly order.
>
> --
> Spatialys - Geospatial professional services
> http://www.spatialys.com
> _______________________________________________
> PROJ mailing list
> PROJ at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/proj
More information about the PROJ
mailing list