Repository navigation
Draw large polygon sets as raster tiles, with the Boston sample - #118
Merged
Merged
Conversation
A grid of hexagons registered with one Polygons(states) call, with buttons to add and remove rows and to replace every state with a new fill.
The same Overture Maps extract as the React sample (central Boston, 688 buildings, ODbL), coloured by height, with 2 x 2 and 4 x 4 copies for load testing. The camera and grid extras fix the view for measurements.
… a tap hit Same data and behaviour as the React sample. Every tap is also logged under BostonTap (seq, id, map-click position), which is how hit testing is checked from outside. The area extra replaces grid.
About 100,000 polygons each, read from the app's external files directory (too large for the APK; push them with adb, see BostonData.kt). Same binary format as the React sample. `data` (downtown, buildings or parcels) joins `camera` and `area` as an intent extra.
Same as the React sample: parcels coloured by land use with a legend (the label is "<GIS_ID>|<land use>"), an overlay saying how far reading, decoding, building the states and drawing have got, and the tapped polygon's data in an InfoBubble at the tap, closed by tapping the map elsewhere. The stats also give the time to the second frame after the list reached Polygons().
Also points android-sdk-core, android-sdk-compose and the providers at their feat/polygon-tiling (compose: feat/polygons), each with develop merged in. Until now this branch's gitlinks still named develop's commits.
# Conflicts: # android-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: ポリゴンのサンプル（Polygons ページ、ボストンの建物・区画）。develop を merge し、gitlink を core / compose（feat/polygons）/ 各プロバイダの新しい先頭に向けました（それまで gitlink は develop の commit のままでした）。develop の取り込み
このブランチは push 済みだったので、rebase せず
origin/developを merge commit で取り込みました。testDebugUnitTest: core 350 件ほか全部 pass（OMM は develop から引き継いだ 1 件の失敗のみ。android.util.Log.isLoggableがテストでモックされていない）。apiCheck: 全モジュール ok（増えた API はベースラインに追加）。マージの順番
この機能は複数のリポジトリにまたがります。android-sdk-core → android-sdk-compose（feat/polygons）→ 各 android-for- → android-sdk（親）* の順にマージが要ります。
この PR は大きな機能なので、マージするかはレビューのうえで判断してください。
先にマージが要る submodule の PR