geocoder in Android app works less often than in web/server OTP

[EdHillsman]

Entering "Lib" (without the quotation marks) in the destination box of the server version of OTP will return "LIB" (without quotation marks) and a destination pin on the USF library just east of Leroy Collins. Doing this in the Android version yields a message box "Geocoder Results Sorrty, the address returns no geographical location". While double-checking this in the server/web version, I noticed that sometimes it finds the LIB and sometimes says it can't but puts a pin there and routes correctly anyway. So it may be that there is some kind of server error as well.

[ktran9]

Ed,

Geocoder in OTP Android is independent of the web/server OTP. Those building initials that work on the web USF OTP instance are manually coded. If we'd like similar functionalities for the Android app, we need to customize it for USF OTP instance as doing this may screw up the geo location when the selected server is NOT Tampa.

[EdHillsman]

Hi Khoa,

OK, thanks for letting me know.

Also, for what it's worth, this week someone posted the GTFS for the Albuquerque bus system on GTFS-X. I'm not 100% sure it was done officially through the transit agency, because the person who posted it also posted one for a transit agency in Santa Cruz, California. But I've snagged a copy to work with once I get settled in out there.

How is your trip going? How is Vietnam?

Ed

-----Original Message-----
From: Khoa Tran [mailto:reply@reply.github.com]
Sent: June 27, 2012 11:11
To: Hillsman, Edward
Subject: Re: [OpenTripPlanner-for-Android] geocoder in Android app works less often than in web/server OTP (#2)

Ed,

Geocoder in OTP Android is independent of the web/server OTP. Those building initials that work on the web USF OTP instance are manually coded. If we'd like similar functionalities for the Android app, we need to customize it for USF OTP instance as doing this may screw up the geo location when the selected server is NOT Tampa.

---

Reply to this email directly or view it on GitHub:
#2 (comment)

[barbeau]

I'm closing this ticket because this is a subset of a larger issue of supporting local geocoding, versus the current global geocoding in the app. The new ticket for this issue is #19