[geotk] CRS issue with WFS module

Fri Oct 27 09:36:57 PDT 2017

Simone,

I agree with your analysis. I think we will have no choice to modify the
behavior of the client. Hopefully, Martin can help us address this issue. I
think we should report this issue as a CR to enforce the adherence to
standards. This is a huge impediment to interoperability as every vendor
comes out with their strategy. Given a URL to WFS, it is impossible to
implement a client that can accommodate the different profile for each
vendor. We are harvesting thousands of WFS on Geoplatform and access them
in a unified way is crucial. So the usage of the short name
EPSG:xxxx should be banned or need to be enforced to follow the standard.
Not sure if this issue has already been addressed by OGC.

Regards
Stephane

On Fri, Oct 27, 2017 at 12:19 PM, Simone Giannecchini <
simone.giannecchini at geo-solutions.it> wrote:

> Ciao All,
> reversing axis order for EPSG:4326 requires coding and cannot be done
> quickly, since we cannot make this behavior the default as most client
> will break.
>
> Preserving the full URL on the client side seems the lowest hanging
> fruit at this stage, since with the full URL you should get
> coordinates in the proper order.
>
>
> Regards,
> Simone Giannecchini
> ==
> GeoServer Professional Services from the experts!
> Visit http://goo.gl/it488V for more information.
> ==
> Ing. Simone Giannecchini
> @simogeo
> Founder/Director
>
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> 55054  Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax:     +39 0584 1660272
> mob:   +39 333 8128928
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
> AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
> 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.
>
>
> On Fri, Oct 27, 2017 at 6:09 PM, Stephane Fellah
> <stephanef at imagemattersllc.com> wrote:
> > Martin,
> >
> > Yes, definitely we will test it. You plan to deploy 4.0.4 on maven repo
> will
> > work for us.
> > Please note that the CRS URL is truncated in the WFSFeatureStore
> >
> >
> > The code snippet that breaks is in the WFSFeatureStore.java  (line 138)
> >
> > //extract the feature type -----------------------------------------
> > CoordinateReferenceSystem crs;
> > FeatureType sft;
> > try {
> >     String defaultCRS = ftt.getDefaultCRS();
> >     if(defaultCRS.contains("EPSG")){
> >         final int last = defaultCRS.lastIndexOf(':');
> >         defaultCRS = "EPSG:"+defaultCRS.substring(last+1);
> >     }
> >     crs = CRS.forCode(defaultCRS);
> >     if (getLongitudeFirst()) {
> >         crs =
> > AbstractCRS.castOrCopy(crs).forConvention(AxesConvention.RIGHT_HANDED);
> >     }
> >     sft = requestType(typeName);
> > }
> >
> >
> > Simone has redeployed the WFS using the short version "EPSG:4326" to see
> if
> > the problem is solved, However, we ran into another issue with Geoserver.
> > The coordinates of lat/long are flipped when the short version is used on
> > Geoserver.
> > Only the preservation of the full URL will keep the order lat/long. I
> will
> > forward to you the email thread related to this problem.
> >
> >
> >
> >
> > Regards
> >
> >
> >
> >
> > On Fri, Oct 27, 2017 at 11:16 AM, Martin Desruisseaux
> > <martin.desruisseaux at geomatys.com> wrote:
> >>
> >> Hello Stephane
> >>
> >> Indeed, the srsName attribute in gml:Envelope is of type anyURI. My
> >> interpretation is that the "urn:ogc:def:crs:epsg:…" syntax is more
> adequate
> >> than "EPSG:…" there. I'm not sure why WFSFeatureStore uses the short
> form;
> >> maybe at the time it was written, not all servers understood the URN
> form.
> >>
> >> I can try modify Geotk 4.0.0 for using the URN form. I think (but I'm
> not
> >> sure) it would be at line 576 of GTtoSE110Transformer. If I try a
> change,
> >> would you have an opportunity to test? What would be the preferred
> approach?
> >>
> >> You checkout the source code and propose the line to edit.
> >> I deploy a 4.0.4-SNAPSHOT version (the changes in 4.0.1 to 4.0.3 should
> >> not affects WFS).
> >>
> >> If we get a test to work, I can deploy a 4.0.4 on
> >> http://maven.geotoolkit.org/ if useful.
> >>
> >>     Martin
> >>
> >>
> >
> >
> >
> > --
> > Stephane Fellah
> > Chief  Knowledge Scientist
> > Image Matters LLC
> > Office: +(703) 669 5510
> > Cell: 703 431 9420
>

-- 
Stephane Fellah
Chief  Knowledge Scientist
Image Matters LLC
Office: +(703) 669 5510
Cell: 703 431 9420
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geotoolkit/attachments/20171027/4963fe7b/attachment-0001.html>