OTP Android App
Marcy
For my independent study project this summer, I'm going to be working
on a "generic" OTP Android application with real-time navigation.
Generic meaning it should be able to work with anyone's back-end OTP
server.
I'm thinking we'll need to create a directory of known OTP servers
including the bounds they serve. This way it can select which server
to use based on the user's location. Not sure yet if this directory is
best implemented as a public DB, API, or static info in the
application. Maybe opentripplanner.org could host it?
I'm hoping to borrow some code from other apps - I think LGPL is ok?
Apache? The plan is to commit the code to opentripplanner.org and
maybe get it into the Android Market.
Hope to have something to show by August! Please feel free to send
ideas and advice.
Thanks,
Marcy
Frank Purcell
> "generic" OTP Android application with real-time navigation...I'm hoping to borrow some code from other apps
Exciting stuff. As for resources to build on, maybe Portland's civic
apps (http://www.civicapps.org/apps) has something ... all apps are open
source...and at least one (pdxtrain) is Android. PDX Bus (iPhone) and
OpenMBTA (iPhone) are also oss, with trip planner capability. Seeing
any of these apps (or a new OTP specific app) use OTP would be very
exciting. BTW, my own opinion (not that you're asking) is that ideally
the app would be cross-platform -- the foundations to build browser
based web apps are starting to take shape -- OpenLayers has recently
done a lot of work to improve support for mobile devices, and jQuery
mobile is on it's way -- I've developed a couple of little apps (not
trip planners) that are mobile browser based; key learning is that as of
today, any mobile browser app is not going to be as slick as a native
Android or iPhone app -- but the deployment of said app is so much
better than platform based app ... and it's early days, and things will
get better (plus, http://maps5.trimet.org/cc/m.html and
http://maps5.trimet.org/m.html are there to borrow from if you went this
route :-).
> I think LGPL is ok? Apache?
To stay consistent with OTP's current license, LGPL 3
(http://opentripplanner.org/wiki/FrequentlyAskedQuestions#WhatlicenseisOTPreleasedunder)
seems the way to go...
.
> Please feel free to send ideas and advice.
I've been recently thinking about localizations and translations
(http://opentripplanner.org/wiki/Translation). We currently put
language translations in separate .js files. I'd be interested to see
what form these existing translations take so that they can be reused in
other UI's that are not javascript/browser-based. Maybe your app will
be impetus to act on proposals made last year to use gnu gettext for
localizing our UIs
(http://groups.google.com/group/opentripplanner-dev/browse_thread/thread/28b77325d9b1f789/19794be9d2619b50?pli=1).
Good luck,
Frank
Frank
http://www.onebusaway.org/p/Tools_IPhone.action are also resources...
On May 14, 12:37 am, Frank Purcell <fxpurc...@gmail.com> wrote:
> Hey Marcy,
>
> > "generic" OTP Android application with real-time navigation...I'm hoping to borrow some code from other apps
>
> Exciting stuff. As for resources to build on, maybe Portland's civic
> apps (http://www.civicapps.org/apps) has something ... all apps are open
> source...and at least one (pdxtrain) is Android. PDX Bus (iPhone) and
> OpenMBTA (iPhone) are also oss, with trip planner capability. Seeing
> any of these apps (or a new OTP specific app) use OTP would be very
> exciting. BTW, my own opinion (not that you're asking) is that ideally
> the app would be cross-platform -- the foundations to build browser
> based web apps are starting to take shape -- OpenLayers has recently
> done a lot of work to improve support for mobile devices, and jQuery
> mobile is on it's way -- I've developed a couple of little apps (not
> trip planners) that are mobile browser based; key learning is that as of
> today, any mobile browser app is not going to be as slick as a native
> Android or iPhone app -- but the deployment of said app is so much
> better than platform based app ... and it's early days, and things will
>
> > I think LGPL is ok? Apache?
>
> To stay consistent with OTP's current license, LGPL 3
> .> Please feel free to send ideas and advice.
>
> I've been recently thinking about localizations and translations
> (http://opentripplanner.org/wiki/Translation). We currently put
> language translations in separate .js files. I'd be interested to see
> what form these existing translations take so that they can be reused in
> other UI's that are not javascript/browser-based. Maybe your app will
> be impetus to act on proposals made last year to use gnu gettext for
> localizing our UIs
>
> Good luck,
> Frank
David Turner
> Hi all,
>
> For my independent study project this summer, I'm going to be working
> on a "generic" OTP Android application with real-time navigation.
> Generic meaning it should be able to work with anyone's back-end OTP
> server.
This sounds really awesome!
> I'm thinking we'll need to create a directory of known OTP servers
> including the bounds they serve. This way it can select which server
> to use based on the user's location. Not sure yet if this directory is
> best implemented as a public DB, API, or static info in the
> application. Maybe opentripplanner.org could host it?
We would be glad to host this if you write it. Probably the best thing
to do is to have the app download a list of otp servers periodically --
once a month or so.
Daniel Choi
Hi
I'm the guy who wrote OpenMBTA. I'm interested in integrating OTP.
Where do I start?
Our data is from GTFS data for the MBTA, Nextbus, and a MBTA-specific
real time subway predictions feed.
We put all the data in PostgreSQL and serve it out with Ruby on Rails.
We have an open-source iOS client for iPhone and iPad and a mobile web
version for everyone else, but we are also starting work on an Android
client.
We also want to do cool stuff with PostGIS, which is why (among other
reasons) we switched our backend from MySQL to Postgres.
Dan
On May 14, 3:37 am, Frank Purcell <fxpurc...@gmail.com> wrote:
> Hey Marcy,
>
> > "generic" OTP Android application with real-time navigation...I'm hoping to borrow some code from other apps
>
> Exciting stuff. As for resources to build on, maybe Portland's civic
> apps (http://www.civicapps.org/apps) has something ... all apps are open
> exciting. BTW, my own opinion (not that you're asking) is that ideally
> the app would be cross-platform -- the foundations to build browser
> based web apps are starting to take shape -- OpenLayers has recently
> done a lot of work to improve support for mobile devices, and jQuery
> mobile is on it's way -- I've developed a couple of little apps (not
> trip planners) that are mobile browser based; key learning is that as of
> today, any mobile browser app is not going to be as slick as a native
> Android or iPhone app -- but the deployment of said app is so much
> better than platform based app ... and it's early days, and things will
>
> > I think LGPL is ok? Apache?
>
> To stay consistent with OTP's current license, LGPL 3
> .> Please feel free to send ideas and advice.
>
> I've been recently thinking about localizations and translations
> (http://opentripplanner.org/wiki/Translation). We currently put
> language translations in separate .js files. I'd be interested to see
> what form these existing translations take so that they can be reused in
> other UI's that are not javascript/browser-based. Maybe your app will
> be impetus to act on proposals made last year to use gnu gettext for
> localizing our UIs
>
> Good luck,
> Frank
David Turner
>
> Hi
>
> I'm the guy who wrote OpenMBTA. I'm interested in integrating OTP.
> Where do I start?
First, you'll want to set up an instance of OTP with your GTFS. You can
take a look at the Wiki for some quick introductions:
http://opentripplanner.org/wiki/TwoMinutes
http://opentripplanner.org/wiki/FiveMinutes
Next, you'll take a look at the trip planning API, and start writing
client code.
> Our data is from GTFS data for the MBTA, Nextbus, and a MBTA-specific
> real time subway predictions feed.
>
> We put all the data in PostgreSQL and serve it out with Ruby on Rails.
> We have an open-source iOS client for iPhone and iPad and a mobile web
> version for everyone else, but we are also starting work on an Android
> client.
OTP's trip planner doesn't really support loading GTFS from a database
-- you need the plain GTFS file.
Let us know if you get stuck!
Daniel Choi
--
Sent from vmail. http://danielchoi.com/software/vmail.html
Frank Purcell
Welcome to OTP. Back in December, I started exploring iOS programming
and found OpenMBTA. I really appreciate you open sourcing the
code...and I'm exited to see what you can do with OTP.
Take care,
Frank
Daniel Choi
Thanks Frank. I'm glad to join this google group and look forward to
making useful software with everyone here.