When adding the line foot=no { add foot=no } to the top of the default lines style file, mkgmap svn revision 985 locks up (100% processor, does not finish), seemingly not depending on the data processed. For reference: it locks up with the data received from curl -L "http://www.informationfreeway.org/api/0.5/map?bbox=11.0338,49.6932,11.0827,4... " -o data.osm But any data I use locks it. Some experiments show that this breaks in revision 951. Rev. 950 works, rev. 951 does not work. Why would anybody want to use such an entry? I discovered this bug while using the entry maxspeed=* { set maxspeed=no; } to get rid of any maxspeed setting for routing experiments. Another command "remove" besides "add" and "set" would be useful for that purpose, but those "self-referencing" entries should not lock mkgmap anyway. Best regards Thilo