[gdal-dev] [Geoserver-devel] GML lat-lon coverages and interoperability

Andrea Aime andrea.aime at geo-solutions.it
Mon Apr 10 06:57:03 PDT 2017

Hi Even,
in CIS 1.1 they state:

Coverages are assumed to have a 1:1 correlation between the axis names
given in axis-Labels and gridLabels, i.e.: they shall relate pairwise,
given by their sequence position. For example, axisLabels=“Lat Long h date”
and gridLabels={i j k l} implies a correspondence of Lat with i, Long with
j, h with k, and date with l.

If there is no 1:1 correspondence between geographic and raster space axis,
then I see no other way but to use Function to explicitly correlate the two.
How would you propose to proceed instead?


On Mon, Apr 10, 2017 at 3:31 PM, Even Rouault <even.rouault at spatialys.com>

> On lundi 10 avril 2017 15:06:55 CEST Andrea Aime wrote:
> > Hi,
> > sorry I lost track of the subject. So, to close up, and approach where
> the
> > envelope is reported as "lat lon" and the "i j" raster space
> > axis would map pairwise, so i pointing north-wards and j east-wards,
> would
> > be considered valid?
> > E.g., if one rescaling says "i is going to be 200 pixels" it really means
> > the output image will be 200 pixels tall?
> IMHO, importing EPSG axis order mess in raster space would seem to be
> foolish to me and cause major annoyances. Performance-wise, processing
> flipped rasters with classic algorithms that process line per line would be
> terrible as soon as they are large enough, since reading each line would in
> practice require to read the whole raster each time.
> Even
> --
> Spatialys - Geospatial professional services
> http://www.spatialys.com
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Geoserver-devel mailing list
> Geoserver-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel

GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549



Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20170410/72118399/attachment.html>

More information about the gdal-dev mailing list