Hi Brad, hi Jukka
Thank you for the tips!
Seems that in fact cs2cs works similar to GDAL and both seem to be
installed e.g. with QGIS
cs2cs +init=epsg:4326 +to +init=epsg:2056
:Stefan
Am Mi., 5. Feb. 2020 um 13:14 Uhr schrieb jratike80
:
>
> Hi,
>
> Gdaltransform should be a rather close hit
>
Good morning,
I unable to use gdal_calc to make a pixel-wise computation between two
tiffs with several bands.
I have two tifs, each contains time series of the same spectral band.
For example, file1.tif contains a time series of RED and file2.tif
contains a time series of NIR (near infrared). Th
On Thu, 6 Feb 2020 at 13:29, Daniel Evans wrote:
>
> I'm still so backwards that I rely on the Git repository and the Python API
> documentation for information (https://gdal.org/python/)
> but I've discovered that the latter is rather out of date today, as options
> like GetAxisMappingOrder ar
> In my previous example, if one compares the responses to
GetAxisMappingStrategy(), the original SRS and that returned by the layer are
different:
> >>> projection.GetAxisMappingStrategy() == osr.OAMS_AUTHORITY_COMPLIANT
>
> # True
>
> >>> projFromLayer.GetAxisMappingStrategy() == osr.OAMS_TRA
I'm still so backwards that I rely on the Git repository and the Python API
documentation for information (https://gdal.org/python/) - but I've discovered
that the latter is rather out of date today, as options like
GetAxisMappingOrder aren't listed at all.
Daniel
-Original Message-
Fr
On Thu, 6 Feb 2020 at 13:20, Daniel Evans wrote:
>
> > Try https://gdal.org/tutorials/osr_api_tut.html#crs-and-axis-order
>
> Thanks - I hadn't spotted your response until sending mine just now. That is
> indeed what's going on, with the setting being changed depending on how an
> SRS has been u
> Try https://gdal.org/tutorials/osr_api_tut.html#crs-and-axis-order
> Best regards,
> --
> Mateusz Loskot, http://mateusz.loskot.net
Thanks - I hadn't spotted your response until sending mine just now. That is
indeed what's going on, with the setting being changed depending on how an SRS
has b
It seems that the Migration Guide has the answer:
> OSRImportFromEPSG() takes into account official axis order.
> Traditional GIS-friendly axis order can be restored with
> OGRSpatialReference::SetAxisMappingStrategy(OAMS_TRADITIONAL_GIS_ORDER);
In my previous example, if one compares the respons
On Thu, 6 Feb 2020 at 11:21, Daniel Evans wrote:
> I am currently looking at upgrading from GDAL 2.x to GDAL 3.x. Most of my
> software tests pass, but I have a few failing because a transform from
> WGS84 to WGS84 is flipping the axes on transformed geometries.
>
>
>
> I have a recollection of r
To give a somewhat more concise example:
from osgeo import gdal, osr, ogr
projection = osr.SpatialReference()
projection.ImportFromEPSG(4326)
temp_ds = gdal.GetDriverByName('Memory').Create('', 0, 0, 0)
layer = temp_ds.CreateLayer("foo", projection, geom_type=ogr.wkbPolygon)
projFromLayer = lay
I am currently looking at upgrading from GDAL 2.x to GDAL 3.x. Most of my
software tests pass, but I have a few failing because a transform from WGS84 to
WGS84 is flipping the axes on transformed geometries.
I have a recollection of reading about GDAL 3 (or PROJ 6) resulting in axis
swapping in
11 matches
Mail list logo
