Closed ghost closed 7 years ago
Was this a problem in gnaf-loader or upstream? :)
The issue was with the iag-geo/psma-admin-bdys process, which I run after gnaf-loader to finalise the Admin Bdys PG dump file.
Due to the fiddly logic to clean localities along the coastline - if a locality MBR centroid falls outside the locality, it can fail to be added to the display table. These are manually fixed. Any new errors are flagged at the end of the psma-admin-bdys process. I missed Cawley in the list due to lack of coffee!
The locality_bdys table generated by gnaf-loader has no errors.
Good to hear - and now I know you have a boundaries cleaning script that I'm going to be making a lot of use of.
Issue fixed, new dump file uploaded to AWS