[SoC] GSoC'13 OpenTripPlanner-for-Android Weekly Report #6

Pavel Melnikov positron96 at gmail.com
Tue Jul 30 10:01:24 PDT 2013

Hello Stefan.
Thanks for interest in the project.
Actually I was thinking that anyone on the mail list is getting my weekly
reports, but from now on I'll include you to recipients.
The map part in OpenSurveyor is not started fully yet, I only embedded a
osmdroid's MapVew into my application and it shows a map in a Fragment,
saving its state. Project goals concerning maps have not been started yet,
so it's topic for further work.

Best wishes,

On Tue, Jul 30, 2013 at 11:43 PM, Stefan Steiniger <sstein at geo.uzh.ch>wrote:

> Hi Pavel,
> yep - thanks for your input too.
> I have actually been looking at your project too to see if we can get some
> ideas for the OTP client.
> However, maybe if you start with OSMdroid that may give us some oportunity
> to check out in the future how you got things to work.
> The OTP android client has its own objectives, that are fairly different
> from your client. We need a real good place (landmark) search and the type
> of background map we use is not super important at the moment. Except maybe
> for possible map location errors, since OTP actually uses OSM data to
> create the street-/path graphs. So using OSM background tiles is best.
> Anyway, we will keep looking at your work :)
> So if you want, also send updates to us: Vreixo and me.
> stefan
> Am 29.07.13 09:42, schrieb Pavel Melnikov:
>> Ok, thanks for the info on the problem! I'll start with osmdroid, and if
>> it does not suit, will change to google maps v2.
>> Best wishes,
>>    Pavel
>> On Mon, Jul 29, 2013 at 8:33 PM, Vreixo González <vreixo at gmail.com
>> <mailto:vreixo at gmail.com>> wrote:
>>     I don't think it works without a key and this are the ToS
>>     https://developers.google.com/**maps/terms<https://developers.google.com/maps/terms>.
>> For me are not a big
>>     problem as they let me maintain the application open source compliant.
>>     MapQuest API seems very similar to OSMdroid one, for the code that I
>>     have seen in your link, with the map activity, map view, map
>>     controllers the implementation of MyLocation, etc. The only thing
>>     that I have seeing different is the route manager, but maybe just
>>     the programmers in OTP client took a different approach and
>>     something similar is also present in OSMdroid.  All problems related
>>     to fragments and lifecycle will still be there.
>>     Kind regards,
>>     Vreixo
>>     2013/7/29 Pavel Melnikov <positron96 at gmail.com
>>     <mailto:positron96 at gmail.com>>
>>         Thanks for your reply Vreixo!
>>         Do Google maps work without API key? I do not plan to use Google
>>         tiles and google services at all, but I suspect I'll need to
>>         obtain a key and sign some ToS anyway.
>>         Also, there is a Mapquest maps api
>>         (http://developer.mapquest.**com/web/products/featured/**
>> android-maps-api/documentation<http://developer.mapquest.com/web/products/featured/android-maps-api/documentation>
>> **),
>>         any idea if it's useful?
>>         Best wishes,
>>             Pavel
>>         On Mon, Jul 29, 2013 at 7:59 PM, Vreixo González
>>         <vreixo at gmail.com <mailto:vreixo at gmail.com>> wrote:
>>             Hello Pavel,
>>             I have chose this API because is much newer and offers much
>>             more functionality. OSMdroid API is what was used until now
>>             in the app and is a replacement of Google's API V1 with
>>             almost the same features.
>>             One of the principal advantages for me is that with new API
>>             some operations are much easier and elegant. It has an
>>             automatic MyOverlay layer to display user's position,
>>             markers added and configured in one instruction, the same
>>             for route lines, better controls to move the camera, etc.
>>             This things could be done with OSMdroid API but required
>>             much more code.
>>             This API uses a fragment natively to display the map and
>>             takes care of all lifecycle steps regarding this (no need of
>>             save and restore map state onPause and onResume). The
>>             fragment is much more adecuate to work with it than the old
>>             activity and also is better for future integration with
>>             Action bars and other components.
>>             Also this maps are more nice to see, with the possibility to
>>             tilt, rotate the map and the MyLocation and compass
>>             integrated. Also the possibility to manage indoor mapping is
>>             interesting (in OTP there are some people working on this).
>>             For what I have read people was really waiting for the new
>>             API and has a lot of promissing features that I didn't have
>>             explored yet.
>>             The issues with the keys can provoke same time waste if
>>             you're not lucky but after being configured there are no
>>             more problems and they don't introduce any limitations and
>>             they produce usefull usage statistics.
>>             If you only want OSM tiles is very simple, just set map type
>>             to none and add a TileOverlay with an OSM provider.
>>             Regarding tiles, I will let the two options in
>>             OpenTripPlanner client.
>>             Kind regards,
>>             Vreixo
>> ______________________________**_________________
>> SoC mailing list
>> SoC at lists.osgeo.org
>> http://lists.osgeo.org/**mailman/listinfo/soc<http://lists.osgeo.org/mailman/listinfo/soc>
>>  ______________________________**_________________
> SoC mailing list
> SoC at lists.osgeo.org
> http://lists.osgeo.org/**mailman/listinfo/soc<http://lists.osgeo.org/mailman/listinfo/soc>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/soc/attachments/20130731/3e47a2ae/attachment.html>

More information about the SoC mailing list