Kommentare zu: MapKit, Google Maps, iPhone and Drawing Routes or Polylines

Von: The Navarra Group » Blog Archive » The definitive iPhone MapKit polyline example project

Thu, 01 Apr 2010 21:12:52 +0000

[...] would disappear when the user is performing a zoom action on the map). Nicolas Neubauer later expanded upon Craig’s idea with the idea of hooking into the annotation view’s center property [...]

Von: Nicolas

Nicolas — Sun, 28 Feb 2010 12:11:09 +0000

I’m not a lawyer so I don’t know what exactly Apple is prohibiting. I understand that you are not allowed to draw routes on the internal MapKit Views for navigational purposes. Wherever your routing information comes from. I think OpenStreetMaps offers (free) possibilities to add routing information (and MapViews) to iPhone Applications but I didn’t use those yet so I can’t give you advice.

Von: john

john — Sun, 28 Feb 2010 10:39:42 +0000

Thanks for the article. If Apple & Google prohibits the use of their routinginformation is there any other known source where to get routinginformation from?

Cloudmade is far way too expensive. Would apple accept an app with this kind of route? I think it depends on the “day”. taxometer just submitted an app using this technique. Mhh.

Von: Nicolas

Nicolas — Mon, 08 Feb 2010 14:21:09 +0000

If your “underlying” map view, as you said above, can’t receive touch events, you’re not using the approach I’m describing in the blog post. In my (or Chris) approach you will not put anything above the maps view, you will only insert the routes as annotations and will not intercept any touch events. If you want to intercept touches you might want to use the delegation method for annotations (which I don’t remember currently).
I’d like to give you further advice but I think the basic problem is, that you are putting views above your map view which is (as I stated above in the blog entry) a bad idea if you want to archive fluid zooming and scrolling with animations.

Greetings,
Nicolas

Von: jacobms

jacobms — Thu, 04 Feb 2010 11:58:42 +0000

Hi,
thanks for your quick response

It’s hard to explain, but see the pics below. The black box is the area of the CSRouteView, i.e. also the view that receives the touch events (can’t get the underlying internal map view to receive touches :-/):

Screen #1 – initial view when app starts, my custom detect touch in polygon function works fine as the polygon (the green one) is inside the black area.

Screen #2 – after a couple of zooms the black area suddenly seems to get close to the edge of the polygon (detection still works).

Screen #3 – one more zoom and the polygon is no longer completely covered by the black area and thus doesn’t receive touch-events in the non-black area.

For me I would think the black area should at screen #3 completely surround the screen as it should cover the same area on the map as screen #1.

Hope that explains it?

Best and thanks for your quick response,
Jacob

Von: Nicolas

Nicolas — Thu, 04 Feb 2010 09:55:03 +0000

Hey,

I’m not sure if I fully understand your problem. If your CSRouteView is an MKAnnotationView, setCenter: will be called when you move within the map. Also (I’m not 100% sure about this since it has been quite long) it should be called when zooming so you would want to redraw your route on setCenter: to abuse this as a event-listener.

Hope this helps.

Nicolas

Von: jacobms

jacobms — Wed, 03 Feb 2010 23:26:15 +0000

Hi,
did you ever end up doing an example project? I am having trouble with my CSRouteView (this is from the original code Craig provided) “moving” around when I zoom in. Rather, the physical area on the map covered initially is reduced as I zoom in and I have a feeling this might be what you’re talking about. I tried overriding the setCenter and calling regionChanged (= your initRedraw), but that didn’t help.

Thanks in advance!

Best,
Jacob

Von: Nicolas

Nicolas — Mon, 21 Sep 2009 23:10:16 +0000

Basicly, after having clearified that your MKAnnotationView and MKAnnotation are the same class it shoudn’t matter… But I guess I’ll go over the text again the next days. Looking forward to your project and glad that I could help

Von: Marcel

Marcel — Mon, 21 Sep 2009 21:29:32 +0000

Hi Nicolas

Thanks for the clarification. I just now managed to get it to work!

There are still a number of sentences where you refer to the MKAnnotation instead of MKAnnotationView, but hey, I got it to work, so what

I’ll send you the link as soon as I can.

Cheers
Marcel

Von: Nicolas

Nicolas — Mon, 21 Sep 2009 09:54:54 +0000

Hi Marcel,

I guess I should have read the article again before publishing it. I made a mistake in the line that says “Create your own MKAnnotationView subclass which follows the MKAnnotation Protocol, too.”. In the original version it said MKAnnotation (without the view) twice, which is wrong of course.

What you do is create indeed an MKAnnotation**VIEW** subclass which also is an MKAnnotation itself. This class will get the custom UIView as subview you can draw your route on, this class can have a size of 0×0 (if it doesn’t clip the just mentioned subview). And in this class you will overwrite setCenter:. Make sure you will add this custom MKAnnotationView to the annotations of the MKMapView and also (!) to return itself (as it is the view as well as the annotation) if the delegate get’s asked for it.

Thank you for your feedback. I’m looking forward to seeing your project and really would like to link it here, as is propably will help a lot more than my (a assume a bit cryptic) writing.

Best Regards,
Nicolas