Parcel fetcher error #67

Status quo

There are rare cases, where the parcel fetcher does not get a proper response but instead the following reply:

<?xml version="1.0" encoding="UTF-8"?>
<ows:ExceptionReport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ows="http://www.opengis.net/ows/1.1" version="2.0.0" xml:lang="en-US" xsi:schemaLocation="http://www.opengis.net/ows/1.1 http://repository.gdi-de.org/schemas/adv/wfs/1.0/WFS-basic.xsd http://schemas.opengis.net/ows/1.1.0/owsExceptionReport.xsd">
    <ows:Exception exceptionCode="NoApplicableCode" locator="mapserv">
        <ows:ExceptionText>msPostGISRetrieveVersion(): Query error. Error executing SQL. check server logs.</ows:ExceptionText>
    </ows:Exception>
</ows:ExceptionReport>

Interestingly, the same request simply resend will be successful. The responsible team behind the WFS has already been contacted.

Importance

For now this is highly important to fix. We want to provide an internal component for all NatIT applications in the future, where we will be able to run parcel intersections on our own database and return results using JSON. However, this is an undated task and for now we need to find a way to get around this error.

Fix

We should add a check whether the returned result xml is a proper response or one of these exceptions. In case of such an exception we may rerun the request, hoping the error will be gone again.

# Status quo There are rare cases, where the parcel fetcher does not get a proper response but instead the following reply: ```xml <?xml version="1.0" encoding="UTF-8"?> <ows:ExceptionReport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ows="http://www.opengis.net/ows/1.1" version="2.0.0" xml:lang="en-US" xsi:schemaLocation="http://www.opengis.net/ows/1.1 http://repository.gdi-de.org/schemas/adv/wfs/1.0/WFS-basic.xsd http://schemas.opengis.net/ows/1.1.0/owsExceptionReport.xsd"> <ows:Exception exceptionCode="NoApplicableCode" locator="mapserv"> <ows:ExceptionText>msPostGISRetrieveVersion(): Query error. Error executing SQL. check server logs.</ows:ExceptionText> </ows:Exception> </ows:ExceptionReport> ``` Interestingly, the same request simply resend will be successful. The responsible team behind the WFS has already been contacted. # Importance For now this is highly important to fix. We want to provide an internal component for all NatIT applications in the future, where we will be able to run parcel intersections on our own database and return results using JSON. However, this is an undated task and for now we need to find a way to get around this error. # Fix We should add a check whether the returned result xml is a proper response or one of these exceptions. In case of such an exception we may rerun the request, hoping the error will be gone again.

Merged in #69

# Merged in #69

Labels Milestones

Parcel fetcher error #67

Status quo

Importance

Fix

Merged in #69