SPAM!

SPAM!

SPAM spam spam spam

spam

Yup, that worked. Thanks.

I tried recreating the shared node (worked) and adding a turn restriction.

Adding the restriction worked, but I couldn't assign the directions it applies to, as no street names appeared in the potlatch menus. They did before. For now, I have left the map without the shared node.

SPAM

They are uploaded, but set to "trackable".

For Agadir, the Bing imagery is often outdated btw.

An onboard satnav will be a disappointment is using or adding to OSM is your goal.

I use Navit for driving navigation (when I cannot use Google nav). OsmAnd is more suited to walking, I think.

OsmAnd has the most features. And the maps have the most detail.

Navit / Zanavi still has the best navigation/routing last time I tested, but the map display is for navigation, not for "human use".

Navdroyd was the first (paid) app to do navigation. Not worth it: maps display is the same as the free Mapdroyd, and navigation routes long distance over secondary roads.

An OSM based router could also refine house numbers by noting the request including number, checking where the person ends up, and guessing that must be the correct location. But how can the initial guess be made acceptable? How can the GPS stay on until the person enters the destination?

I also feel that a road is symbolic. It may or may not match its actual width. If landuse were to accurately follow the road, it would have to overlap anyway or maybe keep a distance.

I have a feeling that getting landuse not overapping with roads makes some sense. But mostly after sidewalks have been added to those streets. And especially then, it will make more sense to use the tooling to "make things right": a park could be a square with 'landuse park' and the roads just overlay on that, the understanding being that there is no greenery when there is road. When the roads have attributes about width and layout, thay would automatically carve that out of the landuse (they do, they render over it normally).

Also look at Osmand, which is better for walking and map viewing (also uses off line vector maps).

Navit (didn't try ZANAvi) is okay for driving. It works, calculates, etc. But does not look pretty.

Google also has software errors that suddenly label streets differently. And the copyright.

Still it is tempting to make notes, and when the notes are not clear, to verify using another map. But usually I am too lazy for street names, tsssk.

SPAM!

I am wondering why the map is not with a mixed license - like how for example the Linux kernel contains GPL code, but also code under other licenses.

Is it that the parts cannot be separated? If they cannot be separated at download time ("please download only the CC licensed bits" vs "download the map that is licensed under ODbL and CC") they cannot be separated now, I'd think.

Het valt reuze mee. Gewoon naar een stukje kaart waarvan je de werkelijkheid kent (eigen buurt) en dan op 'Bewerken' drukken. Klik gewoon op wegen en plaatjes en kijk wat er aan de linkerkant verschijnt. Zolang je niet op 'save' drukt is kan je rustig rondkijken.

I find that editing is becoming harder and harder the more layers are added to the map. Potlatch is not easy to begin with, but the huge amount of data is confusing. It would be useful to have bussons to gery out and disable editing of administrative borders. Similarly, ways and areas could have disable buttons.

I'm missing GPSmid because it does not run on Android. Someone was working on a port and had it running, but it seemed incomplete.

Pity, because there is no program yet on android that combines a track display with offline vector maps.

Did you try gpsmid (gpsmid.sf.net)? I use it for my logging. Not perfect, but it can show you the local osm (vector).