Yes, but one cannot access the unit so far. speed>50 with value 50mp/h or 50m or 50km/h or plain 50 will always yield the same result, or thats what I understood so far. On 28.08.2012 15:22, Steve Ratcliffe wrote: > Mkgmap already splits a number with a unit into its numeric and unit parts > and always has done. > > Also just a small amount of code would be required to convert to a common > unit before comparing. > > Or am I misunderstanding, or is there a bug? > > ..Steve > > Felix Hartmann <[email protected]> wrote: > >> Well it's quite a long time, there has been no discussion about this, >> however it's more and more common to put the unit into the main key. >> Could mkgmap do a clean up on this? >> >> It would be great if mkgmap could do the following: >> Remove any non numeric keys (and not "." or "," ) and place them into >> a >> new key called mkgmap:unit=.... >> Do this for maxspeed, distance, height, width (propose other keys I may >> >> have missed). >> >> As I'm sure this would take quite some time, it should be an option, >> and >> there should be a style-file called units_removed where you can specify >> >> the keys for which mkgmap should do this. >> >> >> Of course an implementation of automatically translating mp/h to km/h >> and other things would be great to have too, but the above is IMHO >> first >> of main importance. The problem is simply that commands like >> maxspeed>50 >> or distance<10 don't work otherwise.
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org _______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
