feat: query & display Flood Risk Zones in PlanningConstraints #2302
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Removed vultr server and associated DNS entries |
jessicamcinchak
commented
Oct 13, 2023
| @@ -23,6 +23,7 @@ const CATEGORY_COLORS: Record<string, string> = { | |||
| "Heritage and conservation": "#EDDCD2", | |||
| Ecology: "#E0EFCC", | |||
| Trees: "#DBE7E4", | |||
| Flooding: "#ECECEC", | |||
There was a problem hiding this comment.
Open to better suggestions than grey here! Easy to adjust later though.
DafyddLlyr
approved these changes
Oct 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes:
flood,flood.zone.1,flood.zone.2andflood.zone.3to the planning constraints check (only adds granular entries iffloodis true, consistent with Article 4 granular variables)I hit two quirks with Planning Data that I've raised with Matt L, and expect to be updated soon on their side. When it is, the dropdown will populate as expected, no extra code changes required (so no need to block initial merge I think!):
flood-risk-zonemetadata (which is used to render the contextual paragraphs in the dropdown)flood-risk-zoneentities (which is used to render the bullet-pointed list in the dropdown)Address in a flood zone for testing: 47, COBOURG ROAD, SOUTHWARK, SE5 0HU