Web ui for gtfs osm matcher

Purpose of this project

In order to display GTFS stops on the map without doubling ond visual clutter we need to match GTFS stops to OSM stops.

This UI displays matching results in more convenient way.

There are several sets of matched (not matched) stops, with different level of confidence and different ways of improving matching.

My city or country is not on the list

We are looking for new sources of data and going to add them, but please be explicit providing source for a gtfs feed.

Best way if you can give us a direct link to gtfs data and trip updates data.

If possible also provide a link to credentials or license to access data.

You can submit all this information to [email protected] or add an issue to this repository.

Types of matches

To help with data matching you can add GTFS id or code to osm stops. Different regions use different tags to store GTFS stop IDs.

Please take a look what tag is considered appropriate by the local community.

Typical tags are <agency>_ref, gtfs:id, gtfs:stop_id, gtfs:stop_code, etc.

At this moment the quickest way to do so is to use Goto OSM button to open the current view on OSM and use Id or JOSM editor via Edit button to add above mentioned data to OSM stops or create it.

match-id

This stops were matched by GTFS stop ID or Code. That means that one of the osm element tags have exact match with GTFS stop ID or Code. Usually this is some kind of a ref tag.

match-name

This stops were matched by name and type and didn't get into a cluster of matches. Names are getting normalised: Special characters removed, lowercase, diacritics removed, ß converted to ss etc. Names are checked against name elemnt tags. Cluster of matches in this context means that more than one GTFS stop matched to the same OSM element.

separated-clusters

This dataset contains matches that were successfuly separated from clusters. At this moment cluster separation is done by distance.

In general this features considered matched. It's possible that stop matches where separated from the cluster incorrectly. To fix this type of an error add GTFS id or code to osm stop.

transit-hub-clusters

This are clusters which contains one and only one OSM element representing trunsport hub, such as amenity=bus_station, railway=station, etc. and any number of stops or platforms.

many-to-one

This are clusters where multiple GTFS stops were matched to excatly one OSM element.

clusters

This are clusters which the tool was unable to separate.

no-match and no-osm-stops

This two categories are simmilar in that they both contain stops that were not matched to OSM element. But in case of no-osm-stops means that no OSM element of the appropiate type was found at all within 750m (1000m for rail transport) radius.