-
Notifications
You must be signed in to change notification settings - Fork 3
Import local planning authority geometry into pipeline for boundary check #145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Loads relevant geometry in harmonise
Codecov ReportAttention:
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #145 +/- ##
==========================================
+ Coverage 79.54% 79.74% +0.20%
==========================================
Files 67 67
Lines 3588 3619 +31
==========================================
+ Hits 2854 2886 +32
+ Misses 734 733 -1
☔ View full report in Codecov by Sentry. |
Instead of using data from ONS
digital_land/commands.py
Outdated
| lpa_geometry_path = "var/cache/local-authority.csv" | ||
| local_authority_path = "var/cache/local-authority.csv" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've hardcoded these for now, it should be pretty easy to add these as inputs to the pipeline run command, but I'm not sure where that run command is actually triggered
This PR adds functionality to process and load LPA geometry data into the harmonise phase, so it can be used for a custom boundary check in the normalise process. This geometry data will be download during the make init process, using changes found in this PR.
Checking whether an entity lies within its Local Planning Authority boundary only occurs for the brownfield land dataset