Repository navigation
Draw large polygon sets as raster tiles, with the Boston sample - #50
Merged
Merged
Conversation
688 building footprints of central Boston (about 0.8 x 1.1 km) from the Overture Maps buildings theme (release 2026-10-21.0, ODbL), coloured by height. The grid lays the block out 2 x 2 or 4 x 4 times (up to 11,008 polygons, 119,776 vertices) for load testing; ?camera= and ?grid= fix the view for measurements.
… a tap hit Replaces the tiled copies with the real Overture buildings of 0.8 x 1.1, 1.6 x 2.2 and 3.2 x 4.4 km around Downtown Crossing (605 / 2,827 / 9,467 polygons), so every polygon sits on the building it outlines. A tap highlights the building and shows its name, height and id; a tap that misses says so. ?area= replaces ?grid=.
The data files (public/boston/full/*.bin) are not committed; they are built from Overture and Analyze Boston Parcels 2025.
Parcels are joined (99.6%) with the City of Boston FY2026 Property Assessment on GIS_ID and coloured by its land use code, grouped into eight classes with a legend; only the code is taken from the assessment. While a dataset loads, an overlay over the map says how far it has got: the download with a progress bar, then reading, preparing and drawing.
A parcel shows its id and land use, a building its name, height and Overture id, both their vertex and hole counts. Tapping the map elsewhere closes it.
react-for-arcgis, -azuremaps, -cesium, -deckgl, -googlemaps, -here, -leaflet, -mapkit and -openlayers draw large polygon sets as raster tiles (PolygonTiler); arcgis, azuremaps, cesium, here and mapkit also show marker tiles with upsert / removeById. The Boston pages already ran against these commits, but the parent never recorded them.
Branched from feat/polygons (the Boston sample and the Polygons page). Points js-sdk-core and every react-for-* that tiles polygons at its feat/polygon-tiling, each with develop merged in (hole union, overlay stacking, clear order, geodesic fill, marker drag click fix).
# Conflicts: # js-sdk-core
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
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.
何をするか
多数のポリゴン（既定: 2,000 個以上または頂点 50,000 以上）を、ネイティブの図形ではなくラスタータイルとして描きます（
PolygonTilingOptions/PolygonTiler）。web・Android・iOS で同じ設計です。このリポジトリで変えたこと
feat/polygon-tilingは、ポリゴンのサンプル（feat/polygons: Polygons ページ、ボストンの建物・区画）に develop を merge し、gitlink を js-sdk-core と各 react-for-* のfeat/polygon-tilingに向けたものです（タイル化の無い submodule は develop の gitlink のまま）。develop の取り込み
このブランチは push 済みだったので、rebase せず
origin/developを merge commit で取り込みました。npm ci→ core/react の build →npm test→npm run lint）を親 react-sdk の feat/polygon-tiling で実行: テスト 625 件 pass、lint ok。node scripts/api-surface.mjs check: ok（増えた公開 API はベースラインに追加。削除なし）。マージの順番
この機能は複数のリポジトリにまたがります。js-sdk-core → 各 react-for- → react-sdk（親）* の順にマージが要ります。
PolygonTiler/OverlayStackingを使うので、js-sdk-core が先です。この PR は大きな機能なので、マージするかはレビューのうえで判断してください。
先にマージが要る submodule の PR