Even Rouault kirjoitti 03.11.2017 klo 11:07:
> 1) My understanding is that there are potentially three CRS in
> operation: the CRS of the bbox of the coverage (the native CRS of the
> server); the CRS of the grid; and the CRS where the user wants the data.
> I can imagine that it is perfectly possible for a server to advertise
> data from an area bounded by geographic coordinates, and that the data
> is in some specific projected coordinate system.
For me the "native" CRS (as much as a client can see) is the one of
the CoverageDescription.boundedBy.Envelope@srsName attribute
exactly
. If the server advertizes it as EPSG:4326, but the native data is in
something else, this is an implementation detail of the server. That
said, as you mention, the user could then decide to request in that
alternative CRS if it has knowledge of that.
> Also, the data could be
> regular but not east-north (it is rotated for example). This would be
> described in a CoverageDescription. Despite the rotation, GDAL would
> show the data east-nort (without rotation), since only the bbox of the
> coverage is given.
You should be able to retrieve the rotation/shearing terms in the
domainSet.RectifiedGrid.offsetVector 's element similarly to other WCS
versions
yes, and that is needed to compute (approximate) the size of the GDAL
dataset raster, as I just wrote in another reply to this thread.
Ari
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
