December 2025 Release

changelog/2025-12-08.mdx

@@ -0,0 +1,19 @@
+---
+title: December, 2025
+---
+
+import Image from '../components/image'
+
+<Image
+  src='/img/custom-breaks.png'
+  alt='Setting custom breaks for the regional analysis map'
+/>
+
+The latest version of Conveyal (including **v7.5** of the R5 routing engine):
+
+- Accelerates map display for completed regional analysis results ([#986](https://github.com/conveyal/r5/pull/986)) and enables [custom breaks for color bins](/analysis/regional#map-display-options)
+- Adds the ability to download a combined .zip file of all destination layer, threshold, and travel time percentile combinations for a regional analysis
+- Uses requested walking speed (rather than a hard-coded default) when linking origin and destination points to the street network 
+- Improves handling of origins and destinations linked to the same network edge ([#980](https://github.com/conveyal/r5/pull/980)). This change may result in lower accessibility results compared to past versions of R5, especially near long network edges and when using low travel time cutoffs or decay functions.
+- Limits application of custom elevation data to walk and bike modes, not car ([#972](https://github.com/conveyal/r5/pull/972))
+- Enables [new options for sidewalk restrictions](/prepare-inputs#advanced-bundle-configuration), such as prohibiting bicycles or requiring step-free paths ([#976](https://github.com/conveyal/r5/pull/976)).

docs/analysis/regional.mdx

@@ -93,7 +93,21 @@ Upon selecting a completed regional analysis, you will see a screen like the fol
 
 When accessibility results have been computed grid origins, the map will show the number of opportunities accessible from each origin. Any destination opportunity layers, travel time percentiles, and time thresholds specified when you created the regional analysis can be interactively selected.
 
-If dual access results were computed for grid origins, the map will show the time needed to reach the selected threshold number of opportunities from each origin. Any destination opportunity layers, travel time percentiles, and opportunity thresholds specified when you created the regional analysis can be interactively selected. For now, dual access results are not interpolated on the map, so the resolution of the grid is easily seen.
+If dual access results were computed for grid origins, the map will show the time needed to reach the selected threshold number of opportunities from each origin. Any destination opportunity layers, travel time percentiles, and opportunity thresholds specified when you created the regional analysis can be interactively selected.
+
+### Map display options
+
+<Image
+  src='/img/custom-breaks.png'
+  alt='Setting custom breaks for the regional analysis map'
+/>
+
+The Settings panel at the bottom of the map legend provides options for customizing the map display:
+
+- The default map interpolates values between the grid cell results for a smooth looking map. To disable this interpolation, toggle off "Smooth grid cells (interpolate)"
+- To set custom breaks for the color bins, toggle off "Set data breaks automatically" then adjust values in the form below
+- By default, automatic data breaks are calculated using [CKMeans clustering](https://simple-statistics.github.io/docs/#ckmeans), similar to Jenks natural breaks. To use equal interval breaks instead, toggle off "Smart data breaks"
+- "Generate pretty breaks from data" populates the breaks with "nicely-rounded" numbers from [D3.js](https://d3js.org/d3-array/ticks#ticks).
 
 ## Downloading regional results
 For more advanced display and processing of regional accessibility results, you can download the results and open them in GIS software. This allows you to create maps with custom color bins or your own basemap layer, or even [compute custom indicators](/guides/process-raster-results). The download button for a selected regional analysis allows you to save results in the [GeoTIFF](https://en.wikipedia.org/wiki/GeoTIFF) raster format, which is supported by most common geospatial software. Working with the downloaded raster data also allows you to see the raw [grid cells](/analysis/methodology#spatial-resolution) used for analysis, rather than the smoother interpolated results shown in your browser.

docs/prepare-inputs/index.mdx

@@ -46,7 +46,7 @@ If there are no previously created network bundles, or if you want to use update
 
 #### Downloading
 
-Extracts from the global OSM database can be downloaded in [many different ways](https://wiki.openstreetmap.org/wiki/Downloading_data). For most regions, we recommend [Protomaps](https://app.protomaps.com/downloads/osm), a service that provides up-to-date OSM extracts in the required PBF format. If you need a region that is too large for Protomaps, [Geofabrik](http://download.geofabrik.de) provides easy downloads for entire countries and other selected regions. In either case, your extract should cover your entire service area or region, but not extend unnecessarily far beyond it as that may cause computation to stall.
+Extracts from the global OSM database can be downloaded in [many different ways](https://wiki.openstreetmap.org/wiki/Downloading_data). For most regions, we recommend [OSM by the Slice](https://slice.openstreetmap.us), a service that provides up-to-date OSM extracts in the required PBF format. If you need a region that is too large for this service, [Geofabrik](http://download.geofabrik.de) provides easy downloads for entire countries and other selected regions. In either case, your extract should cover your entire service area or region, but not extend unnecessarily far beyond it as that may cause computation to stall.
 
 #### Cropping
 
@@ -134,7 +134,12 @@ Conveyal's routing engine:
 These advanced configuration JSON options are hidden by default and should be modified only after consulting your support team. Once a network bundle is built, these options cannot be changed.
 - `"buildGridsForModes":` Additional on-street modes (other than walk) for which to pre-build large data tables (defaults to `["WALK"]`). Setting this to `["BICYCLE", "CAR"]` will eliminate repeated re-building of these tables when subsequent routing servers start up but require extra time when the network is first built. To keep this extra time reasonable, especially for car tables, minimize the number of transit stops included in the bundle's GTFS feeds. Attempting to build car tables for large regions with more than 24k stops will likely exceed various computation limits in the Conveyal platform, triggering errors.
 - `"modifications":` [Modifications](/edit-scenario) to include permanently in this network bundle (defaults to `[]`). This option is useful if you have modifications or data (such as custom levels of traffic stress or elevations for slope-sensitive routing) that you always want included as part of the baseline network.
-- `"traversalPermissionLabeler":` Which rules to use when setting mode-specific permissions on OSM ways. `"sidewalk"` activates an experimental labeler that restricts walking on most driving ways (useful for networks with complete sidewalks).
+- `"stepFree"`: Whether to exclude pedestrian traversal of ways with highway=stairs tags and nodes with kerb=raised tags. This option should generally be used with detailed sidewalk networks and a TraversalPermissionLabeler that forces use of sidewalks (restricts walking on most driving ways, see below).
+- `"maxIncline"`: Steepest allowable slope for traversal, currently implemented only for pedestrians and with `"traversalPermissionLabeler":"noSteepInclines"` (see below)
+- `"traversalPermissionLabeler":` Which rules to use when setting mode-specific permissions on OSM ways. Available experimental labelers include:
+  - `"sidewalk"`: restricts walking on most driving ways (useful for networks with complete sidewalks)
+  - `"noSidewalkCycling"`: prohibits cycling on sidewalks 
+  - `"noSteepInclines"`: restricts walking on most driving ways and on ways with a custom `incline` value (generally from a special data source such as [OpenSidewalks](https://sidewalks.washington.edu/) or [GATIS](https://dotbts.github.io/BPA/)) that exceeds the specified `maxIncline` value (above)
 
 ## Finalizing network bundle creation