Parcel WFS as geojson #156

Status quo

We fetch the parcel WFS as default xml, whilst it supports geojson as well (according to the capabilities document).

Improvement

Adding outputFormat="application/json; subtype=geojson" to the POST XML root element's attributes, we can receive the data as geojson FeatureCollection.

There are two major benefits from this:

json appears to be faster in response (20-40% faster)
json response size is lower (up to 15% lower)
Using xmltodict we already transform a received xml response into a python dict. This step is not needed, if we could receive the desired format directly from the server --> another performance increase

# Status quo We fetch the parcel WFS as default xml, whilst it supports geojson as well (according to the capabilities document). # Improvement Adding `outputFormat="application/json; subtype=geojson"` to the POST XML root element's attributes, we can receive the data as geojson FeatureCollection. There are two major benefits from this: 1. json appears to be faster in response (20-40% faster) 1. json response size is lower (up to 15% lower) 1. Using xmltodict we already transform a received xml response into a python dict. This step is not needed, if we could receive the desired format directly from the server --> another performance increase

Merged in #157

# Merged in #157

Labels Milestones

Parcel WFS as geojson #156

Status quo

Improvement

Merged in #157