Mobile friendly web OTP frontent?

[Marko Burjek]

Does anyone know if there exist working mobile friendly OTP frontend?

I found this https://github.com/OneStopTransport/OpenTripPlanner which is mobile friendlier. But whole code is in spanish.

And OTP.js https://github.com/conveyal/otp.js but it throws errors when I'm trying to run it.

[Andrew Byrd]

Check this out:
https://github.com/CUTR-at-USF/OpenTripPlanner-for-Android
https://play.google.com/store/apps/details?id=edu.usf.cutr.opentripplanner.android

Vreixo González did a bunch work on it last year in a Google Summer of
Code internship. Or are you looking for a cross-platform HTML frontend?

-Andrew

[Marko Burjek]

Thanks. I know about that I was looking more for a HTML frontend.

--
You received this message because you are subscribed to the Google Groups "OpenTripPlanner Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opentripplanner...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Stefan de Konink]

I think it is possible to hookup:

<https://github.com/bliksemlabs/whitelabel/>

Its running at https://1313.nl/ the only change you might have to make is
the geocoder query, it now expects geojson.

Stefan

[Marko Burjek]

This seems to be usefull. Thanks.

[Ricardo Vitorino]

Hello Marko!

On Sunday, 25 May 2014 09:52:59 UTC+1, Marko Burjek wrote:

Does anyone know if there exist working mobile friendly OTP frontend?

I found this https://github.com/OneStopTransport/OpenTripPlanner which is mobile friendlier. But whole code is in spanish.

This application was developed by a Brazilian partner on this big project we're working, and it's a simple prototype. We're aware that it lacks some quality so we welcome patches that improve its front-end and its functionalities :)

Best regards

[Sean Barbeau]

Marko,
Are you aware of the bundled Leaflet-based client for OTP?

I believe this is the current directory in the master branch:
https://github.com/opentripplanner/OpenTripPlanner/tree/master/src/client

That's what we're using as a basis for a mobile browser-friendly front end for a project at our university (work-in-progress):
http://mobullity.forest.usf.edu/

Sean

[Chris Alfano]

Here's a Sencha Touch based mobile UI we're working on in Philly: http://v3.septa.mobi/#tripplanner

Source: https://github.com/JarvusInnovations/SeptaMobi

[Andrew Byrd]

Hi Chris,

I'm just curious, what are you using for a backend for this app? Based
on the URLs I see in the code it doesn't seem to be OpenTripPlanner. Of
course I imagine that you were just suggesting reusing the UI code.

-Andrew

[Chris Alfano]

The backend for this app is a collection of stub scripts that either just forward proxy to another service, or do some minor compositing/caching/trimming of other services to make mobile requests more efficient.

The trip planning endpoint is an unmodified forwarder to opentrips.phl.io and the only other API endpoint the trip planning feature uses is Google Maps' autocomplete API for the start/destination input form.

Outside of trip planning the app uses a mix of real-time status APIs provided by SEPTA (Philly's transit agency) and NEXT-Transit for GTFS data. We originally set out to use OTPs TransitIndex API for GTFS data but the way it provided route/schedule details was really difficult to work with and we gave up on trying to coalesce it into a format resembling the published schedules. NEXT-Transit is an open source server that you can load GTFS data into and it provides a very clean REST API with schedules smoothed out for human consumption.

If any other groups would want to use this UI my company would be interested in spinning out the trip planner feature into a standalone open-source app, or maybe a template app where you can optionally plug in other sections. It would be awesome if we could figure out how to make the schedule browser work from the OTP's TransitIndex API so that section could be included too and ready to work from any OTP instance. Or maybe a new version of the TransitIndex API could be built with some of the smarts NEXT-Transit offers... any volunteers? :)

--
You received this message because you are subscribed to a topic in the Google Groups "OpenTripPlanner Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/opentripplanner-dev/4FgBmyn0rbM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to opentripplanner...@googlegroups.com.

[Marko Burjek]

Thanks everyone It seems I would have to build something myself based on current leaflet.

I first thought to build something completely new but routing input with map is apparently very hard to do on touch devices (especially if you have only one touch tablet), leaflet routing https://github.com/Turistforeningen/leaflet-routing and leaflet routing machine https://github.com/perliedman/leaflet-routing-machine doesn't work. Osrm web interface also. In current leaflet everything works the problem is that widgets cover map and each other on a small screen.

 Although next transit seems very interesting. I'll play a little with it. I could also implement new TransitIndex API to OTP with NEXT-Transit knowledge.

--

You received this message because you are subscribed to the Google Groups "OpenTripPlanner Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to opentripplanner...@googlegroups.com.

[Chris Alfano]

The mobile UI I I linked to is based on leaflet, I'd be interested to hear where it comes up short for your needs as we are interested in putting some more work into it to give it broader appeal as an open-source standalone mobile OSM UI. The backend dependencies could definitely be stripped for a trip planner-only version so it only needs an OSM server.

Chris Alfano

[Marko Burjek]

As a mobile OTP UI it is great. My idea was to find something mobile friendly. So that I could have same website for desktop users and mobile users. Something responsive. Similar to current official leaflet client only more adjusted for small screens and touch support.

I'm beginning to wonder if it is even possible. Because you have one widget for input location and date/time, map to input location and after you get a itinerary you have a path description and you have to show all of that on a small screen in a smart way. I'll see what I will do.

I tried next-transit and I wasn't able to add my GTFS to it. First it took a lot of time to find how to add parameters to app. Then I struggled with import.js and changing a lot of code it started to import GTFS, but then I got and error that tables doesn't exist. Which is completely correct I just can't find how to create them. There is no code in whole app for creating tables.

[Chris Alfano]

It can be made responsive to screen size, we haven't considered any large format layouts yet. FWIW I opened a github issue for it https://github.com/JarvusInnovations/SeptaMobi/issues/3, someone might pick it up at an upcoming Code for Philly hack night.

I've never had to set it up as the developer maintains a Philadelphia instance. It looks like there's a separate project for importing data, did you find that? https://github.com/reedlauber/next-transit-data/issues

If that's what you were using already it would be worth opening a github issue, you might be the first person redeploying it so it would be very valuable to highlight the rough spots for him.

[Marko Burjek]

Great! Thanks!

In desktop mode you can have something layed out as openlayers client or little nicer like https://citymapper.com/london/superrouter?start=51.5150456546981,-0.1544952392578125&saddr=2%20Orchard%20St&end=51.48095527263103,-0.14247894287109375&eaddr=Cringle%20St%20London .

I was using next-transit-data and have added an issue.