Patterns

Patterns belong to routes, and define the physical path along which a vehicle travels. The pattern is created with an outbound, and optionally inbound, definition.

Creating patterns

  1. Click the name of the route that you wish to edit in the services tool panel
  2. Navigate to the patterns tab of the newly opened route panel
  3. Click add to create a new pattern with the default name 'Pattern A'
  4. Click edit pencil to begin the drawing process.
  5. Click to select an existing station, or on any point on the map to create a new station.
  6. Continue adding stops until you have connected the final stop
  7. If the route has an inbound direction, switch to the inbound tab to begin drawing the reverse
  8. Once finished drawing the relevant directions, click save

If a route does not have a return inbound leg and is not a "loop" that starts and ends in the same location, the return leg is considered deadheading. In the case of unidirectional patterns, the deadheading return leg is imputed and added to the total runtime, in order to ensure accurate fleet calculations.

Pattern Operations

pattern add Add Create a new pattern
pattern duplicate Duplicate Create a copy of the selected pattern(s)
pattern export Export Export pattern as GeoJSON, Shapefile or KML
pattern merge Merge Merge multiple patterns, selecting an inbound and outbound pattern
pattern split Split Split a single pattern in two, associating the new pattern with outbound, inbound or both
pattern reverse Reverse Swaps inbound or outbound directions
pattern join Join Create new pattern by concatenating two selected patterns into a longer single pattern
pattern delete Delete Remove selected pattern

Pattern Joining

joining patterns

Patterns can be joined with the pattern join button in the patterns tab of the your chosen route. From here, select the two patterns that you would like to join and then select the starting outbound pattern as the pattern that you would like your new, joined pattern to begin with.

Changes made by joining patterns will be automatically updated on the trips tab.

Editing Station Type

Station settings

By clicking the cog next to a station in your stations list, you can select its kind (station, depot or waypoint).

Unlike stations, waypoints do not cause vehicles to slow down and stop, and dwell times specified in your layer's transport layer properties will not be applied.

Path routing

path routing

Podaris can calculate the route of the path in one of three ways:

  • Following the existing road network (Buses).
  • Following Podaris-drawn infrastructure (Rail/Metro/Hyperloops).
  • Following a set of manually defined coordinates.

When drawing a bus route, by default, the pattern will be solved using the existing road network. When using any other mode, the Podaris-drawn infrastructure is used.

In the case that you want to explicitly define a segment of the pattern, select manual when drawing to draw a line of coordinates for the pattern to follow.

In manual mode, you have the option to override the speed or duration of that segment.

As the underlying infrastructure changes, or stops on the pattern change, the pattern will update to find the new optimal path.

In order to understand how patterns function within service scheduling, you can follow the tutorial on creating scheduled services.

Pattern troubleshooting

Error Meaning

Missing return: assumed deadheading

No return definition has been defined that allows the vehicle to return to the starting station.

Podaris considers the return journey a dead heading and estimates the duration

Pattern uses a layer with routing mode "On-Demand" Creating a pattern which uses a layer with an on-demand (as opposed to Schedule Driven) routing mode will have unintended side-effects.
Pattern references a non-existent station One or more stations this pattern references may have since been deleted.
Unable to solve outbound definition No outbound definition could be found. This could be a result of hidden stops, or missing infrastructure.
Unable to solve inbound definition No inbound definition could be found. This could be a result of hidden stops, or missing infrastructure.