GTFS Display Map

Adds maps to GTFS Display. Route shapes and stop geometry from your imported feed are drawn with MapLibre GL, over a basemap style you choose.

Features

• A computed geodata field on GTFS rows, and a field formatter that renders it as a map — so a route or a stop can show its own geometry anywhere Drupal renders fields.
• Route shapes drawn from the feed's own shapes.txt, with stop points alongside them.
• A map tooltip view mode you can lay out per bundle, so what appears when someone taps a stop is a display setting rather than a template override.
• One site-wide basemap style URL: change it once and every map follows.

Requirements

GTFS Display 3.x, which in turn requires GTFS Core and GTFS Realtime.

Installation

composer require drupal/gtfs_display_map

Configuration

Administration › GTFS › Displays › Map settings (/admin/gtfs/display/map/settings).

Basemap coverage

The default basemap style is hosted at styles.gtfs.media and currently covers California only. Planet-wide tiles are in progress. Until then, if you are mapping anywhere else, set your own style URL in the module settings — any MapLibre GL style will work, provided the host sends CORS headers.

For live vehicles on top of these maps, and for an embeddable map you can put in another site, see GTFS Display Map RT.

Related modules

• GTFS Core — the entities, the importer and the API everything else reads
• GTFS Realtime — trip updates, vehicle positions and service alerts
• GTFS Display — stop, route and system displays for public screens
• GTFS Display Map RT — live vehicles, and an embeddable map
• GTFS Schedule — readable timetables
• GTFS 511 — feed provisioning from the 511 SF Bay API
• GTFS+ — the GTFS+ extension files

Maintainers

Maintained by tbcs and jpsalter,
supported by FivePaths. These modules run public transit information systems in daily service. Issues and merge requests are welcome, and so are co-maintainers.