[CITE-Forum] Issues during OGC test

Dirk Stenger cite at lat-lon.de
Tue Sep 6 03:22:58 EDT 2016


Hi Kaustubh,

apparently, your service is still providing AUTO CRS instead of AUTO2
which is not correct according to the specification.

Page 15 of the specification (document 06-042) says: "This International
Standard defines three namespaces: CRS, EPSG and AUTO2, as discussed below."

Kind regards,
Dirk



Am 06.09.2016 um 06:43 schrieb Kaustubh.Chandorkar at igenesys.com:
> Hi Dirk,
>  
> Thanks for your reply.
>  
> Our service are already updated and service has posted on Geoserver
> using wms 1.3.
>
> forums.igenesys.com/geoserverogc/cite/wms?service=WMS&request=GetCapabilities&version=1.3.0
>
>  
>
> Please suggest.
>
>  
> Regards,
> Kaustubh
> ------------------------------------------------------------------------
> *From:* CITE-Forum
> [cite-forum-bounces+kaustubh.chandorkar=igenesys.com at lists.opengeospatial.org]
> On Behalf Of Dirk Stenger via CITE-Forum
> [cite-forum at lists.opengeospatial.org]
> *Sent:* Friday, September 02, 2016 3:37 PM
> *To:* Andrea Aime
> *Cc:* cite-forum at lists.opengeospatial.org
> *Subject:* Re: [CITE-Forum] Issues during OGC test
>
> Hi,
>
> yes, correct, WFS 1.3 just supports AUTO2. So, the capabilities should
> be modified regarding that.
>
> The CITE test will not add additional values to the CRS parameter but
> pick the value from the metadata. So, we have to find a way how to
> handle this case inside the test suite (e.g. skipping AUTO2 CRS as
> Andrea already proposed).
>
> @Kaustubh: Can you please  update your service accordingly and confirm
> these findings? Can we use this service to reproduce the just
> discussed error which will probably occur next?
>
> Kind regards,
> Dirk
>
>
>
> Am 02.09.2016 um 10:46 schrieb Andrea Aime:
>> Hi,
>> the AUTO CRS need extra parameters to be parsed (like, central
>> meridian) which are dynamically provided by the client.
>> It seems to me there are two possible cases:
>>
>>   * The AUTO CRS are not supposed to be advertised, so they should be
>>     removed from the caps document (but then, how is the client
>>     supposed to know if they are supported, or not?)
>>   * The AUTO CRS are supposed to be advertised/advertiseable, and if
>>     so, the CITE test should be filling in the missing parameters on
>>     its own
>>
>> The spec for WMS 1.3 apparently supports only AUTO2, so the caps
>> should be modified to use those instead of AUTO I believe, and then
>> the spec says:
>>
>> -----------------------------------
>> A server indicates that it supports Auto Orthographic CRS by
>> including the element
>> “<CRS>AUTO2:42003</CRS>” in its service metadata. A client may issue
>> a GetMap request for a map in this CRS, with
>> bounding box in meters, centered at 100 degrees West longitude and 45
>> degrees North latitude, using the parameter
>> “CRS=AUTO2:42003,1,-100,45”.
>> -----------------------------------
>>
>> So it seems to me that the CITE tests should also either ignore the
>> AUTO2 CRSs, or fill in the necessary parameters
>>
>> Cheers
>> Andrea
>>
>>
>> On Thu, Sep 1, 2016 at 9:10 AM, cite--- via CITE-Forum
>> <cite-forum at lists.opengeospatial.org
>> <mailto:cite-forum at lists.opengeospatial.org>> wrote:
>>
>>     Hi Kaustubh,
>>
>>     as far as I see, the test failure is correct. In the details you
>>     see the request
>>     send by the ETS:
>>     http://forums.igenesys.com:80/geoserverogc/cite/ows?SERVICE=WMS&&HeIgHt=200&LaYeRs=Autos&CrS=AUTO%3A42001&BbOx=0,0,1,1&StYlEs=&ReQuEsT=GetMap&WiDtH=200&VeRsIoN=1.3.0&FoRmAt=image%2Fpng
>>     <http://forums.igenesys.com:80/geoserverogc/cite/ows?SERVICE=WMS&&HeIgHt=200&LaYeRs=Autos&CrS=AUTO%3A42001&BbOx=0,0,1,1&StYlEs=&ReQuEsT=GetMap&WiDtH=200&VeRsIoN=1.3.0&FoRmAt=image%2Fpng>
>>
>>     An unexpected exception is returned by the service:
>>
>>     <ServiceExceptionReport version="1.3.0"
>>     xsi:schemaLocation="http://www.opengis.net/ogc
>>     <http://www.opengis.net/ogc>
>>     http://forums.igenesys.com:80/geoserverogc/schemas/wms/1.3.0/exceptions_1_3_0.xsd
>>     <http://forums.igenesys.com:80/geoserverogc/schemas/wms/1.3.0/exceptions_1_3_0.xsd>">
>>       <ServiceException code="InvalidCRS">
>>           Error occurred decoding the espg code AUTO:42001 No code
>>     "AUTO:42001" from
>>     authority "AUTO" found for object of type "ProjectedCRS".
>>       </ServiceException>
>>     </ServiceExceptionReport>
>>
>>
>>     The crs (AUTO:42001) is taken from the parent of the requested
>>     layer (Autos).
>>     The crs are inherited to the child layers, so this request should be
>>     processable. But the service cannot handle this crs.
>>
>>     Kind regards,
>>     Lyn
>>
>>     Am 31.08.2016 um 13:59 schrieb Kaustubh.Chandorkar at igenesys.com
>>     <mailto:Kaustubh.Chandorkar at igenesys.com>:
>>     > Thanks Lyn.
>>     >
>>     > As suggested by you, I have changed the titles and now able to
>>     see images.
>>     >
>>     > Now, still there are some errors are coming.
>>     >
>>     >   Testing getmap:invalid-crs type Mandatory in Test Mode with
>>     defaultResult Pass (s0012/d711e387_1/d1794e39_1/d1794e146_1)...
>>     >    Context: WMS_Capabilities element
>>     >    Assertion: When the CRS parameter in a GetMap request
>>     contains a CRS that is not valid for any of the layers being
>>     requested, then the server shall throw a Service Exception 
>>      (code=InvalidCRS).
>>     >   Test getmap:invalid-crs Passed
>>     >   Test getmap:crs Failed - Inherited
>>     >
>>     >
>>     >
>>     >   Testing getmap:crs-inherited type Mandatory in Test Mode with
>>     defaultResult Pass (s0013/d711e387_1/d1794e39_1/d1794e144_1)...
>>     >    Context: WMS_Capabilities element
>>     >    Assertion: When a GetMap request contains a single layer and
>>     a CRS where the CRS is inherited from a parent layer in the
>>     capabilities document, then the response is valid.
>>     >   Test getmap:crs-inherited Failed
>>     >
>>     >
>>     >
>>     > Please see the attached screenshot and log files.
>>     >
>>     > Summary of results
>>     > Best Practice   Passed  Continue        Not Tested      Warning
>>     Skipped Failed  Failed (Inherited)
>>     > 0       214     0       0       0       0       1       3
>>     >
>>     >
>>     >
>>     > Please let me know if I am missing something.
>>     >
>>     >
>>     >
>>     > Regards,
>>     >
>>     > Kaustubh
>>     >
>>     >
>>     > ________________________________________
>>     > From: CITE-Forum [cite-forum-bounces at lists.opengeospatial.org
>>     <mailto:cite-forum-bounces at lists.opengeospatial.org>] On Behalf
>>     Of cite--- via CITE-Forum [cite-forum at lists.opengeospatial.org
>>     <mailto:cite-forum at lists.opengeospatial.org>]
>>     > Sent: Wednesday, August 31, 2016 12:29 PM
>>     > To: cite-forum at lists.opengeospatial.org
>>     <mailto:cite-forum at lists.opengeospatial.org>
>>     > Subject: Re: [CITE-Forum] Issues during OGC test
>>     >
>>     > Hi Kaustubh,
>>     >
>>     > sorry for not getting back to you sooner. Thanks for the
>>     excellent and detailed
>>     > report! I can follow you until the cause of the missing images.
>>     I've tried with
>>     > your WMS
>>     >
>>     (http://forums.igenesys.com/geoserverogc/cite/wms?service=WMS&request=GetCapabilities&version=1.3.0
>>     <http://forums.igenesys.com/geoserverogc/cite/wms?service=WMS&request=GetCapabilities&version=1.3.0>)
>>     > and official Teamengine
>>     (http://cite.opengeospatial.org/teamengine
>>     <http://cite.opengeospatial.org/teamengine>).
>>     >
>>     > As cause for the missing images I see the empty layers in src
>>     attribute of the
>>     > img tag (e.g.
>>     >
>>     http://forums.igenesys.com/geoserverogc/cite/ows?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&LAYERS=&STYLES=&CRS=CRS:84&BBOX=-1,-1,1,1&WIDTH=300&HEIGHT=300&FORMAT=image%2Fpng
>>     <http://forums.igenesys.com/geoserverogc/cite/ows?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&LAYERS=&STYLES=&CRS=CRS:84&BBOX=-1,-1,1,1&WIDTH=300&HEIGHT=300&FORMAT=image%2Fpng>),
>>     > the service parameter is available.
>>     >
>>     > The reason for the missing layers are the unexpected layer
>>     titles in the
>>     > capabilities. From
>>     http://cite.opengeospatial.org/te2/about/wms/1.3.0/site/
>>     <http://cite.opengeospatial.org/te2/about/wms/1.3.0/site/>
>>     > (Test Dataset Description): "The features are organized into
>>     layers as shown in
>>     > table below. The layers may be named in any fashion, but must
>>     be titled exactly
>>     > as shown in the table."
>>     >
>>     > Please ensure that your service provides the layer with the
>>     titles from the
>>     > documentation.
>>     >
>>     > Best regards,
>>     > Lyn
>>     >
>>     >
>>     > Am 01.08.2016 um 10:22 schrieb Kaustubh.Chandorkar--- via
>>     CITE-Forum:
>>     >> Hi ,
>>     >>
>>     >> We are facing issues during OGC test.
>>     >>
>>     >>
>>     >>
>>     >> We have tried both the sites for ogc test :
>>     >>  http://cite.opengeospatial.org/teamengine/
>>     <http://cite.opengeospatial.org/teamengine/>
>>     >>  http://cite.opengeospatial.org/te2/
>>     <http://cite.opengeospatial.org/te2/>
>>     >>
>>     >> GeoServer details :
>>     >>           1. GeoServer version -  2.9
>>     >>           2. WMS version         - 1.3
>>     >>           3. Dataset (test dataset):
>>     http://cite.opengeospatial.org/te2/about/wms/1.3.0/site/
>>     <http://cite.opengeospatial.org/te2/about/wms/1.3.0/site/>
>>     >>
>>     >>
>>     >>
>>     >> For testing services we are using OGC validator test suite -
>>     Web Map Service (WMS) version 1.16.
>>     >>
>>     >> Capabilities Setup :
>>     >>
>>     http://forums.igenesys.com/geoserverogc/cite/wms?service=WMS&request=GetCapabilities&version=1.3.0
>>     <http://forums.igenesys.com/geoserverogc/cite/wms?service=WMS&request=GetCapabilities&version=1.3.0>
>>     >>
>>     >>  These are the options I am selecting in the validator website:
>>     >>
>>     >> UpdateSequence Values : Automatic - The updateSequence tests
>>     will use automatically generated updateSequence values
>>     >>
>>     >> Options : BASIC - Test basic functionality that depends on the
>>     CITE dataset. This option is required for certification.
>>     >>                QUERYABLE - Test GetFeatureInfo functionality
>>     that depends on the CITE dataset.
>>     >>
>>     >> Everytime it asks below questions :
>>     >>
>>     >> 1. Does the image above depict a large diamond that fills the
>>     frame?
>>     >> 2. Does the image above depict a map of the Blue Lake vicinity
>>     with a surrounding neatline?
>>     >> 3. In the picture on the left, Goose Island, Blue Lake, and
>>     Ashton should overlay State Forest. In the picture on the right,
>>     State Forest should be on top of Ashton, Blue Lake, and Goose
>>     Island. Are the  pictures correct?
>>     >> 4. The two pictures above should depict the same scene, but
>>     the picture on the right should be stretched so it is twice as
>>     tall as the picture on the left. Are the pictures correct?
>>     >> 5. Does the image above contain an error message indicating
>>     that the layer requested was not defined?
>>     >>
>>     >> But during these questions there is no image displays on the
>>     screen.
>>     >>  If We have a look at the src="" of the <img src> -Tag we see
>>     that the test request used to fetch the image does not have the
>>     mandatory SERVICE parameter set.
>>     >>
>>     >> Please let us know what to do in this case.
>>     >>
>>     >> Regards,
>>     >> Kaustubh
>>     >>
>>     >> ________________________________
>>     >> DISCLAIMER
>>     >>
>>     >> This communication (including any accompanying documents) is
>>     intended only for the use of the addressee(s) and contains
>>     information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized
>>     reading, dissemination, distribution or copying of this
>>     communication is prohibited. If you have received this
>>     communication in error, please promptly destroy the original
>>     communication and all copies taken thereof. Any views expressed
>>     in this message are those of the individual sender, except where
>>     the sender specifically states them to be the views of his/her
>>     company. Our company does not represent, warrant and/or guarantee
>>     that the integrity of this message has been maintained or that
>>     the communication is free of errors, virus, interception or
>>     interference.
>>     >>
>>     >>
>>     >>
>>     >> _______________________________________________
>>     >> CITE-Forum mailing list
>>     >> CITE-Forum at lists.opengeospatial.org
>>     <mailto:CITE-Forum at lists.opengeospatial.org>
>>     >> https://lists.opengeospatial.org/mailman/listinfo/cite-forum
>>     <https://lists.opengeospatial.org/mailman/listinfo/cite-forum>
>>     >>
>>     > _______________________________________________
>>     > CITE-Forum mailing list
>>     > CITE-Forum at lists.opengeospatial.org
>>     <mailto:CITE-Forum at lists.opengeospatial.org>
>>     > https://lists.opengeospatial.org/mailman/listinfo/cite-forum
>>     <https://lists.opengeospatial.org/mailman/listinfo/cite-forum>
>>     >
>>     _______________________________________________
>>     CITE-Forum mailing list
>>     CITE-Forum at lists.opengeospatial.org
>>     <mailto:CITE-Forum at lists.opengeospatial.org>
>>     https://lists.opengeospatial.org/mailman/listinfo/cite-forum
>>     <https://lists.opengeospatial.org/mailman/listinfo/cite-forum>
>>
>>
>>
>>
>> -- 
>> ==
>> GeoServer Professional Services from the experts! Visit
>> http://goo.gl/it488V for more information.
>> ==
>>
>> Ing. Andrea Aime 
>> @geowolf
>> 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
>>
>> 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.
>>
>>
>> -------------------------------------------------------
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opengeospatial.org/pipermail/cite-forum/attachments/20160906/251f12ab/attachment-0001.html>


More information about the CITE-Forum mailing list