Repository navigation
Conversation
Port of the android-sdk / ios-sdk street-tree labels. From zoom 16 each visible tree is labelled with its species, placed by a per-road chooser (vertical text above/below the road, horizontal left/right). Each road keeps its previous side while it still places at least two thirds as many labels as the best side, so panning no longer flips labels. Labels are chosen again whenever the camera stops; on the first load, where web maps report no visible region, a box around the centre stands in. `?camera=lat,lng,zoom` opens the page at a given spot.
js-sdk-core#23 adds labelWritingMode and draws tile labels separately; react-for-here#10 fixes the half-size marker tiles on HERE.
Label street trees on the web and keep label sides across pans
Bumps [node-forge](https://github.com/digitalbazaar/forge) from 1.4.0 to 1.4.3. - [Changelog](https://github.com/digitalbazaar/forge/blob/main/CHANGELOG.md) - [Commits](digitalbazaar/forge@v1.4.0...v1.4.3) --- updated-dependencies: - dependency-name: node-forge dependency-version: 1.4.3 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
…-forge-1.4.3 build(deps): bump node-forge from 1.4.0 to 1.4.3
The post-office markers and the weather icon on the marker icons page no longer load their images first; ImageIcon takes the URL and redraws the markers once the image arrives. Needs js-sdk-core feat/image-icon-url.
MapConductor/js-sdk-core#24 lets ImageIcon take an image URL, which the samples now use.
Pass image URLs straight to ImageIcon in the samples
Shape opacity defaults (Circle/Polygon 1, GroundImage 1.0) and InfoBubble following its content and position.
Bump submodules: shape defaults and InfoBubble fixes
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=.
AGENTS.md still said the RN design was deferred and the post-office sample used a fixed scale. The bridge has carried the callback through registerIconScaleCallback since July, and the callback only reaches tiled markers. Also point js-sdk-core at its doc comment fix.
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.
…ippets Fix runnable React example documentation snippets
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.
…ded ran The overlay used to go two frames after the states reached <Polygons>, while the SDK was still preparing the tiles, so the map showed no polygons for a while. Each state now counts itself in onAdded; the overlay goes when the count reaches the number of distinct ids of the shown dataset. Calls from a dataset switched away from are ignored. Points js-sdk-core, js-sdk-react and the MapLibre-family providers at feat/overlay-on-added.
Switching the Downtown area while the polygons were being drawn left the loading overlay up for good: the count was held to the first list's size, and the polygons the new list dropped never report onAdded. Each state now records its id, and the count is redone against every list handed to <Polygons>; an id already on the map counts for the new list, since the SDK calls onAdded again only for a polygon it saw leave.
Fix Mapbox and MapLibre coexistence in demo
Fix Mapbox after Longdo in camera-sync demo
The template's clearOverlays() goes through BaseMapViewController.clearOverlayControllers() like the providers, and its conformance test now runs checkClearOverlaysReachesExtensions(), which fails on the old clearOverlays() (extension marker controller cleared 0 times) and passes now. Needs the js-sdk-core change on fix/clear-strategy.
The template now calls BaseMapViewController.clearOverlayControllers and its conformance test runs checkClearOverlaysReachesExtensions; both landed in js-sdk-core with MapConductor/js-sdk-core#29.
Template: clear registered strategy markers in clearOverlays()
npm 12 prints 'npm pkg get version' as plain text ('<name> <version>') and, with --json, as {"<name>": {"version": "<version>"}}. The workflow parsed the npm 11 shape {"<name>": "<version>"} without --json, so the preview step failed with 'Unexpected token @' after the switch to npm 12 and nothing was published. Pass --json and accept both shapes, failing loudly if neither matches.
Read the package version under npm 12 as well
Move the example to HERE Maps API for JavaScript 3.2
- buildscript classpath (AGP and other build plugins): netty 4.1.140, bouncycastle 1.87, commons-compress 1.28.0, jose4j 0.9.6, jdom2 2.0.6.1, guava 33.7.2 - RN example app runtime: commons-io 2.14.0 (from expo-file-system), proton-j 0.35.0 (from the TomTom SDK's Azure IoT client) - npm: fflate 0.7.5 for @loaders.gl/compression, which pins 0.7.4
T-Mobile / Sprint (pink) and Verizon (red) were too close to tell apart on the map.
Raise vulnerable transitive dependencies to patched versions
Draw Verizon in orange in the antenna sample
On a phone the map stage sat under the page title and two paragraphs, and an open control panel covered most of it; there was no way to see the map alone. - Under 760 px: one line of title (the description stays in the page but takes no room), and a stage that ends at the bottom of the screen. - ControlPanel's title folds the panel. Until it is pressed the width decides in CSS: open on a desktop, folded to its title on a phone; opened there it takes at most 55% of the stage and scrolls. Folding only hides the body, so the controls keep their state. - A full screen button on the stage: the Fullscreen API, or the stage fixed over the page where there is none (iPhone Safari). Escape leaves. Camera Sync keeps its own. - Camera Sync keeps only the selector and the numbers over each of its two maps on a phone.
Fit the samples to a phone screen
Points js-sdk-core and js-sdk-react at the add-progress branches (MapConductor/js-sdk-core#47, MapConductor/js-sdk-react#17).
Brings in MapConductor/js-sdk-core#45 (the endless tile loop after the browser restarts an idle service worker, which crashed antenna-horizons after a few minutes) and #46 (WebGL2 circle tiles).
Point js-sdk-core at the service-worker restart fix
Every sample with <Markers>, <Circles>, <Polylines> or <Polygons> puts up a small "Loading..." dialog between their onAddStart and onAddEnd. It waits 150 ms before showing, so quick lists do not flash it, and does not block the map. The Boston pages keep their own overlay, which already ends once every state is on the map. antenna-horizons uses it instead of its progress line.
js-sdk-core 47f6d0b (MapConductor/js-sdk-core#47, includes the service-worker fix from #68) and js-sdk-react d743b19 (MapConductor/js-sdk-react#17).
Add progress callbacks for Markers/Circles/Polylines/Polygons
MapConductor/js-sdk-core#48: zoomed-in circle tiles read only the blocks round them (Pixel 5a, antenna-horizons: 3.5-5.4 s -> 0.09-0.6 s for 9 tiles).
Point js-sdk-core at circle blocks stored by place
Point js-sdk-core at the merge of #48
Point js-sdk-core at the marker tap fix
Points every published package at its 0.4.1 release commit and syncs the lockfile.
Release 0.4.1
js-sdk-react, react-geojson, react-heatmap and react-marker-clustering now pin com.mapconductor:* 1.4.0 for the 0.4.1 release.
Point the React Native native code at the Android SDK 1.4.0 artifacts
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.
Merges develop into main for the 0.4.1 release.