Getting 404 when querying reverseGeocoding api

[luckyhandler]

I'm using motis 2.0.15 self-hosted.
I generated the API code for Dart with an openapi generator according to the openapi.yaml.

When I try to request this API with my own instance of motis I receive an 404 response .
When I replace the base url with https://europe.motis-project.de/ I receive a response (for some unrelated Italian places and stops - see response in logs at the bottom)

There is no documentation on how motis needs to be configured via the config.yaml any more except this one or do I miss a detailed documentation here?

As there's a difference in using my own base url and https://europe.motis-project.de/ I would guess that it is a configuration issue of the config file. Does anyone spot the issue?

server:
  port: 8080
  web_folder: ui
osm: ./osm.pbf
tiles:
  profile: tiles-profiles/full.lua
  db_size: 1099511627776
  flush_threshold: 10000000
timetable:
  first_day: TODAY
  num_days: 365
  railviz: true
  with_shapes: true
  ignore_errors: false
  adjust_footpaths: true
  merge_dupes_intra_src: false
  merge_dupes_inter_src: false
  link_stop_distance: 100
  update_interval: 60
  http_timeout: 10
  incremental_rt_update: false
  use_osm_stop_coordinates: false
  extend_missing_footpaths: true
  max_footpath_length: 25
  datasets:
    schedule-de-nv:
      path: ./schedule_germany-nv.zip
      default_bikes_allowed: false
    schedule-de-rv:
      path: ./schedule_germany-rv.zip
      default_bikes_allowed: false
    schedule-vgn:
      path: ./schedule_vgn.zip
      default_bikes_allowed: false
street_routing: true
osr_footpath: true
geocoding: false
reverse_geocoding: true

The log for requesting my own instance looks like this:

*** DioException ***:
uri: https://<my own base url>/api/v1/reverse-geocode?place=49.598119%252C11.003645%252C0
DioException [bad response]: This exception was thrown because the response has a status code of 404 and RequestOptions.validateStatus was configured to throw for this status code.
The status code of 404 has the following meaning: "Client error - the request contains bad syntax or cannot be fulfilled"
Read more about status codes at https://developer.mozilla.org/en-US/docs/Web/HTTP/Status
In order to resolve this exception you typically have either to verify and fix your request code or you have to fix the server code.

uri: https://<my own base url>/api/v1/reverse-geocode?place=49.598119%252C11.003645%252C0
statusCode: 404
headers:
Response Text:
null

The log for requesting the demo motis instance looks like this:

uri: https://europe.motis-project.de/api/v1/reverse-geocode?place=49.598119%252C11.003645%252C0
statusCode: 200
headers:
 content-type: application/json
Response Text:
[{type: STOP, tokens: [], name: START, id: START, lat: 0, lon: 0, level: 0, areas: [], score: -10}, {type: STOP, tokens: [], name: END, id: END, lat: 0, lon: 0, level: 0, areas: [], score: -10}, {type: STOP, tokens: [], name: VIA0, id: VIA0, lat: 0, lon: 0, level: 0, areas: [], score: -10}, {type: STOP, tokens: [], name: VIA1, id: VIA1, lat: 0, lon: 0, level: 0, areas: [], score: -10}, {type: STOP, tokens: [], name: VIA2, id: VIA2, lat: 0, lon: 0, level: 0, areas: [], score: -10}, {type: STOP, tokens: [], name: VIA3, id: VIA3, lat: 0, lon: 0, level: 0, areas: [], score: -10}, {type: STOP, tokens: [], name: VIA4, id: VIA4, lat: 0, lon: 0, level: 0, areas: [], score: -10}, {type: STOP, tokens: [], name: VIA5, id: VIA5, lat: 0, lon: 0, level: 0, areas: [], score: -10}, {type: STOP, tokens: [], name: VIA6, id: VIA6, lat: 0, lon: 0, level: 0, areas: [], score: -10}, {type: PLACE, tokens: [], name: Monte Piselli - San Giacomo, id: node/1, lat: 0, lon: 0, areas: [{name: Italia, adminLevel: 2, matched: false, default: false}, {name: Abruzzo, adminLevel: 4, matched: false, default: false}, {name: Teramo, adminLevel: 6, matched: false, default: false}, {name: Valle Castellana, adminLevel: 8, matched: false, default: true}], score: 0}]

@felixguendling any idea?

[felixguendling]

Might be that the config.ini changed was not the one in the data directory that's actually loaded?

Does the data/adr folder look like this?

-rw-rw-r-- 1 felix felix   19928912 Nov 25 21:27 inner_rings_data.bin
-rw-rw-r-- 1 felix felix     333400 Nov 25 21:27 inner_rings_idx_0.bin
-rw-rw-r-- 1 felix felix    7457656 Nov 25 21:27 inner_rings_idx_1.bin
-rw-rw-r-- 1 felix felix    6329792 Nov 25 21:27 inner_rings_idx_2.bin
-rw-rw-r-- 1 felix felix 3131052808 Nov 25 21:27 outer_rings_data.bin
-rw-rw-r-- 1 felix felix    7457656 Nov 25 21:27 outer_rings_idx_0.bin
-rw-rw-r-- 1 felix felix    6329792 Nov 25 21:27 outer_rings_idx_1.bin
-rw-rw-r-- 1 felix felix 7727428184 Dez  9 11:24 rtree_data.bin
-rw-rw-r-- 1 felix felix        112 Dez  9 11:24 rtree_meta.bin
-rw-rw-r-- 1 felix felix          0 Dez  9 11:23 street_segments_data.bin
-rw-rw-r-- 1 felix felix          0 Dez  9 11:23 street_segments_idx_0.bin
-rw-rw-r-- 1 felix felix          0 Dez  9 11:23 street_segments_idx_1.bin
-rw-rw-r-- 1 felix felix 7740069820 Nov 25 21:27 t.bin
-rw-rw-r-- 1 felix felix 7950119076 Dez  9 11:23 t_ext.bin

I would not consider the reverse geocoder in its current form particularly useful. It contains stuff like ATMs but no tags what places are. So I would not recommend to enable it as it's not helpful.

[luckyhandler]

Thanks for the answer, Felix.
Before I used a combination of those requests to get nearby stations and their departures.

  @POST('')
  Future<GeoStationLookupResponse> getStations({
    @Body() required GeoStationLookupRequest request,
  });

  @POST('')
  Future<RailvizStationResponse> getStationTimetable({
    @Body() required RailvizStationRequest request,
  });

Is there still a possibility to do that with the current version?

My idea was to now use the reverseGeocode api in combination with the stoptimes api.

[felixguendling]

there's a parameter for this already in stop times api (radius)

[felixguendling]

to get only stops there's a map stops endpoint

[luckyhandler]

ok, but the stoptimes api requires a stop id
required String stopId
Will check the map api, thanks.

And also I will check the content of the folder and let you know.

[luckyhandler]

The issue was related to my dockerfile

FROM ghcr.io/motis-project/motis:2.0.15

WORKDIR /home/motis # <-- this line was missing and therefore it skipped the COPY process silently

COPY --chown=motis:motis ./osm.pbf /osm.pbf
COPY --chown=motis:motis ./schedule_germany.zip /schedule_germany.zip
COPY --chown=motis:motis ./config.yml /config.yml

WORKDIR /

RUN ./motis import # <-- here it then used the default config.yml, I guess and not mine