New Slice Convention #161
Merged
New Slice Convention #161
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
This PR introduces a new slice convention to the FireAlert, featuring three main updates. It expands old slices, updates the create-postgis-triggers.sql script, and includes an updated geoslice.png. Specifically, slices 1, 7, and 8 have been systematically renumbered to 10, 70, and 80 respectively, to allow for more granular segmentation. Furthermore, slices 2,3,4, 5, and 6 (which normally has large fire volume) underwent a more intricate division, being split into three vertical sub-slices each. This change ensures that the fire-alert detection logic will work seamlessly for previously dense slices.