If you plan to transform to a different system anyway, I would definitely
prefer going to geographical coordinates, and computing the length of the
geodesic between the two points.
First step in converting between a projected system and the earth centered
cartesian XYZ, is using the inverse of the
I think that sounds awesome wrt. PROJ dependency reduction,
since the informal interpretation of TIFF as "Thousands of
Incompatible File Formats" doesn't really apply to PROJ's use
case
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osge
Way back in a different career stage, I published this method for
displaying colour-infrared as fairly convincing pseudo-true colour:
https://www.researchgate.net/publication/242078137_A_simplified_method_for_generation_of_pseudo_natural_colours_from_colour_infrared_aerial_photos
At least one comp
In the DK registry we used descriptive names, rather than numbers to refer
to the transformations taking legacy systems to ETRS89. Essentially these
transformations amounted to CRS definitions. Is it safe to assume a
"crs_code" is strictly numeric?
Den ons. 10. jan. 2024 kl. 20.46 skrev Meyer, Jes
Den tirs. 5. dec. 2023 kl. 02.15 skrev Greg Troxel via gdal-dev <
gdal-dev@lists.osgeo.org>:
> Building the
> rust compiler requires the *immediately preceding* compiler, which seems
> unprecented, and I don't understand how people can think that's ok
I don't think this is true - it's merely the
