For WFS endpoint, we should always apply a maxFeatures to GetFeature requests

[t83714]

Background

We have this WFS dataset that doesn't work on magda map preview

https://data.gov.au/geoserver/manningham-maternal-and-child-health-centres/wfs?service=WFS&version=1.1.0&request=GetCapabilities

The reason is the GetFeature request below

https://data.gov.au/geoserver/manningham-maternal-and-child-health-centres/wfs?service=WFS&request=GetFeature&typeName=manningham-maternal-and-child-health-centres%3Ackan_37dda99d_83d9_4261_8c5d_c70a5d38cc86&version=1.1.0&outputFormat=JSON&srsName=EPSG%3A4326

will trigger around 2GB download.

Solution

Background

We have this WFS dataset that doesn't work on any TerriaJS map:

https://data.gov.au/dataset/ds-dga-7ded7c00-475a-4c54-aaa6-6b4538eb28ef/distribution/dist-dga-759053f2-7597-4997-84ff-f722af4ca660/details

https://data.gov.au/geoserver/manningham-maternal-and-child-health-centres/wfs?service=WFS&version=1.1.0&request=GetCapabilities

The reason is the GetFeature request below

https://data.gov.au/geoserver/manningham-maternal-and-child-health-centres/wfs?service=WFS&request=GetFeature&typeName=manningham-maternal-and-child-health-centres%3Ackan_37dda99d_83d9_4261_8c5d_c70a5d38cc86&version=1.1.0&outputFormat=JSON&srsName=EPSG%3A4326

will trigger around 2GB download.

Solution

We should always apply a maxFeatures query parameter to GetFeature requests that terriaJS send out.

Currently, latest v8 terriaJS already auto-add maxFeatures query parameter to GetFeature requests.

As we still using an earlier version of terriaJS for map preview, we probably have two options to fix the issue:

• Upgrade to latest terria map v8. We will need to fix the CI release issue as Magda preview is released via CI at this moment.
• Apply the fix on a current version TerriaJs fork.