fix(home): replace jagged/overlapping barangay boundaries - #15
Merged
Conversation
…gy-preserving source
The previous data/aborlan-barangay-boundaries.json came from
bendlikeabamboo/barangay-boundaries-repository, filtered from its
national barangays.geojson. That whole dataset — raw, enriched, and
the final curated hierarchical output alike — is Douglas-Peucker
simplified per-feature at a flat 0.005 degree tolerance (per its own
README). Independent per-polygon simplification doesn't preserve
shared edges between neighbors, so adjacent barangays' borders drift
apart differently: hence the jaggedness (5-16 vertices per barangay)
and the overlaps/gaps at shared edges.
Swapped to faeldon/philippines-json-maps' per-municipality hires
extract (2023/geojson/municities/hires, PSGC 1705301000, MIT
licensed), simplified with mapshaper -simplify over a merged topology
— shared borders between neighboring barangays stay identical by
construction, so no overlaps. 26-619 vertices per barangay (vs. 5-16
before), 135KB total (vs. 8.6KB) for still-tiny page weight.
Names normalized to data/barangays.json's verified PSA spellings, same
as before. No AborlanMap.tsx changes needed — same FeatureCollection
shape ({name, pcode} properties, Polygon/MultiPolygon geometry).
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
|
Preview deployed: https://betteraborlan-7lixsuds6-jdbhomecillo-projects.vercel.app |
Contributor
Author
|
🎉 This PR is included in version 1.2.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Old boundary source (bendlikeabamboo/barangay-boundaries-repository) is Douglas-Peucker simplified per-feature at flat 0.005° tolerance, independently per polygon — doesn't preserve shared edges, hence the jaggedness and overlaps/gaps at barangay borders.
Swapped to faeldon/philippines-json-maps' per-municipality hires extract (MIT), simplified with mapshaper over a merged topology — shared borders stay identical by construction. 26-619 vertices per barangay (was 5-16), 135KB total (was 8.6KB).
No code changes — same FeatureCollection shape, just better source data. Verified visually in dev.
🤖 Generated with Claude Code