--buildStreet keep skip GTFS data

139 views
Skip to first unread message

Sarah Matthews

unread,
Feb 19, 2021, 1:21:59 AM2/19/21
to OpenTripPlanner Users
Run build for the OTP2, followed the instruction from link below:

Always has message like this:

16:39:48.216 INFO (GraphBuilderDataSources.java:126) Process data sources: .
16:39:48.217 INFO (GraphBuilderDataSources.java:129) Load files:
16:39:48.220 INFO (GraphBuilderDataSources.java:136) - šŸŒ australia-latest.osm.pbfĀ  .Ā  2021-02-15 16:49:31Ā  522.0 MB
16:39:48.221 INFO (GraphBuilderDataSources.java:136) - 🦠 streetGraph.obj  .  2021-02-19 16:02:15  613.8 MB
16:39:48.222 INFO (GraphBuilderDataSources.java:136) - 🦠 graph.obj  .  2021-02-19 16:25:33  614.1 MB
16:39:48.223 INFO (GraphBuilderDataSources.java:141) Skip files:
16:39:48.224 INFO (GraphBuilderDataSources.java:144) - 🚌 google_transit.gtfs.zip  .  2021-02-15 16:43:22  10.2 MB

The plan journey not working with transit data, also there is no address search/auto-complete.

Anyone can help, please?Ā 

Andrew Byrd

unread,
Feb 19, 2021, 4:50:18 AM2/19/21
to Sarah Matthews, opentrippl...@googlegroups.com
Hi,

The purpose of the --buildStreet switch is specifically to skip the transit data and build a graph of the streets only. In the tutorial you linked to, the section containing the command with the --buildStreet switch is intended to explain why you would do this, and gives a series of three commands that would first create a street graph, then add transit data to that street graph, then run a server using the combined graph.Ā 

Are you running these three commands in sequence, as described? What specific command did you run that produced this output?Ā 

Please let us know if there is something confusing about this section, or if you find that it is missing certain information.

Thanks,
Andrew


--
You received this message because you are subscribed to the Google Groups "OpenTripPlanner Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opentripplanner-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/opentripplanner-users/b0485c8e-3cf3-4327-8a2c-22ed034fee64n%40googlegroups.com.

Sarah Matthews

unread,
Feb 21, 2021, 6:42:26 PM2/21/21
to OpenTripPlanner Users
Thanks, change to -build and it works, appreciatedĀ  for the help.

Another question is how can I have address autocomplete or location search? Does this related to the map file I have?
cheers,

Andrew Byrd

unread,
Feb 21, 2021, 10:14:22 PM2/21/21
to Sarah Matthews, opentrippl...@googlegroups.com
Hi,

OTP has a client-server architecture. The client included in OTP2 is essentially an example for debugging and testing, and I wouldn't recommend using it in production. At this point many organizations deploying OTP have their own user interfaces. The search/geocoding functionality is handled by the client (UI) so would be configured differently depending on which UI you use.

I do not personally know as much about the UI development, but the UI you are using is probably this default "test" UI in the src/client/ directory of the repo, and the Geocoder seems to be configured here:
https://github.com/opentripplanner/OpenTripPlanner/blob/dev-2.x/src/client/js/otp/config.js#L176

I realize we don't have much documentation about which UIs are available and how to use them. I hope to enrich this part of the documentation soon with information collected from the developers of these UIs. In short here are the repos I'm aware of: https://github.com/opentripplanner/otp-react-redux is under the OpenTripPlanner Github organization and under active development by IBI Group. It is based on React components available at https://github.com/opentripplanner/otp-ui. HSL Helsinki's UI is at https://github.com/HSLdevcom/digitransit-ui.

If you're going to invest effort in configuring geocoding it might be better to do it within one of these production-oriented UIs instead of the largely unmaintained UI within OTP2 itself.

Hope this helps.

Andrew
> To view this discussion on the web visit https://groups.google.com/d/msgid/opentripplanner-users/a43debc4-b630-430f-b0e4-c50158e37777n%40googlegroups.com.

ęž—å®ēÆ¤

unread,
Jan 31, 2022, 9:42:31 PM1/31/22
to OpenTripPlanner Users
Hi Andrew

I'd like to confirm about your reply.
(Sorry for replay about an old message.)

> The purpose of the --buildStreet switch is specifically to skip the transit data and build a graph of the streets only.

Does that mean OTM2 needs both street data(OSM) and transit data(GTFS)?
If we want to use OTM2 for making trip plan with only transit data (i.e. no need street data), do we have a way to build graph?
(It seems if we don't use street data, it doesn't work fine.)

Regards,

2021幓2月22ę—„ęœˆę›œę—„ 12:14:22 UTC+9 and...@fastmail.net:

Andrew Byrd

unread,
Feb 3, 2022, 6:48:09 AM2/3/22
to ęž—å®ēÆ¤, OpenTripPlanner Users
Hello,

In order to give a more complete response to your question, we discussed this at Tuesday’s OTP2 development meeting. The capability to route with GTFS or Netex but no OSM is already present in OTP2, and several organizations confirmed that they consider an important capability because it facilitates testing. Therefore it will continue to be supported and probably expanded over time.

Currently to use this feature you must route from individual stops or stations, not from geographic coordinates. This is possible via the GraphQL APIs and should also be present in the REST API via the fromPlace and toPlace query parameters, using values with the format feedId:stopId.

We may eventually add the ability to route from geographic coordinates via all the close transit stops without having OSM data. Ā 

Hope this helps,
Andrew

ęž—å®ēÆ¤

unread,
Feb 5, 2022, 10:19:45 AM2/5/22
to Andrew Byrd, OpenTripPlanner Users
Thank you for yourĀ reply.

> Currently to use this feature you must route from individual stops or stations, not from geographic coordinates. This is possible via the GraphQL APIs and should also be present in the REST API via the fromPlace and toPlace query parameters, using values with the format feedId:stopId.

I'll try to use it!

2022幓2月3ę—„(木) 20:48 Andrew Byrd <and...@fastmail.net>:

Jan-Hendrik Hausner

unread,
Feb 8, 2022, 3:58:43 AM2/8/22
to OpenTripPlanner Users
Hey Sarah,

you should use Pelias for an autocomplete search. In OTP itself there is just a nearest station search for the provided stops in gtfs.

With best regards
Henni

Reply all
Reply to author
Forward
0 new messages