Menu

#41 'strictOGC' error on any SOS request (2.3.1-RC1)

Done
nobody
2.3.1-RC1 (1)
High
Defect
Ubuntu 14.04
2016-04-12
2016-04-12
No

Installed v2.3.1-RC1 from .tar.gz on Ubuntu 14.04 with Apache WSGI. Setup (PostGIS database setup, creating a New Service etc) went ok. Only on any SOS request (GetCapabilities), via browser or "requests" Poster page, I get this response.

<ExceptionReport xmlns="http://www.opengis.net/ows/1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/ows/1.1 ../owsExceptionReport.xsd" version="1.0.0" xml:lang="en"> <Exception locator="" exceptionCode="NoApplicableCode"> <ExceptionText> 'strictOGC' </ExceptionText> </Exception> </ExceptionReport>

Also when adding a New Procedure for a temperature sensor via web interface using LUGANO example data from the documentation, the webform returns 200 with the same error message 'strictOGC'.

Ok, the SOS is empty, but WA REST shows no errors:
/istsos/wa/istsos/services/<myservice> returns JSON "message": "Informations of service <myservice> successfully retrived" etc

Then installed 2.3.0 the same way and found none of the above problems, could create New Procedure etc.
Only change is that I made the Proxy form empty in 2.3.0, but think I tried that in v2.3.1-RC1 as well at some point.

Related

Tickets: #41

Discussion

  • Milan P. Antonovic

    Thanks Just,
    This is corrected in the trunk..
    Next release will fix this.

     
  • Milan P. Antonovic

    Hi Just,
    Thanks for opening the ticket for this issue.
    I've checked the 2.3.1-RC1 and I saw that a the "strictOGC" param is
    missing from the configurations files.
    in the "service" folder there is the default.cfg file, and in the section
    [getobservation] is missing the "strictOGC" parameter.
    Adding it manually should fix the issue.

    [getobservation]
    strictOGC = False
    correct_qi = 110
    stat_qi = 200
    aggregate_nodata_qi = -100
    default_qi = 100
    aggregate_nodata = -999.9
    maxGoPeriod = 0
    transactional_log = False

    Best regards

    Milan

    PS: If you created also a new instance, there is also a subfolder
    containing a ".cfg" file check also if the paramenter is missing there.

    Il giorno mar 12 apr 2016 alle ore 16:01 Just van den Broecke justb@users.sf.net ha scritto:


    Status: New
    Labels: 2.3.1-RC1
    Created: Tue Apr 12, 2016 02:01 PM UTC by Just van den Broecke
    Last Updated: Tue Apr 12, 2016 02:01 PM UTC
    Owner: nobody

    Installed v2.3.1-RC1 from .tar.gz on Ubuntu 14.04 with Apache WSGI. Setup
    (PostGIS database setup, creating a New Service etc) went ok. Only on any
    SOS request (GetCapabilities), via browser or "requests" Poster page, I get
    this response.
    <ExceptionReport xmlns="http://www.opengis.net/ows/1.1" xmlns:xsi=" &lt;a href=" http:="" www.w3.org="" 2001="" XMLSchema-instance"="">http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://www.opengis.net/ows/1.1 ../owsExceptionReport.xsd" version="1.0.0" xml:lang="en"> <Exception locator="" exceptionCode="NoApplicableCode">
    <ExceptionText> 'strictOGC' </ExceptionText> </Exception>
    </ExceptionReport>

    Also when adding a New Procedure for a temperature sensor via web
    interface using LUGANO example data from the documentation, the webform
    returns 200 with the same error message 'strictOGC'.

    Ok, the SOS is empty, but WA REST shows no errors:
    /istsos/wa/istsos/services/<myservice> returns JSON "message":
    "Informations of service <myservice> successfully retrived" etc

    Then installed 2.3.0 the same way and found none of the above problems,
    could create New Procedure etc.
    Only change is that I made the Proxy form empty in 2.3.0, but think I
    tried that in v2.3.1-RC1 as well at some point.


    Sent from sourceforge.net because you indicated interest in
    https://sourceforge.net/p/istsos/tickets/41/

    To unsubscribe from further messages, please visit
    https://sourceforge.net/auth/subscriptions/

     

    Related

    Tickets: #41

  • Milan P. Antonovic

    • status: New --> Done
     
  • Just van den Broecke

    Yes, I can confirm that setting strictOGC = False in default.cfg fixes the problems. Thanks for the quick action!

     

Log in to post a comment.