The patch moves the road speed calculations based on the maxspeed tag to
the style file. It uses the new maxspeedkmh function to calculate the
new internal tag mkgmap:road-speed-class.
This makes the ignore-maxspeeds option superfluous. Anyhow I have kept
it to ignore the evaluation of the
No comments or solution to this bug?
On Aug 26, 2013 9:37 PM, Felix Hartmann extremecar...@gmail.com wrote:
Well the bug is quite serious and took me about 6 hours to find out why
I'm missing roads in my maps.
In case you have an unconnected type of a road that you set up a rule
for, with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'n not sure, but you are only covering the cases:
only digits
digits and mph
digits and kmh
asking taginfo, there are also km/h in the data (almost more often
then kmh). But my java-knowledge is not that good. So if I'm wrong
forgive me.
I have directly converted the existing functionality. But it's a good
idea to add support for km/h. maxspeedmph() is also quite easy to add.
I have started a new branch mergeroads that contains all the changes
regarding merging of roads and moving of functionality from java source
code to the
Hi WanMil
The patch moves the road speed calculations based on the maxspeed tag to
the style file. It uses the new maxspeedkmh function to calculate the
new internal tag mkgmap:road-speed-class.
Have only glanced at the code, but I heartily approve of removing as
many hard-wired tags from
On 26/08/13 20:37, Felix Hartmann wrote:
lines file (only this content needed).
highway=motorway bridge=yes {set mkgmap:set_unconnected_type=none}
[0x13 road_class=1 road_speed=0 resolution 24 continue]
highway=motorway [0x10001 resolution 24 continue]
Its because the road is completely
Just to confirm - this affects only the *max* speed, correct? So if my
defaults for single-track unclassified roads suggest 40mph, but tags say
we're allowed to do up to 60mph (both quite reasonable here in Scotland,
where the National Speed Limit is unattainable on many roads), then the
map
