Hi
The problem lines were part of a much longer style file. Originally the
file followed your work around, but this creates long style files
because speed limits are defined in one of 5 ways on OSM data.
I appreciate that you cut down the file to make a good
example and that for the whole
Felix Hartmann wrote:
Mapsource only uses even resolution. Only gps uses uneven. So as you did
not set 20, that might be the reason to go straight up to 22. Try with
even resolution only.
I've changed the second line to
highway=primary mcssl=40 [0x04 resolution 20]
but it doesn't
On 09/09/09 11:27, MarkS wrote:
Felix Hartmann wrote:
Mapsource only uses even resolution. Only gps uses uneven. So as you did
not set 20, that might be the reason to go straight up to 22. Try with
even resolution only.
I've changed the second line to
highway=primary mcssl=40 [0x04
Steve Ratcliffe wrote:
On 09/09/09 11:27, MarkS wrote:
The problem is definitely in the generated img and not how mapsource
displays it. I would expect that both roads would be at resolution 22
which is probably not what you wanted but that is due to the usual
issue of the action rules
I've battled trying to narrow this down for a couple of days.
I have a lines style file that contains:
highway=* maxspeed=40mph {set mcssl=40}
highway=primary mcssl=40 [0x04 resolution 19]
highway=* mcssl=40 [0x04 resolution 22]
I'm then running a stripped down (in JSOM) set of OSM data
Mapsource only uses even resolution. Only gps uses uneven. So as you did
not set 20, that might be the reason to go straight up to 22. Try with
even resolution only.
MarkS wrote:
I've battled trying to narrow this down for a couple of days.
I have a lines style file that contains:
