Error: can't get vehicle details by clicking on it in web interface when real time data available

Question

Error: can't get vehicle details by clicking on it in web interface when real time data available

kalon33 opened this issue 3 months ago · comments

Using 0.1.27 version, clicking on vehicles with real time data available in web interface leads to an empty window with no information. Clicking on a vehicle without real time data works properly.

In the logs, that kind of message appears:

[erro][2024-03-25T21:15:17Z+0000][trip_to_connection.cc:29] unable to find trip (id=sncf_ter_OCESN866267F3034497:2024-03-25T00:43:01Z, station=sncf_ter_StopPoint:OCETrain TER-87584052, train_nr=866267, time=2024-03-25 20:25, target=sncf_ter_StopPoint:OCETrain TER-87582668, target_time=2024-03-25 21:54, line=F41+)
2024-03-25T21:15:17Z [VERIFY FAIL] unable to resolve sncf_ter_OCESN866267F3034497:2024-03-25T00:43:01Z, departure 1711398300 at sncf_ter_StopPoint:OCETrain TER-87584052
[erro][2024-03-25T21:15:17Z+0000][dispatcher.cc:128] error executing /trip_to_connection: unable to resolve sncf_ter_OCESN866267F3034497:2024-03-25T00:43:01Z, departure 1711398300 at sncf_ter_StopPoint:OCETrain TER-87584052

Using nigiri.

Thanks for your help.

Felix Gündling · Answer 1 · Tue Mar 26 2024 20:07:42 GMT+0800 (China Standard Time)

In our demo it seems to work: https://europe.motis-project.de
With transitous I also can't reproduce it: https://routing.spline.de

Did you delete your data/nigiri folder when upgrading? Did it work for you before?

Can you post a script like this with a minimal example?

Nicolas Derive · Answer 2 · Tue Mar 26 2024 21:47:53 GMT+0800 (China Standard Time)

Sure, I will look at it after work for the script.

Yes, I removed all modules folders in data folder in order to start from scratch. I'm using Valhalla module, and added routing=true (along lookup, railviz and guesser) in the nigiri section of my config.ini file. I'm using (enabled in file) nigiri, intermodal, address, tiles and valhalla modules, with intermodal.router=nigiri.

Is full address geocoding also planned? Not only stops but house numbers in a street?

Nicolas Derive · Answer 3 · Wed Mar 27 2024 23:46:20 GMT+0800 (China Standard Time)

Sorry, still couldn't found a lot of time at home to prepare this... Here is the config.ini:

server.static_path=web
modules=nigiri
modules=intermodal
modules=address
modules=tiles
modules=valhalla
num_threads=3
intermodal.router=nigiri
server.port=8082

[import]
data_dir=/home/nicolas/new_motis
# Configure timetables
paths=schedule-sncf_ter:data/import/export-ter-gtfs-last
paths=schedule-sncf_intercites:data/import/export-intercites-gtfs-last
paths=schedule-sncf_tgv:data/import/export_gtfs_voyages
paths=schedule-caee:data/import/caee
paths=schedule-normandie:data/import/normandie_latest
paths=schedule-idfm:data/import/IDFM_gtfs
paths=schedule-naq:data/import/gironde-aggregated-gtfs
paths=schedule-bordeauxaero:data/import/bordeaux-aeroport
paths=schedule-blablabus:data/import/blablabus
paths=schedule-bordeaux:data/import/bordeaux
paths=osm:data/merged_otp_cotentin_etroit.osm.pbf
paths=osm:data/sncf_global.osm.pbf

[osrm]
profiles=osrm-profiles/car.lua
#profiles=osrm-profiles/bike.lua
profiles=osrm-profiles/bus.lua
profiles=osrm-profiles/foot.lua

[ppr]
profile=ppr-profiles/default.json

[tiles]
profile=tiles-profiles/background.lua

[nigiri]
# Configure schedule range
first_day=TODAY
num_days=64
lookup=true
railviz=true
guesser=true
routing=true
default_timezone=Europe/Paris
gtfsrt=idfm|http://localhost:5001/STIF
gtfsrt=sncf_ter|https://proxy.transport.data.gouv.fr/resource/sncf-ter-gtfs-rt-trip-updates
gtfsrt=sncf_intercites|https://proxy.transport.data.gouv.fr/resource/sncf-ic-gtfs-rt-trip-updates
gtfsrt=sncf_tgv|https://proxy.transport.data.gouv.fr/resource/sncf-tgv-gtfs-rt-trip-updates
gtfsrt=caee|https://zenbus.net/gtfs/rt/poll.proto?dataset=caee
gtfsrt=bordeauxaero|https://zenbus.net/gtfs/rt/poll.proto?dataset=bordeaux-navettes-aeroport
gtfsrt=normandie|https://pysae.com/api/v2/groups/transdev-cotentin/gtfs-rt
gtfsrt=bordeaux|https://bdx.mecatran.com/utw/ws/gtfsfeed/realtime/bordeaux?apiKey=opendata-bordeaux-metropole-flux-gtfs-rt

[dataset]
link_stop_distance=0
begin=TODAY
cache_graph=true
read_graph_mmap=true
no_schedule=true

but looking at the error, you probably could reproduce using this :

server.static_path=web
modules=nigiri
modules=intermodal
modules=address
modules=tiles
modules=valhalla
num_threads=3
intermodal.router=nigiri
server.port=8082

[import]
data_dir=/home/nicolas/new_motis
# Configure timetables
paths=schedule-sncf_ter:data/import/export-ter-gtfs-last
paths=osm:data/ile-de-france-latest.osm.pbf

[osrm]
profiles=osrm-profiles/car.lua
#profiles=osrm-profiles/bike.lua
profiles=osrm-profiles/bus.lua
profiles=osrm-profiles/foot.lua

[ppr]
profile=ppr-profiles/default.json

[tiles]
profile=tiles-profiles/background.lua

[nigiri]
# Configure schedule range
first_day=TODAY
num_days=64
lookup=true
railviz=true
guesser=true
routing=true
default_timezone=Europe/Paris
gtfsrt=sncf_ter|https://proxy.transport.data.gouv.fr/resource/sncf-ter-gtfs-rt-trip-updates


[dataset]
link_stop_distance=0
begin=TODAY
cache_graph=true
read_graph_mmap=true
no_schedule=true

with http://download.geofabrik.de/europe/france/ile-de-france-latest.osm.pbf as osm source and https://eu.ftp.opendatasoft.com/sncf/gtfs/export-ter-gtfs-last.zip as the GTFS feed corresponding to the GTFS-RT in the file.

Felix Gündling · Answer 4 · Thu Mar 28 2024 22:03:45 GMT+0800 (China Standard Time)

The problem with your configuration is that you're using _ as part of your tag. To distinguish stations from different timetables, MOTIS uses this pattern to create unique station IDs: ${TAG}_${ID} so the _ is already taken as a "special character" and should not be used as part of a tag.

Offtopic:

I think you can simplify your configuration:

remove configuration for ppr and osrm if you're using valhalla and don't list them as active modules (if you use OSRM, the bus profile would only be relevant for the path module)
nigiri flags lookup=true, railviz=true, guesser=true, routing=true are all the default values. You can remove them.
dataset.no_schedule disables the old core. So any other dataset.* options are irrelevant and can be removed.
I would recommend to split the data folder into input (read-only) and data (read-write).

Note that vallhalla module integration is experimental and does not really work well as mentioned in other issues here. Chances are that we'll remove it in favor of a module that just does HTTP requests to an external Valhalla instance.

Edit: config I used to launch for testing

modules=nigiri
modules=intermodal
modules=tiles

intermodal.router=nigiri
server.port=8082
server.static_path=motis/web
dataset.no_schedule=true

[import]
paths=schedule-sncf-ter:export-ter-gtfs-last.zip  # not necessary to unpack
paths=osm:ile-de-france-latest.osm.pbf

[tiles]
profile=motis/tiles-profiles/background.lua

[nigiri]
first_day=TODAY
num_days=64
default_timezone=Europe/Paris
gtfsrt=sncf-ter|https://proxy.transport.data.gouv.fr/resource/sncf-ter-gtfs-rt-trip-updates

Nicolas Derive · Answer 5 · Fri Mar 29 2024 00:13:55 GMT+0800 (China Standard Time)

Thanks a lot for your input @felixguendling . So if valhalla is not working well, the fallback is to re-enable ppr and osrm? Are they working with nigiri?

Felix Gündling · Answer 6 · Fri Mar 29 2024 01:16:22 GMT+0800 (China Standard Time)

I'm working to integrate a new router I developed (it doesn't support turn restrictions yet, but otherwise the basics work). But until then, nigiri+osrm+ppr is the best option.

Nicolas Derive · Answer 7 · Tue Apr 02 2024 04:58:13 GMT+0800 (China Standard Time)

The problem with your configuration is that you're using _ as part of your tag. To distinguish stations from different timetables, MOTIS uses this pattern to create unique station IDs: ${TAG}_${ID} so the _ is already taken as a "special character" and should not be used as part of a tag.

Thanks, that fixed my problem.