Skip to content

chore(deps): update dependency ol to v10.11.0 - #14

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/ol-10.x
Open

chore(deps): update dependency ol to v10.11.0#14
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/ol-10.x

Conversation

@renovate

@renovate renovate Bot commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
ol (source) 10.8.0 → 10.11.0 age confidence

Release Notes

openlayers/openlayers (ol)

v10.11.0

Compare Source

10.11.0

The 10.11 release improves styling, raster data and OGC service support, and makes the library leaner to load. The highlights are

  • Canvas styles now evaluate the color and array operators, and interpolate mixes colors in sRGB on both the Canvas and WebGL renderers; a new interpolate-hcl operator keeps the perceptual gradient
  • ol/source/Raster gains basic data tile support, and the GeoZarr source can visualize generic n-D datacubes and accepts storeOptions for headers and credentials
  • WMTS sources no longer derive their extent from the tile matrices, so layers that cover a wider area at low zoom levels are no longer cut off
  • Tiles that the current view no longer needs are dropped from the queue, and the WebGL text overlay worker is loaded on demand
  • The VectorImageLayer gets crisp rendering on rotated views, with rotated text and point symbols
  • New wrapX option for getPixelFromCoordinate and getCoordinateFromPixel, and projection options for the WKT format
  • Fixes for RTL text along lines, nested WFS 2.0 feature collections, empty GeoJSON coordinate arrays, and MouseWheelZoom target cleanup
Upgrade notes
Fixed GeoJSON parsing of geometries with empty coordinate arrays

Previously, a GeoJSON geometry with an empty coordinates array (e.g. {"type": "Point", "coordinates": []}) produced a geometry with an empty coordinates array. We have now changed this to match the GeoJSON spec's recommendation to treat such geometries (except GeometryCollection) as null geometries. This change should not affect application code, unless it had special handling for geometries with empty coordinates arrays.

Fixed: interpolate mixed colors differently on the Canvas and WebGL renderers

The ['interpolate', ...] operator interpolated colors in the Hue-Chroma-Luminance space on
the Canvas renderer, but component-wise in sRGB on the WebGL renderer. The same style
produced different gradients depending on which renderer drew it, and neither behaviour was
documented. Both now interpolate in sRGB.

Gradients built with interpolate over colors will look slightly different on the Canvas
renderer. To keep the previous appearance, use the new interpolate-hcl operator:

// Before
const style = {
  'fill-color': ['interpolate', ['linear'], ['get', 'value'], 0, 'red', 1, 'green'],
};
// After - to keep the perceptual gradient
const style = {
  'fill-color': ['interpolate-hcl', ['linear'], ['get', 'value'], 0, 'red', 1, 'green'],
};

interpolate-hcl is only supported by the Canvas renderer for now.

With the ['interpolate', ...] operator, channels now keep their fractional part, so operations
applied on top of an interpolated color are more accurate. Code reading back a color from an
evaluated style may now see a fractional channel.

The WMTS tile grid extent is no longer calculated from the tile matrices

optionsFromCapabilities now only uses an advertised BoundingBox as the tile grid's
extent, and tileGrid.getExtent() returns null when none is advertised. Tile requests
are limited by the advertised tile matrix sizes and TileMatrixSetLimits instead, so
layers that cover a wider area at low zoom levels than at high ones are no longer cut off.

wrapX from optionsFromCapabilities is based on the tile matrix

The world is now wrapped when the first tile matrix spans exactly the width of the
projection's extent, instead of when the layer's WGS84BoundingBox covers the whole world.
Sources that cover only part of the world on a world spanning tile matrix set - e.g. a
national basemap on GoogleMapsCompatible - are now configured with the wrapX option set
to true. If that's undesired, wrapX needs to be overridden to false.

// Before
new WMTS(optionsFromCapabilities(capabilities, {layer: 'my-layer'}));
// After - to keep the layer in a single world copy
new WMTS({
  ...optionsFromCapabilities(capabilities, {layer: 'my-layer'}),
  wrapX: false,
});

The Layer's WGS84BoundingBox is no longer used, because the WMTS specification allows
it to be approximate.

List of all changes

See below for a complete list of features and fixes.

Dependency Updates

v10.10.0

Compare Source

10.10.0

The 10.10 release brings improvements throughout the library — from tile and vector rendering to sources, formats and interactions. The highlights are

  • Text support in the WebGL vector renderers, plus stale tile handling for WebGL tile layers
  • Smoother tile rendering: instead of clipping and redrawing full tiles, only the remainders of lower zoom levels are drawn
  • WMTS and OGC tile grids now honor the advertised tile matrix set limits, so no tiles are requested outside a layer's data extent
  • GeoZarr gains selection of non-spatial dimensions, e.g. for time series
  • Text along lines honors offsetX and is split into graphemes, so ligatures are no longer cut apart
  • Fixes for the Modify interaction's tracing, vector tile resolutions, decluttering z-index order, and text rendering of long lines

Upgrade notes

Usage of Intl.Segmenter

TextPath now relies on Intl.Segmenter.
For support of very old browsers (e.g. Firefox before version 125),
a polyfill is available: https://formatjs.github.io/docs/polyfills/intl-segmenter/.

Deprecation of ol/source/BingMaps

Bing Maps for Enterprise is being retired on June 30th, 2028. The BingMaps source
has been deprecated. Use ol/source/ImageTile with the Azure Maps tile API instead.
See the azure-maps example for guidance.

// Before
new BingMaps({
  key: 'YOUR_BING_MAPS_KEY',
  imagerySet: 'RoadOnDemand',
})

// After
new ImageTile({
  url: `https://atlas.microsoft.com/map/tile?subscription-key=YOUR_AZURE_MAPS_KEY&api-version=2.0&tilesetId=microsoft.base.road&zoom={z}&x={x}&y={y}&tileSize=256`,
  attributions: `© ${new Date().getFullYear()} TomTom, Microsoft`,
})
createFromCapabilitiesMatrixSet now respects TileMatrixSetLimits

When a matrixLimits array is passed to createFromCapabilitiesMatrixSet, the returned
tile grid will now restrict tile requests to the MinTileRow/MaxTileRow/MinTileCol/MaxTileCol
bounds advertised for each zoom level. Previously those bounds were ignored and the full
matrix extent was used, causing tile requests outside the layer's data extent.

If you were passing matrixLimits only to filter zoom levels and relied on the full matrix
range being loaded at each level, you can omit the matrixLimits argument or pass an empty
array to restore the previous behavior.

List of all changes

See below for a complete list of features and fixes.

Dependency Updates
  • chore(deps): bump pbf from 5.1.0 to 5.1.2 in the production-minor-patch group across 1 directory (by @​openlayers in #​17566)
  • chore(deps): bump websocket-driver from 0.7.4 to 0.7.5 (by @​openlayers in #​17563)
  • chore(deps): bump the actions group with 2 updates (by @​openlayers in #​17567)
  • chore(deps): bump github/codeql-action from 4.36.2 to 4.36.3 in the actions group (by @​openlayers in #​17555)
  • chore(deps-dev): bump the development-minor-patch group with 3 updates (by @​openlayers in #​17557)
  • chore(deps): bump earcut from 3.1.0 to 3.2.3 in the production-minor-patch group (by @​openlayers in #​17558)
  • chore(deps-dev): bump the development-minor-patch group across 1 directory with 8 updates (by @​openlayers in #​17554)
  • chore(deps): bump earcut from 3.0.2 to 3.1.0 in the production-minor-patch group (by @​openlayers in #​17549)
  • chore(deps-dev): bump the development-major group with 2 updates (by @​openlayers in #​17547)
  • chore(deps): bump actions/checkout from 6.0.3 to 7.0.0 in the actions group (by @​openlayers in #​17541)
  • chore(deps-dev): bump the development-security group across 1 directory with 2 updates (by @​openlayers in #​17534)
  • chore(deps-dev): bump sinon from 21.1.2 to 22.0.0 in the development-major group across 1 directory (by @​openlayers in #​17510)
  • chore(deps-dev): bump tmp from 0.2.4 to 0.2.7 in the development-security group across 1 directory (by @​openlayers in #​17496)
  • chore(deps-dev): bump the development-minor-patch group across 1 directory with 15 updates (by @​openlayers in #​17533)
  • chore(deps): bump the actions group across 1 directory with 2 updates (by @​openlayers in #​17532)
  • chore(deps): bump pbf from 4.0.1 to 5.1.0 in the production-major group across 1 directory (by @​openlayers in #​17521)
  • chore(deps-dev): bump webpack-dev-server from 5.2.3 to 5.2.4 in the development-security group across 1 directory (by @​openlayers in #​17485)
  • chore(deps-dev): bump fast-uri from 3.0.2 to 3.1.2 in the development-security group across 1 directory (by @​openlayers in #​17484)
  • chore(deps-dev): bump the development-minor-patch group across 1 directory with 11 updates (by @​openlayers in #​17481)
  • chore(deps): bump zarrita from 0.7.2 to 0.7.3 in the production-minor-patch group (by @​openlayers in #​17480)
  • chore(deps): bump the actions group with 2 updates (by @​openlayers in #​17477)
  • chore(deps-dev): bump ip-address from 10.1.0 to 10.2.0 in the development-security group across 1 directory (by @​openlayers in #​17475)
  • chore(deps-dev): bump the development-minor-patch group with 2 updates (by @​openlayers in #​17470)
  • chore(deps): bump zarrita from 0.7.1 to 0.7.2 in the production-minor-patch group (by @​openlayers in #​17471)
  • chore(deps): bump github/codeql-action from 4.35.1 to 4.35.2 in the actions group (by @​openlayers in #​17460)
  • chore(deps-dev): bump the development-minor-patch group with 6 updates (by @​openlayers in #​17461)
  • chore(deps-dev): bump the development-minor-patch group across 1 directory with 10 updates (by @​openlayers in #​17458)
  • chore(deps): bump geotiff from 3.0.5 to 3.1.0-beta.0 in the production-minor-patch group (by @​openlayers in #​17450)
  • chore(deps-dev): bump marked from 17.0.6 to 18.0.0 in the development-major group (by @​openlayers in #​17448)
  • chore(deps): bump the actions group with 2 updates (by @​openlayers in #​17447)
  • chore(deps): bump protocol-buffers-schema from 3.6.0 to 3.6.1 in the production-security group across 1 directory (by @​openlayers in #​17443)
  • chore(deps-dev): bump dompurify from 3.3.3 to 3.4.0 in the development-security group across 1 directory (by @​openlayers in #​17441)

New Contributors

Full Changelog: openlayers/openlayers@v10.9.0...v10.10.0

v10.9.0

Compare Source

Summary

In the 10.9 release, GeoZarr and GeoTIFF support saw major improvements — including multi-group band support, per-band metadata, and more efficient tile loading. WebGL rendering precision and performance were enhanced, and several vector rendering, hit detection, and trackpad zoom interaction issues were resolved.

What's Changed

New Contributors

Full Changelog: openlayers/openlayers@v10.8.0...v10.9.0

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants