Openstreetmap's doesnt address any of the OP's issues. Having built maps for the past 12 years, I know exactly what of each of those issues are about. The blurry images are underlying base layers that drew first and then probably the upper layer timed out when rendering the tile. The curves are caused by elevation measurements that are incorrect (measuring elevation from a satellite involves bouncing from the ground - when there are structures below, depending on the material, it may go through or bounce differently) or precision problems when generating the elevation grid (very common). The big white thing are clouds, when you buy highly expensive imagery you get them with louds (say 30% cloud blockage) and you need to comnine several images taken a different times, color correct them, and stitch them back to remove it (try to do this for one city and then think about doing it for the entire world). The routes that don't match the pins is weird, but it could be that the snapping point for the routing engine snapped to the wrong street edge (it seems very far though) or that the geocoder and the routing engine use different geocoders (that would be bad). Creating a good mapping product is difficult, but Apple will have something much better in one year.