Changes to Trip Planner API's

[Marcie]

@phelum

nd according to the documentation the only sf_type now accepted is ““any”. Previously I could specify “stop” as the sf_type which was sensible because I’m only interested in stops. Now the search results are littered with a multitude of irrelevant entries (e.g. type street or suburb or poi). Yes, I can trawl through the replies and ignore all locations that aren’t “type: stop” but it does mean I can’t restrict the size of the reply as I could before because if say I only wanted 10 locations (type stop) in the reply now the reply might only contain one “type: stop” entry and the rest have an unwanted type. Is there any way I can specify that I only want locations of a certain type ?

If I try to search for names with “sf-type=stop” I get an error message “stop invalid” which implies to me that I can’t specify “sf_type=stop”. However, if I try to specify “sf_type=suburb” or “sf_type=street” I still get the error “stop invalid” whereas I would expect “suburb invalid” or “street invalid” in these cases.

Also, the search can return strange results. If I search for “turr” or “turram” I get a list of Turramurra entries as expected. But if I search for “turra” I get no results except for a BROKER error message “any - input uniquely verified”.

Finally, if I search for “zturrzz” or other entries such as “yzturrzzz” I still get the Turramurra locations in the reply. This doesn’t seem quite right to me.

I’m hoping these problems are just due to some upgrade in progress because the stop_finder

Hi Steven, thank you for your message.

Yes the Trip Planner API has been through an upgrade as there has been changes in the back end- see here.

We have had similar feedback and have sent this back to the team. They are awaiting feedback from their vendor.

I will respond when we get an answer.

Thanks, Marcela