stops for location issue

已查看 15 次
跳至第一个未读帖子

kossavot

未读,
2020年6月2日 16:11:222020/6/2
收件人 OneBusAway API
Hi all,
I've got a strange behaviour when I call the stops for location API which I use to convert the user-facing stop code to the actual stop id.
The API works fine for most stops except for a limited subset. In the gtfs stops.txt I've noticed that this limited subset differs from all other stops and the difference is that they have a parent station defined with location_type=0 if that matters.
Now, when I search for a stop belonging to this subset I get no results. Curiously If I searched the same stop by using the parent station (which is not a user-facing stop code) the API returns a result: wrong stop_id but lat,lon,name are right.
Any clue on what's going on here ? What can I do to pinpoint the issue to give you more info ?

Thanks

P.S.
I'm using OBA 2.0 from the master branch.
回复全部
回复作者
转发
0 个新帖子