"free" Navigator 10 by mapfactor.com ... uses OSM data

Idea: move the “init bar status” (blue line on the bottom of the screen when you lauch the Navigator10) on a other place to better view the waiting time.

Idea2: don’t always ask to validate the OpenStreet Data participation at the starting process, does this every 20 lauching, for example.

“Who wants to try the fabulous turn restriction plugin in order to fix it? ;-)”

Ok - I’ve fixed the turn restrictions.

I’ve got a new problem that I need to investigate a bit more. When driving from Victoria to South Australa the time zone changed automatically at the border but the ETA on the Navicator 10 went back 1.5 hours rather the correct 0.5 hours. I’m not sure if this is a Windows problem or a Navigator 10 problem or both but I will test it out a lot more soon.

Also I’ve had a couple more strange routing calls while driving. These have all appeared to be consistant with the routing algorithm automatically switching from car mode to pedestrian mode. I’ve never (knowingly) selected pedestrian mode. I can test this theory out fairly easily over the next few months.


Idea3: permit to download the OSM data from the PDAphone instead of from the PC (with a dedicated WM binary program isolate from the Navigator10 main application).
With the unlimited 3G data in Europe, it’s easy now (speed decrease after the first 500Mb in 1 month).

Navigator 10 is using GAPI (http://gapidraw.com/) and I am not sure what functions it may accelerate. Map drawing is primarily our own algorithm …

Teddy80 pointed out a problem with the “Lago di Garda” in Italy which is not visible in NavigatorFREE. I noticed that somebody recently added tags natural=‘water’ also to ways but that tag is already in relation 8569. Similar problem is with “Lake Geneva”, but there the tag natural=‘water’ is only in relation 332617 and not in member ways. Is there a rule about tagging members of relation? If not then during processing I should remove all member ways of particular relation (if you add the same water area twice it will cancel out).
thanks for any hints

Looking at the Lake Garda I found the two outer ways tagged with natural=water one was added recently, Changeset 6776129. At the Lake Geneva I found no outer way tagged natural=water, but an untagged inner way 26848816, where natural=land was deleted recently, Changeset 6466835.

According to this rule tagging the outer ways with natural=water isn’t correct. But because multipolygons might be tagged according to an old definition there’s another rule which might help:

Thank you Willi2006 for your help. I understand it from the “relation point of view” now. What troubles me a little is that if I process something what looks like a pond (small closed way with tag natural='water") I should also check that it is not mentioned in any relation, because it could be a bay of some larger lake (I suppose, that island would not have this tag even it is a water boundary).

I would have another question related to data processing. We are using relations with admin_level=2 (for USA admin_level=4) and boundary=‘administrative’ for definition of countries/regions. What we expect is geometric multi-polygon, so that we can say if given element is inside region or not.
We are currently processing planet-110105.osm and there is again problem with France (relation = 79981, before we used 11980) which now contains only ‘maritime’ boundaries, i.e. the polygon is not complete. I understand, that for example Philippines (relation 443174) are not finished yet, and that in Switzerland (relation 51701) is probably missing member type ‘subarea’ (I see it fixed now), but again I am not sure if there is a rule that relation boundary=‘administrative’ should define geometrically valid multi-polygon? Once a while I fix self-crossing boundary, if it is not caused by resolution error (there is no limit how precise can be nodes (lat,lon) defined, right?), but I am not sure about these big relations.
Thank you

For questions about processing OSM data you might get more help on one of the mailing lists where OSM developers tend to communicate. This forum is mainly used by mappers and users. Contact / Mailing lists, Develop, Routing

Looking into this I found that with Changeset 6898344 dated 7 January 2011 a new parent relation France Metropolitaine was introduced with 15 boundary_segments as child relations defining the border of France. One of them is the relation 11980. There’s a Wiki page about this construction France boundary pyramidal construction last updated in March 2010. I hope this is of some help.

I transmited to the french OSM list

You should really try to keep using relation 11980 even if it is now a super-relation (relation of relations). Your application converting relations to polygons will have to support this solution soon or later for all countries with large borders anyway because they are no alternatives when the amount of elements is too big for a single relation.

Or, as said, this one http://www.openstreetmap.org/browse/relation/1362232 if you only whant the european part of France. (which only contains one level of relation childs)

Unfortunetly, we are lacking some Quality checker tools fo such a type of relation in order to check if it stills forms a valid multipolygon (in the osm sense)

Thank you all :). For this batch processing I used boundary from previously processed planet, but for the next one I would probably use the newly created France Métropolitaine (1362232) you mentioned and process islands separately. From Navigator point of view it is better when the data regions are “compact” and simple bounding box reflect where the data are. Thanks for your help Martin

Since almost two years I’m now mapping in Thailand. From the beginning I added names in Thai and English. Now I realize that this is supported quite well by PC and Pocket Navigator. When I choose in the setup Language English the English names are shown on the map otherwise the Thai names. At the same time I can choose the voice independently, e.g. German. For finding addresses I can enter the English or Thai name independent of the setting. Even mixed is possible, e.g. city in English and street in Thai. That’s great.

But I’m wondering at which zoom levels and in which size place names are shown. I expected that it is according to place=city/town/village/hamlet. But it isn’t, e.g villages show up at different zoom levels and their names are in different sizes.

The names of places are sorted into 12 “display classes”. We use primarily city/town/village/hamlet rule, but we would need more precise rule (the best for us would be priority order of all names). So if available we use population tag. If there is another tag we should use, please let me know.
p.s. I am glad somebody noticed the multi-language feature and liked it :). At the moment there is only ‘name’ and ‘name:en’, but it could be extended to other languages too (it just was not priority yet).

I’ve just installed Navigator10 Free on an old PocketLooX with WindowsMobile5. So far Navigator seems to work just fine. What I question is the horrible high energy consumption. Usually my battery runs fine for about 2h even with GPS active, yet with Navigator running it was empty after about 1h.

It seems the Navigator completely refreshes the screen about every second. And it seems the backlight never is turned down. This isn’t a problem when driving in a car but during wandering it’s not acceptable. Maybe Navigator10 can’t be run on WM5 yet this would make it useless for me.


The backlight is by default always on - you can change it in settings in Settings > Application > 2nd page Backlight (there should be possibility to switch between “always on” and “system settings”).

If you navigate, the program refreshes every GPS position = usually every second (actually it tries to extrapolate position, so the update could be more frequent, depending on your device). If you use only GPS without navigation, then turn off automatic map rotation, and there should be refresh of the GPS sprite only (unless it leaves the center area - then the map is shifted/refreshed).

Let me know if it helped


I recently aquired a Windows Core 5 based system for my car, and since I do a fair bit mapping, stumbled over this piece of software. The unit I’ve installed it on is a Hualingan navigation unit.

First of all, thanks, it’s brilliant. The UI is pretty straight forward and nicely designed.

I’ve got a few issues.

When calculating a route, the Navigator sometimes wants to send me over secondary and tertiary roads, instead of prioritizing national (primary routes). I’ve set it for the fastest route. Is this down to missing speed limits on the roads ?

Also, when recording a route, what is the logging interval ? I haven’t found an option to set this.


You can set your own car profile and define average speeds for each road category. Alternatively you can set preferences or disable some types of roads completely.

The average speeds of roads are not perfect :(. There is no distinction between urban/non-urban roads yet (during conversion of OSM data), when maxspeed tag is present then it is used also as average speed (this is causing some problems when on nearby roads is maxspeed tag missing), etc. Recommendations how to improve default speeds are welcome :).

There is no such a option yet - it is every second and it used to be primarily for debugging and not necessarily for mapping. What interval would you use?