<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi,<br>
    <br>
    yes, correct, WFS 1.3 just supports AUTO2. So, the capabilities
    should be modified regarding that.<br>
    <br>
    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).<br>
    <br>
    @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?<br>
    <br>
    Kind regards,<br>
    Dirk<br>
    <br>
    <br>
    <br>
    <div class="moz-cite-prefix">Am 02.09.2016 um 10:46 schrieb Andrea
      Aime:<br>
    </div>
    <blockquote
cite="mid:CA+nxMTvFvKUsM4_2M3KmEQL_+CAFevsAEc05vrt+0dd8_LQ+ow@mail.gmail.com"
      type="cite">
      <div dir="ltr">Hi,
        <div>the AUTO CRS need extra parameters to be parsed (like,
          central meridian) which are dynamically provided by the
          client.</div>
        <div>It seems to me there are two possible cases:</div>
        <div>
          <ul>
            <li>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?)</li>
            <li>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</li>
          </ul>
          <div>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:</div>
          <div><br>
          </div>
          <div>-----------------------------------</div>
          <div>
            <div>A server indicates that it supports Auto Orthographic
              CRS by including the element</div>
            <div>“<CRS>AUTO2:42003</CRS>” in its service
              metadata. A client may issue a GetMap request for a map in
              this CRS, with</div>
            <div>bounding box in meters, centered at 100 degrees West
              longitude and 45 degrees North latitude, using the
              parameter</div>
            <div>“CRS=AUTO2:42003,1,-100,45”.</div>
          </div>
          <div>-----------------------------------<br>
          </div>
          <div><br>
          </div>
          <div>So it seems to me that the CITE tests should also either
            ignore the AUTO2 CRSs, or fill in the necessary parameters</div>
          <div><br>
          </div>
          <div>Cheers</div>
        </div>
        <div>Andrea</div>
        <div><br>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Thu, Sep 1, 2016 at 9:10 AM, cite---
          via CITE-Forum <span dir="ltr"><<a moz-do-not-send="true"
              href="mailto:cite-forum@lists.opengeospatial.org"
              target="_blank">cite-forum@lists.opengeospatial.org</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi
            Kaustubh,<br>
            <br>
            as far as I see, the test failure is correct. In the details
            you see the request<br>
            send by the ETS:<br>
            <a moz-do-not-send="true"
href="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"
              rel="noreferrer" target="_blank">http://forums.igenesys.com:80/<wbr>geoserverogc/cite/ows?SERVICE=<wbr>WMS&&HeIgHt=200&LaYeRs=Autos&<wbr>CrS=AUTO%3A42001&BbOx=0,0,1,1&<wbr>StYlEs=&ReQuEsT=GetMap&WiDtH=<wbr>200&VeRsIoN=1.3.0&FoRmAt=<wbr>image%2Fpng</a><br>
            <br>
            An unexpected exception is returned by the service:<br>
            <br>
            <ServiceExceptionReport version="1.3.0"<br>
            xsi:schemaLocation="<a moz-do-not-send="true"
              href="http://www.opengis.net/ogc" rel="noreferrer"
              target="_blank">http://<wbr>www.opengis.net/ogc</a><br>
            <a moz-do-not-send="true"
href="http://forums.igenesys.com:80/geoserverogc/schemas/wms/1.3.0/exceptions_1_3_0.xsd"
              rel="noreferrer" target="_blank">http://forums.igenesys.com:80/<wbr>geoserverogc/schemas/wms/1.3.<wbr>0/exceptions_1_3_0.xsd</a>"><br>
              <ServiceException code="InvalidCRS"><br>
                  Error occurred decoding the espg code AUTO:42001 No
            code "AUTO:42001" from<br>
            authority "AUTO" found for object of type "ProjectedCRS".<br>
              </ServiceException><br>
            </ServiceExceptionReport><br>
            <br>
            <br>
            The crs (AUTO:42001) is taken from the parent of the
            requested layer (Autos).<br>
            The crs are inherited to the child layers, so this request
            should be<br>
            processable. But the service cannot handle this crs.<br>
            <br>
            Kind regards,<br>
            Lyn<br>
            <div class="HOEnZb">
              <div class="h5"><br>
                Am 31.08.2016 um 13:59 schrieb <a
                  moz-do-not-send="true"
                  href="mailto:Kaustubh.Chandorkar@igenesys.com">Kaustubh.Chandorkar@igenesys.<wbr>com</a>:<br>
                > Thanks Lyn.<br>
                ><br>
                > As suggested by you, I have changed the titles and
                now able to see images.<br>
                ><br>
                > Now, still there are some errors are coming.<br>
                ><br>
                >   Testing getmap:invalid-crs type Mandatory in Test
                Mode with defaultResult Pass
                (s0012/d711e387_1/d1794e39_1/<wbr>d1794e146_1)...<br>
                >    Context: WMS_Capabilities element<br>
                >    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).<br>
                >   Test getmap:invalid-crs Passed<br>
                >   Test getmap:crs Failed - Inherited<br>
                ><br>
                ><br>
                ><br>
                >   Testing getmap:crs-inherited type Mandatory in
                Test Mode with defaultResult Pass
                (s0013/d711e387_1/d1794e39_1/<wbr>d1794e144_1)...<br>
                >    Context: WMS_Capabilities element<br>
                >    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.<br>
                >   Test getmap:crs-inherited Failed<br>
                ><br>
                ><br>
                ><br>
                > Please see the attached screenshot and log files.<br>
                ><br>
                > Summary of results<br>
                > Best Practice   Passed  Continue        Not Tested 
                    Warning Skipped Failed  Failed (Inherited)<br>
                > 0       214     0       0       0       0       1 
                     3<br>
                ><br>
                ><br>
                ><br>
                > Please let me know if I am missing something.<br>
                ><br>
                ><br>
                ><br>
                > Regards,<br>
                ><br>
                > Kaustubh<br>
                ><br>
                ><br>
                > ______________________________<wbr>__________<br>
                > From: CITE-Forum [<a moz-do-not-send="true"
                  href="mailto:cite-forum-bounces@lists.opengeospatial.org">cite-forum-bounces@lists.<wbr>opengeospatial.org</a>]
                On Behalf Of cite--- via CITE-Forum [<a
                  moz-do-not-send="true"
                  href="mailto:cite-forum@lists.opengeospatial.org">cite-forum@lists.<wbr>opengeospatial.org</a>]<br>
                > Sent: Wednesday, August 31, 2016 12:29 PM<br>
                > To: <a moz-do-not-send="true"
                  href="mailto:cite-forum@lists.opengeospatial.org">cite-forum@lists.<wbr>opengeospatial.org</a><br>
                > Subject: Re: [CITE-Forum] Issues during OGC test<br>
                ><br>
                > Hi Kaustubh,<br>
                ><br>
                > sorry for not getting back to you sooner. Thanks
                for the excellent and detailed<br>
                > report! I can follow you until the cause of the
                missing images. I've tried with<br>
                > your WMS<br>
                > (<a moz-do-not-send="true"
href="http://forums.igenesys.com/geoserverogc/cite/wms?service=WMS&request=GetCapabilities&version=1.3.0"
                  rel="noreferrer" target="_blank">http://forums.igenesys.com/<wbr>geoserverogc/cite/wms?service=<wbr>WMS&request=GetCapabilities&<wbr>version=1.3.0</a>)<br>
                > and official Teamengine (<a moz-do-not-send="true"
                  href="http://cite.opengeospatial.org/teamengine"
                  rel="noreferrer" target="_blank">http://cite.opengeospatial.<wbr>org/teamengine</a>).<br>
                ><br>
                > As cause for the missing images I see the empty
                layers in src attribute of the<br>
                > img tag (e.g.<br>
                > <a moz-do-not-send="true"
href="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"
                  rel="noreferrer" target="_blank">http://forums.igenesys.com/<wbr>geoserverogc/cite/ows?SERVICE=<wbr>WMS&VERSION=1.3.0&REQUEST=<wbr>GetMap&LAYERS=&STYLES=&CRS=<wbr>CRS:84&BBOX=-1,-1,1,1&WIDTH=<wbr>300&HEIGHT=300&FORMAT=image%<wbr>2Fpng</a>),<br>
                > the service parameter is available.<br>
                ><br>
                > The reason for the missing layers are the
                unexpected layer titles in the<br>
                > capabilities. From <a moz-do-not-send="true"
                  href="http://cite.opengeospatial.org/te2/about/wms/1.3.0/site/"
                  rel="noreferrer" target="_blank">http://cite.opengeospatial.<wbr>org/te2/about/wms/1.3.0/site/</a><br>
                > (Test Dataset Description): "The features are
                organized into layers as shown in<br>
                > table below. The layers may be named in any
                fashion, but must be titled exactly<br>
                > as shown in the table."<br>
                ><br>
                > Please ensure that your service provides the layer
                with the titles from the<br>
                > documentation.<br>
                ><br>
                > Best regards,<br>
                > Lyn<br>
                ><br>
                ><br>
                > Am 01.08.2016 um 10:22 schrieb
                Kaustubh.Chandorkar--- via CITE-Forum:<br>
                >> Hi ,<br>
                >><br>
                >> We are facing issues during OGC test.<br>
                >><br>
                >><br>
                >><br>
                >> We have tried both the sites for ogc test :<br>
                >>  <a moz-do-not-send="true"
                  href="http://cite.opengeospatial.org/teamengine/"
                  rel="noreferrer" target="_blank">http://cite.opengeospatial.<wbr>org/teamengine/</a><br>
                >>  <a moz-do-not-send="true"
                  href="http://cite.opengeospatial.org/te2/"
                  rel="noreferrer" target="_blank">http://cite.opengeospatial.<wbr>org/te2/</a><br>
                >><br>
                >> GeoServer details :<br>
                >>           1. GeoServer version -  2.9<br>
                >>           2. WMS version         - 1.3<br>
                >>           3. Dataset (test dataset): <a
                  moz-do-not-send="true"
                  href="http://cite.opengeospatial.org/te2/about/wms/1.3.0/site/"
                  rel="noreferrer" target="_blank">http://cite.opengeospatial.<wbr>org/te2/about/wms/1.3.0/site/</a><br>
                >><br>
                >><br>
                >><br>
                >> For testing services we are using OGC validator
                test suite - Web Map Service (WMS) version 1.16.<br>
                >><br>
                >> Capabilities Setup :<br>
                >> <a moz-do-not-send="true"
href="http://forums.igenesys.com/geoserverogc/cite/wms?service=WMS&request=GetCapabilities&version=1.3.0"
                  rel="noreferrer" target="_blank">http://forums.igenesys.com/<wbr>geoserverogc/cite/wms?service=<wbr>WMS&request=GetCapabilities&<wbr>version=1.3.0</a><br>
                >><br>
                >>  These are the options I am selecting in the
                validator website:<br>
                >><br>
                >> UpdateSequence Values : Automatic - The
                updateSequence tests will use automatically generated
                updateSequence values<br>
                >><br>
                >> Options : BASIC - Test basic functionality that
                depends on the CITE dataset. This option is required for
                certification.<br>
                >>                QUERYABLE - Test GetFeatureInfo
                functionality that depends on the CITE dataset.<br>
                >><br>
                >> Everytime it asks below questions :<br>
                >><br>
                >> 1. Does the image above depict a large diamond
                that fills the frame?<br>
                >> 2. Does the image above depict a map of the
                Blue Lake vicinity with a surrounding neatline?<br>
                >> 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?<br>
                >> 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?<br>
                >> 5. Does the image above contain an error
                message indicating that the layer requested was not
                defined?<br>
                >><br>
                >> But during these questions there is no image
                displays on the screen.<br>
                >>  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.<br>
                >><br>
                >> Please let us know what to do in this case.<br>
                >><br>
                >> Regards,<br>
                >> Kaustubh<br>
                >><br>
                >> ______________________________<wbr>__<br>
                >> DISCLAIMER<br>
                >><br>
                >> 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.<br>
                >><br>
                >><br>
                >><br>
                >> ______________________________<wbr>_________________<br>
                >> CITE-Forum mailing list<br>
                >> <a moz-do-not-send="true"
                  href="mailto:CITE-Forum@lists.opengeospatial.org">CITE-Forum@lists.<wbr>opengeospatial.org</a><br>
                >> <a moz-do-not-send="true"
                  href="https://lists.opengeospatial.org/mailman/listinfo/cite-forum"
                  rel="noreferrer" target="_blank">https://lists.opengeospatial.<wbr>org/mailman/listinfo/cite-<wbr>forum</a><br>
                >><br>
                > ______________________________<wbr>_________________<br>
                > CITE-Forum mailing list<br>
                > <a moz-do-not-send="true"
                  href="mailto:CITE-Forum@lists.opengeospatial.org">CITE-Forum@lists.<wbr>opengeospatial.org</a><br>
                > <a moz-do-not-send="true"
                  href="https://lists.opengeospatial.org/mailman/listinfo/cite-forum"
                  rel="noreferrer" target="_blank">https://lists.opengeospatial.<wbr>org/mailman/listinfo/cite-<wbr>forum</a><br>
                ><br>
                ______________________________<wbr>_________________<br>
                CITE-Forum mailing list<br>
                <a moz-do-not-send="true"
                  href="mailto:CITE-Forum@lists.opengeospatial.org">CITE-Forum@lists.<wbr>opengeospatial.org</a><br>
                <a moz-do-not-send="true"
                  href="https://lists.opengeospatial.org/mailman/listinfo/cite-forum"
                  rel="noreferrer" target="_blank">https://lists.opengeospatial.<wbr>org/mailman/listinfo/cite-<wbr>forum</a><br>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
        <br clear="all">
        <div><br>
        </div>
        -- <br>
        <div class="gmail_signature" data-smartmail="gmail_signature">
          <div dir="ltr">
            <div>
              <div dir="ltr">
                <div dir="ltr">
                  <div dir="ltr">
                    <div dir="ltr">
                      <div dir="ltr">
                        <div dir="ltr">
                          <div dir="ltr">
                            <div>
                              <div>
                                <div>==</div>
                                <div>GeoServer Professional Services
                                  from the experts! Visit</div>
                                <div><a moz-do-not-send="true"
                                    href="http://goo.gl/it488V"
                                    target="_blank">http://goo.gl/it488V</a>
                                  for more information.</div>
                                <div><span
                                    style="font-size:12.8000001907349px">==</span><br>
                                </div>
                              </div>
                              <div><br>
                              </div>
                            </div>
                            <div>Ing. Andrea Aime <br>
                            </div>
                            <div>@geowolf</div>
                            <div>Technical Lead</div>
                            <div><br>
                            </div>
                            <div><span style="font-size:12.8px">GeoSolutions
                                S.A.S.</span><br
                                style="font-size:12.8px">
                              <span style="font-size:12.8px">Via di
                                Montramito 3/A</span><br
                                style="font-size:12.8px">
                              <span style="font-size:12.8px">55054 
                                Massarosa (LU)</span></div>
                            <div><span style="font-size:12.8px">phone:
                                +39 0584 962313</span><br>
                            </div>
                            <div>fax: +39 0584 1660272</div>
                            <div>mob: +39  339 8844549</div>
                            <div><br>
                            </div>
                            <div><a moz-do-not-send="true"
                                href="http://www.geo-solutions.it"
                                target="_blank">http://www.geo-solutions.it</a></div>
                            <div><a moz-do-not-send="true"
                                href="http://twitter.com/geosolutions_it"
                                target="_blank">http://twitter.com/geosolutions_it</a></div>
                            <div><br>
                            </div>
                            <div>
                              <p><span lang="IT"><font size="1"><b>AVVERTENZE
                                      AI SENSI DEL D.Lgs. 196/2003</b></font></span></p>
                              <p><span lang="IT"><font size="1">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.</font></span></p>
                              <p><span lang="IT"><font size="1"> </font></span></p>
                              <p><font size="1">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.</font></p>
                            </div>
                            <div><br>
                            </div>
                            <div>-------------------------------------------------------</div>
                          </div>
                        </div>
                      </div>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>