This PR makes the authority name more specific, including the LAD or TA prefix. And since we're changing boundary names, there's new logic to match a GJ scheme to the smallest boundary fully containing it. That also helps backfill previously broken data in the browse page.
After merging this PR, manual deployment steps will be:
[x] Uploading a new all_scheme_data.geojson to Sharepoint where people will find it
[x] Regenerating and uploading random_schemes.geojson to the test bucket
[x] Manually deploying to GCP (since we still don't have service account automation)
I've updated all_schemes_data.geojson in the Sharepoint folder. At your leisure, could you sync past this PR, npm run generate-random-schemes, and replace the file in GCS? Thanks!
345
This PR makes the authority name more specific, including the LAD or TA prefix. And since we're changing boundary names, there's new logic to match a GJ scheme to the smallest boundary fully containing it. That also helps backfill previously broken data in the browse page.
After merging this PR, manual deployment steps will be:
all_scheme_data.geojson
to Sharepoint where people will find itrandom_schemes.geojson
to the test bucket