[mkgmap-dev] leading and trailing spaces
From GerdP gpetermann_muenchen at hotmail.com on Thu Jan 29 06:17:59 GMT 2015
Hi Mike, I can't find it now, but I seem to remember a comment that trim() should be used with great care as it removes the highway shield codes. Gerd Mike Baggaley wrote > Good evening all, > > I've noticed that there are a number of unwanted leading and trailing > spaces > in OSM data. You can get a list of the ones on the name field using the > following: > > name~'.* ' {echotags "name ends with a space"} > name~' .*' {echotags "name starts with a space"} > > I can't see any facility in mkgmap to remove these, and was wondering > whether the best way would be simply to code them out by replacing the > following line in parseDense, parseNodes, ParseWays and parseRelations: > > String val = getStringById(...); > > With > > String val = getStringById(...).trim(); > > I can't think of any reason why a value would need to start or end with a > space, so it seems reasonable to just remove them. Are there any other > suggestions, or reasons why this should not be done? > > Regards, > Mike > > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev at .org > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- View this message in context: http://gis.19327.n5.nabble.com/leading-and-trailing-spaces-tp5831778p5831782.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
- Previous message: [mkgmap-dev] leading and trailing spaces
- Next message: [mkgmap-dev] leading and trailing spaces
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list