From e6cae3a994dd43f1c06c793223a533d397863dfa Mon Sep 17 00:00:00 2001 From: Anson Stewart Date: Fri, 2 Feb 2024 15:29:11 -0500 Subject: [PATCH 1/3] Specify limits on analysis page --- docs/analysis/regional.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/analysis/regional.mdx b/docs/analysis/regional.mdx index b5b3fcb..a613b43 100644 --- a/docs/analysis/regional.mdx +++ b/docs/analysis/regional.mdx @@ -47,7 +47,7 @@ If you select a freeform (non-grid) origin pointset, results can be downloadable ### Select destinations and run analysis Select at least one Destination opportunity layer: -* When using grid spatial datasets as destinations, you may specify several grids. They may be of different sizes and shapes (but must all be at the same zoom level). +* When using grid spatial datasets as destinations, you may specify several grids. They may be of different sizes and shapes (but must all be at the same zoom level). In each grid, the number of cells is limited to a maximum of 5 million, and the number of opportunities is limited to a maximum of 2 billion. * When using freeform spatial datasets as destinations in a regional analysis, you can specify only a single layer for now. The maximum number of freeform destination points is 4 million (and the maximum number of freeform origin-destination pairs is 16 million). Grid and freeform destinations cannot yet be mixed. Ensure the list of travel time cutoffs and percentiles will cover the results you want. For example, if you want a travel time matrix to include trips up to 120 minutes, ensure that 120 is included as a cutoff; any travel times exceeding the maximum cutoff will be clipped and recorded as -1. @@ -133,4 +133,4 @@ In the example below, the baseline scenario is shown in blue and an alternative In the baseline, the 10th percentile household (marked by the leftmost vertical line) has access to fewer than 50 thousand jobs, while in the alternative scenario, the 10th percentile household (the second vertical line) has access to more than 141 thousand jobs. The large increase at the lower end of the distribution suggests the alternative scenario could help advance more equitable access to jobs. -Finally, Conveyal displays weighted mean accessibility, which represents the average accessibility experienced by residents (or whatever unit you have weighted by) in the aggregation area. Aggregate accessibility is often bimodal or skewed with a long right tail. In such cases, a substantial majority of the population may experience accessibility values well below the mean, so we generally recommend reporting different percentiles of aggregate accessibility rather than the mean. \ No newline at end of file +Finally, Conveyal displays weighted mean accessibility, which represents the average accessibility experienced by residents (or whatever unit you have weighted by) in the aggregation area. Aggregate accessibility is often bimodal or skewed with a long right tail. In such cases, a substantial majority of the population may experience accessibility values well below the mean, so we generally recommend reporting different percentiles of aggregate accessibility rather than the mean. From 0918e42dbbe6a1096736278b11e94a868359a0bf Mon Sep 17 00:00:00 2001 From: Anson Stewart Date: Fri, 2 Feb 2024 15:31:27 -0500 Subject: [PATCH 2/3] Add limit on number of opportunities to spatial dataset page --- docs/prepare-inputs/upload-spatial-data.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/prepare-inputs/upload-spatial-data.mdx b/docs/prepare-inputs/upload-spatial-data.mdx index dc9484e..e3f6fb7 100644 --- a/docs/prepare-inputs/upload-spatial-data.mdx +++ b/docs/prepare-inputs/upload-spatial-data.mdx @@ -38,6 +38,7 @@ Saved datasets can be displayed as a dot-density map. These maps represent relat ### Troubleshooting Certain limits on spatial uploads help ensure reasonable computation: - The maximum number of grid cells is 5 million. If you encounter this limit, consider cropping the dataset to the region of interest or using a lower zoom level (see the table of approximate geodetic distances and size limits for different zoom levels [here](/analysis/methodology#zoom-levels)). +- The maximum number of opportunities in a layer is 2 billion. - The maximum size of any single feature in the dataset source is 2 square degrees (roughly 20k sq. km. at the latitude of Melbourne or 25k sq. km. at the equator). If you encounter other errors, additional troubleshooting suggestions are [here](/troubleshooting#problems-with-uploaded-files). From 7330dd2391cb0a4324f187d287d762004172a8fb Mon Sep 17 00:00:00 2001 From: Anson Stewart Date: Wed, 28 Feb 2024 15:57:57 -0500 Subject: [PATCH 3/3] Fix typo in pickup delay example Also, update link to R5 source code --- docs/edit-scenario/modifications.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/edit-scenario/modifications.mdx b/docs/edit-scenario/modifications.mdx index d8c9463..bd567f3 100644 --- a/docs/edit-scenario/modifications.mdx +++ b/docs/edit-scenario/modifications.mdx @@ -255,12 +255,12 @@ Custom modification types allow experimenting with certain features that are not This modification type allows modeling on-street modes that serve defined zones with specified service levels, such as shared scooters or ridehail services. It requires an uploaded geojson polygon [data source](/prepare-data) with `id` and `wait` (in minutes) attributes for each feature. For example, within a polygon with `id: "Downtown"` and `wait: 10`, the routing engine would allow people starting journeys in the "Downtown" polygon to wait 10 minutes then proceed by car. Custom JSON settings allow setting different modes, default wait times, designated transit stops for pickup/dropoff, etc. For example, if your uploaded data source has a pickup/drop-off zone polygon (`ArtesiaZone`) and two station zone polygons that are buffers around fixed-route transit stops (`AvalonStation` and `ComptonStation`), you can add this to the custom JSON: ``` -"stopsForZones":{"ArtesiaZone":["AvalonStation","ComptonStation"]} +"stopsForZone":{"ArtesiaZone":["AvalonStation","ComptonStation"]} ``` This setting will prevent point-to-point travel in the Artesia zone, and only allow on-demand rides as first-/last-mile connections to fixed-route transit at the stops in the two specified station zones. -For more details and other custom configuration options, see the [R5 source code](https://github.com/conveyal/r5/blob/v6.6/src/main/java/com/conveyal/r5/analyst/scenario/PickupDelay.java) or contact your support team. +For more details and other custom configuration options, see the [R5 source code](https://github.com/conveyal/r5/blob/v7.1/src/main/java/com/conveyal/r5/analyst/scenario/PickupDelay.java) or contact your support team. #### Road congestion This modification type lets you set a scale factor for car speed within features of a geojson polygon [data source](/prepare-data). It requires an uploaded geojson polygon data source with `scale` and `priority` attributes for each feature. For example, within a polygon with `name: "Downtown"`, `scale: 0.60`, and `priority: 1`, default car speeds in the "Downtown" polygon would be multiplied by 0.60. Custom JSON settings allow overriding the default attribute names, setting a default scaling value to be applied outside of the supplied polygons, etc. For more details, see the [R5 source code](https://github.com/conveyal/r5/blob/v6.6/src/main/java/com/conveyal/r5/analyst/scenario/RoadCongestion.java) or contact your support team.