Mapmapper wrote:
The bike-routing is programmed a bit dirty. I took two highways in one for cycleways. The original highway and the cycleway. The same with cobblestone-streets. On these streets every node is a crossing point. Navit will then announce slight left/right from node to node.
Why do you use a separate street here? Wouldn't it be enough to add some attribute to the street?
Quote:
street_0 is cobblestone-street and street_1_land my cycleways (only the cycleways beside streets without own way in osm-data). street_1_land is originally for minor-roads, but this is deprecated in osm-data.
I think, routing for cars is still possible, but the route could differ with the manipulated map. In 0,1%, the orignal road dissapear out from map-data, and there is only the cycleway street_1_land. This could be an problem for routing with cars. Routing is still possible, but the speed for this road is calculated wrong.
Hm... Looks like this needs a bit more work to "properly" integrate it... I will try when I have some time, but if someone else wants to do it in the meantime, don't hesitate

Quote:
The Multipolygon-resolving is an own tool, written in Java. Osm-data would at first go through my tool, and then trough maptool. Perhaps, I can integrate it. But the special thing here is the time. It needs 2,5 hours, to resolve the Multipolygons for Brandenburg+Berlin, part of Germany. Perhaps, some people dont want to wait so long. For planet-extractor with fast computers, its no problem, I hope. Or an option for maptool, to resolve or not the multipolygons?
I guess then it would really be a good idea to make it optional. The easiest way would probably to code it as a function in C, make this a part of maptool and call this function only if some command line switch is given.