Re: [gdal-dev] WCS GetCoverage with AxisOrder swap

On 11/09/2017 10:44 AM, Andrea Aime wrote: > On Thu, Nov 9, 2017 at 10:36 AM, jratike80 > > wrote: > > Hi folks, > > I think that it is extremely good to discuss about axisOrder, > GridFunctions, > offsetVectors, axisLabels etc. because fo

Re: [gdal-dev] WCS GetCoverage with AxisOrder swap

Even- very good question: On 11/09/2017 08:41 AM, Even Rouault wrote: > > Peter, > >   > > > the axisLabels attribute determines axis order, and this in turn refers to > > the > > > CRS definition behind the URL in srsName. > >   > > Does the value of RectifiedGrid.axisLabels must be correlated

Re: [gdal-dev] WCS GetCoverage with AxisOrder swap

Ari Jolma kirjoitti 09.11.2017 klo 15:52: jratike80 kirjoitti 09.11.2017 klo 15:18: Piero Campa wrote And for WCS subsetting, when you write something like SUBSET=AXIS_NAME(min,max), ​ ​ where AXIS_NAME should come from ? From the RectifiedGrid.axisLabels I guess ? ​ ​NO, subsetting/subspacin

Re: [gdal-dev] WCS GetCoverage with AxisOrder swap

jratike80 kirjoitti 09.11.2017 klo 15:18: Piero Campa wrote And for WCS subsetting, when you write something like SUBSET=AXIS_NAME(min,max), ​ ​ where AXIS_NAME should come from ? From the RectifiedGrid.axisLabels I guess ? ​ ​NO, subsetting/subspacing​ is meant to work aligned with the coordi

Re: [gdal-dev] WCS GetCoverage with AxisOrder swap

Piero Campa wrote >> And for WCS subsetting, when you write something like >> SUBSET=AXIS_NAME(min,max), >> ​ ​ >> where AXIS_NAME should come from ? From the RectifiedGrid.axisLabels I >> guess ? >> > ​ > ​NO, subsetting/subspacing​ is meant to work aligned with the coordinate > system (!) > You c

Re: [gdal-dev] WCS GetCoverage with AxisOrder swap

Even, On 8 November 2017 at 16:31, Even Rouault wrote: > OK thanks for the explanations. Makes some sense > > So it would seem that if you want to return a GeoTIFF in > > traditional GIS order (ie faster varying dimension corresponds to > longitude), AND you emit > ​ ​ > offsetVector in the

Re: [gdal-dev] WCS GetCoverage with AxisOrder swap

On Thu, Nov 9, 2017 at 10:36 AM, jratike80 < jukka.rahko...@maanmittauslaitos.fi> wrote: > Hi folks, > > I think that it is extremely good to discuss about axisOrder, > GridFunctions, > offsetVectors, axisLabels etc. because for sure we all want to build > interoperability between different WCS 2.

Re: [gdal-dev] WCS GetCoverage with AxisOrder swap

Even Rouault-2 wrote > Peter, > >> the axisLabels attribute determines axis order, and this in turn refers >> to the >> CRS definition behind the URL in srsName. > > Does the value of RectifiedGrid.axisLabels must be correlated with the one > of the CRS, > or can it be a "random" value ? > For ex

Re: [gdal-dev] WCS GetCoverage with AxisOrder swap

Peter, > the axisLabels attribute determines axis order, and this in turn refers to the > CRS definition behind the URL in srsName. Does the value of RectifiedGrid.axisLabels must be correlated with the one of the CRS, or can it be a "random" value ? For example, GeoServer has i j > My team ha

Re: [gdal-dev] WCS GetCoverage with AxisOrder swap

On 11/08/2017 10:01 PM, Ari Jolma wrote: > > Even Rouault kirjoitti 08.11.2017 klo 17:31: > >> On mercredi 8 novembre 2017 15:50:48 CET Piero Campalani wrote: >> >> >> > This order is what can be referred to in the GridFunction: +1 --> first >> >> > GRID axis, +2 --> second GRID axis, etc. >> > >

Re: [gdal-dev] WCS GetCoverage with AxisOrder swap

Even Rouault kirjoitti 08.11.2017 klo 17:31: On mercredi 8 novembre 2017 15:50:48 CET Piero Campalani wrote: > This order is what can be referred to in the GridFunction: +1 --> first > GRID axis, +2 --> second GRID axis, etc. Ok, this tells me that the axisOrder attribute in sequenceRule

Re: [gdal-dev] WCS GetCoverage with AxisOrder swap

Even Rouault-2 wrote > So, it would seem that there are 2 more or less equivalent way of > achieving the same end result ? My understanding is that these two are equivalent and define a grid in EPSG:4326 with pixel size of 1 degree (if it is an image). First way is to turn the offset vectors, this

Re: [gdal-dev] WCS GetCoverage with AxisOrder swap

On mercredi 8 novembre 2017 15:50:48 CET Piero Campalani wrote: > Hi there, > > The gml:GridFunction is *not* an auxiliary definition of the grid geometry, > but rather a guidance on how to link the grid to the *range set* (i.e. the > data), so it shall not be compared with the "domain" informatio

Re: [gdal-dev] WCS GetCoverage with AxisOrder swap

8:49 +0200 > From: Ari Jolma > To: "'gdal-dev@lists.osgeo.org' (gdal-dev@lists.osgeo.org)" > > Subject: [gdal-dev] WCS GetCoverage with AxisOrder swap > Message-ID: > Content-Type: text/plain; charset=utf-8; format=flowed > > I've got to t

Re: [gdal-dev] WCS GetCoverage with AxisOrder swap

Even Rouault-2 wrote > On mercredi 8 novembre 2017 14:50:54 CET Ari Jolma wrote: >> Ari Jolma kirjoitti 08.11.2017 klo 13:48: >> > for MapServer and GeoServer I need to have at least two hack options >> > (NoOffsetSwap and NoGridEnvelopeSwap, maybe there could be only one). >> > I have not yet che

Re: [gdal-dev] WCS GetCoverage with AxisOrder swap

On mercredi 8 novembre 2017 14:50:54 CET Ari Jolma wrote: > Ari Jolma kirjoitti 08.11.2017 klo 13:48: > > for MapServer and GeoServer I need to have at least two hack options > > (NoOffsetSwap and NoGridEnvelopeSwap, maybe there could be only one). > > I have not yet checked if the rasters returne

Re: [gdal-dev] WCS GetCoverage with AxisOrder swap

Ari Jolma kirjoitti 08.11.2017 klo 13:48:  for MapServer and GeoServer I need to have at least two hack options (NoOffsetSwap and NoGridEnvelopeSwap, maybe there could be only one). I have not yet checked if the rasters returned from those two are ok. The rasters that those servers return are

[gdal-dev] WCS GetCoverage with AxisOrder swap

I've got to the point in the new WCS driver development, where I'm trying to issue GetCoverage request to a GeoServer, which is serving data in EPSG that has axis order swapped. This is related to the earlier discussion https://lists.osgeo.org/pipermail/gdal-dev/2017-April/046366.html The dat