@karussell Wahrscheinlich (sogar sehr wahrscheinlich ;-) versteh ich den Code nicht ganz, aber Du nimmst dort immer den kleineren Wert von forward-speed und backward-speed, d.h. ich sehe dort jetzt nicht wie die Richtungsabhängigkeit reinkommt?

D.h. ich habe einen way mit - maxspeed: nicht definiert - forward-speed: 50 km/h - backward-speed: 30 km/h

die Routine getMaxSpeed() gibt in jedem Fall 30 km/h zurück, auch wenn in der anderen Richtung eigentlich 50 gefahren werden könnte.

Looks like he/she held the GPS device wrong by 90° ;-)

I’m sorry to say this, but Google does a better work here. It’s all about map generalization - for smaller zoomlevels the map has to reduce the complexity and only show a simplified view.

In your example, Google does this much better than OSM - no need to show buildings at this zoomlevel or any tiny street - it just overwhelms the user.

If you zoom-in on this Google map you see similar details as on OSM.

A glaring example is the world-overview on OSM. Try to find the important cities or country-boundaries on zoomlevel 5 over Europe… and try the same with Google.

I’m a developer of an GPX-recording iPhone app as well - and this would be concerning…

But are you sure? Looking at your devices, one is a 3GS (very old, old GPS) and the other one is the iPhone 5 (quite new, GPS is even GLONASS compatible).

Also if you leave the 3G connection on - it helps to bring down the GPS-fix time, so accuracy might be improved as well.

Using my own devices I just found out, the iPhone 5 has much better GPS accuracy than older devices - just because the GPS chip is better.

It would be interesting to know if you reverse the test (3GS with 3G, 5 offline). I would expect the 5 to be slightly worse but not that much.

That’s the “problem” with OSM, relations and multipolygons are not that easy to produce for a novice user.