[Bug 🐛] Column mapping not working for tree polygons

[Ben-Hodgkiss]

Describe the bug

We've had an example from an LPA who tried to submit their endpoint via Check tool. The endpoint URL is: https://services-eu1.arcgis.com/U9TdzyuSbEnjj4tz/arcgis/rest/services/Forest_of_Dean_Tree_Preservation_Orders/FeatureServer/0.

Upon the Check being ran, it goes to column mapping. This looks correct with geometry matching the WKT field:

However, when the Check results page is shown, i.e. https://provide.planning.data.gov.uk/check/results/jDREtk2EZiUPVfA9DQnwV3/1, the field mapping has moved the mapping to be to the point column.

This is despite selecting polygons when asked at the start of the Check tool. This then creates must fix errors as the geometry is showing as invalid.

Expected behavior

WKT maps to geometry - user can submit endpoint.

[Ben-Hodgkiss]

This can be correctly added via Manage with no field mappings required - as shown in https://manage.planning.data.gov.uk/datamanager/check-results/fkZ2vQHfJY5dsMV3dyeenC

[gibahjoe]

After investigating, I found that the issue was in the async service. It was applying either the column mapping or the geometry-to-WKT conversion, rather than both.

If no column mapping was specified, it would map the geometry to WKT. However, if a column mapping was provided, the geometry was not mapped to WKT, leaving that responsibility to the C&P.

I’ve updated the service to first map the geometry to WKT, followed by applying the column mapping. The PR has been sent.