Route registry rules

Local editors decide which regions use the route registry. Once a region switches to the new route format, it cannot return to the old format

A route is a defined path that a bus regularly follows between designated stops

The registry may include regular passenger routes, staff shuttles with fixed routes, free shopping centre shuttles, established sightseeing routes (such as City Sightseeing), and other routes that meet the definition in item 1.2

Do not enter phrases describing a bus outside regular route service (such as "at the depot", "charter", or "lunch break") as separate routes

Split a route into two separate routes if its number, both terminius, and more than half of its path and/or stops change at the same time. Also split it if the old and new versions share no section of their paths

Fill in all route fields in the region's primary language as used on the site

Fields in sections 2–9 use dated history entries, as in vehicle profiles. When information changes, add a new entry with the relevant dates rather than editing the existing one. Fields in sections 10–15 apply to the route as a whole

In the "Number" field, enter the route number or identifier shown in official documents, such as registries or timetables

A route number may contain digits, letters, special characters, and no more than one space

Letters in a route number may be lowercase or uppercase, depending on the official designation or regional practice. Two routes may differ only in the case of one letter

By default, use the alphabet of the region's primary language for letters in route numbers, unless foreign characters are intentional

Enter a name for every type of route, including city routes, whenever the name is known

The "Name" field should usually contain the route's terminius or its official, widely used name

List only two terminius in the name, even if the official name differs, except as described in item 3.4

For circular routes, use the format "A — B — A", where A is the main terminus and B is a reference point on the loop, such as the most distant stop

Separate the terminius with an em dash surrounded by spaces. The site automatically converts a hyphen with spaces around it to an em dash

For routes that leave a settlement, use settlement names in the "Name" field and add clarifications in parentheses where needed

Put the more populous settlement first unless that conflicts with the route's official name

Begin the name with a capital letter and omit the final period

Use the optional "Remarks" field for a short clarification if users might otherwise struggle to choose between similar routes. Begin with a lowercase letter and omit the final period

If a route runs entirely within one region, list only that region, regardless of where its operators are based

If a route crosses several regions, list only those directly involved in operating it. These are usually the regions where its operators or dispatch facilities are based

Editors may create route groups to suit regional needs. A route history entry may belong to no more than five groups at a time. Route groups are generally separate from operator groups

A route group may represent a route network or the organisation that arranges services. Groups may also classify routes by type, using either an official registry or a locally defined classification

The group's "Information" field must briefly explain how routes are grouped and provide any other necessary details. Begin with a capital letter and omit the final period

Route groups may have previous names, which appear on route pages for the dates when they applied

If a route runs entirely within one location, list only that location, regardless of where its operators are based

If a route crosses several locations, list only those directly involved in operating it. These are usually the locations of its operators or dispatch facilities (up to five at a time)

In the "Facility" field, select every facility serving the route (up to ten at a time)

If a company runs a route as a subcontractor, or is the carrier but does not use its own buses (for example, because it subcontracts the service), you can assign the appropriate status ("Subcontractor" or "No own services") by right-clicking its entry in the "Facility" field while editing

Use the "Since..." and "To..." fields for the first and last dates when a route operated in a particular configuration

Active: the route runs regularly and its most recent trip was within the past month. Seasonal routes also count as active if they last ran within the past year and service is expected to resume

Inactive: the route appears in a registry or other documents but is not currently operating, although service is expected to resume. Routes that have not yet begun operating also fall into this category

Closed: the route has officially closed, or it has not operated for over a month and is unlikely to resume

Public: anyone may use the route. No pass is required, and tickets, where needed, are freely available

Non-public: ordinary passengers cannot use the route. Travel requires a pass or inclusion on a prearranged passenger list

A tracing is a defined variant of a route, usually distinguished by at least one terminus. Variants with the same terminius but different stops count as separate tracings only if they are visibly distinct or can be identified unambiguously from the photo date (except as described in item 12.2)

If the terminius are the same, the outbound and return trips form one tracing unless more than half their stops differ

Tracings that serve the same stops but follow different paths between them are not treated as separate tracings on the site

Temporary route changes, such as those caused by roadworks, are generally not added as separate tracings. An exception may be made for a change lasting more than a month if it is visibly distinct or can be identified unambiguously from the photo date

In a tracing's "Name" field, list the terminius separated by an em dash

If the official language uses a script other than Cyrillic or Latin, enter the name in that language in the "Local name" field

Separate the terminius with an em dash surrounded by spaces. The site automatically converts a hyphen with spaces around it to an em dash

Editors may add an optional stop list when the information is available

Enter the stop list as plain text, one stop per line

For a stop served in one direction only, add "(outbound only)" or "(return only)" after its name

Add a free-form description if needed. Begin with a capital letter and omit the final period

For seasonal routes, it is useful to describe the period of operation in this field