Modifications can be grouped by project and scenario, and different projects and scenarios can be compared against each other in analysis mode, giving you flexibility on how to use them. Depending on your use cases, different approaches may make sense.
If one user will be responsible for analyses in your region, involving a relatively small number of modifications, we recommend doing your work in one project and assessing the impact of different combinations of modifications by creating and using scenarios within that project.
If multiple users will be involved in editing scenarios, or if you want to assess more than 10 different combinations of modifications, which would make the list of scenarios annoyingly long, we recommend dividing the modifications among different projects. For example, one team member could code rail scenarios in Project A, another team member could code bus scenarios in Project B. Modifications can be imported between projects that use the same GTFS bundle; in this example, modifications from the two projects could combined in a third Project C.
Toggling display of modifications¶
In the list of modifications on the initial view in editing mode, clicking the title of a modification will open it and allow you to edit it. To control whether each modification is displayed on the map, click
Stops and segments representing modifications are displayed on the map, using different colors to indicate their state relative to the baseline GTFS:
- Blue: Added trip pattern
- Red: Removed trip pattern
- Purple: Changed timetable (e.g. modified frequency, speed, or dwell time)
- Gray: Unchanged (alignment is unchanged but the trip pattern is effected somehow, e.g. Reroute)
Projects start with only a “Default” scenario (plus a locked Baseline in which no modifications can be active). You can create additional scenarios expanding the list of scenarios, clicking the create button, and entering a name.
When the Scenario list is expanded, options next to each scenario allow you to:
the modifications active in the scenario
the scenario (not available for baseline or default scenario)
To see options for exporting scenarios from the top of the editing panel, click
A panel will then be shown with multiple options to download or share the scenarios in your project:
- Raw scenario (.json) all scenario details
- New alignments (.geojson) alignments of add-trip modifications
- New stops (.geojson) new stop locations created in the scenario
- Summary Report a summary of all modifications in a scenario, for printing or reference. Keep in mind that some browsers may not print more than 30 pages or so of a long report.
To import modifications from another project or a shapefile, click
From another project¶
Occasionally, you may want to copy all of the modifications from one project into another. This may be useful to make a copy of a project, or to combine modifications developed by different team members into a single project (for instance, one team member working on rail changes and another on bus changes).
To do so, select a project in the upload/import panel and click
If you choose a project associated with the same GTFS bundle, all modifications will be imported; when there are multiple scenarios, the scenarios in the project being imported will be mapped directly to the scenarios in the receiving project (i.e. modifications in the first scenario will remain in the first scenario in the new project).
If you choose a project associated with a different GTFS, bundle, only add-trip modifications will be imported.
In general, it is best to create all modifications directly in Conveyal Analysis as it allows full control over all aspects of transit network design. However, on occasion, it may be desirable to import modifications from an ESRI shapefile. If you have a shapefile containing lines, you can upload it to Conveyal Analysis and have it turned into a set of Add Trips modifications. To do so from the upload/import panel, click
Then, after selecting and importing a zipped shapefile, you will see the following:
There are several fields that must be filled in, corresponding to attributes (columns) in the Shapefile:
- Name of each modification (e.g. route id).
- Speed (in km/h)
- Headway (in minutes)
Finally, as Shapefiles only contain the route geometry and not the stop locations, stops can be created automatically at a specified spacing. The generated stop positions may be individually edited after import, for example to place a stop at a major transfer point.
Manually edit raw modifications (beta)¶
By clicking on “Customize modification” in the details pane for any modification, advanced users can copy, paste, and edit its raw JSON data.