Skip to content

Allow disabling operator filtering #60

@valpackett

Description

@valpackett

Hi, thanks for the tool!

I wanted to investigate using it here in Buenos Aires, and the obligatory config options

#value of the operator tag for the bus stop nodes used to filter OSM stops
operator=*

#Value of the OSM network tag - used to get relations' data from OSM
network=*

are really problematic for us. We have a huge diversity of bus line operators, 1-2 lines can be its own tiny company, but all data is centrally managed by the city government, and available via open data or the transport API.

So running gtfs-osm-import currently results in a bunch of:

Skipping OSM Stop node ID 4597266560 (ref=null, gtfs_id=null) as its operator tag value (Empresa San Vicente SA) is different than the one specified in the properties file.
Skipping OSM Stop node ID 2658813132 (ref=null, gtfs_id=null) as its operator tag value (Transportes San Juan Bautista) is different than the one specified in the properties file.
Skipping OSM Stop node ID 6746345960 (ref=null, gtfs_id=null) as its operator tag value (Metropol) is different than the one specified in the properties file.
Skipping OSM Stop node ID 4682611591 (ref=null, gtfs_id=null) as its operator tag value (Líneas 76; 99; 106 y 124) is different than the one specified in the properties file.
Skipping OSM Stop node ID 7114753735 (ref=null, gtfs_id=null) as its operator tag value (128 32A 31) is different than the one specified in the properties file.
Skipping OSM Stop node ID 7887847491 (ref=null, gtfs_id=null) as its operator tag value (324 - 129) is different than the one specified in the properties file.
…

It would be nice to have the option to skip the filtering.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions