[mkgmap-dev] [PATCH v3] - beware of the bollards!
From Mark Burton markb at ordern.com on Wed Jul 8 08:07:29 BST 2009
Hi WessexMario, > As a map user and data contributor I get frustrated by the lack of > resolution. I'm not sure exactly where in the map rendering process the > detail being discussed here lies, but it would be my preference to > resolve nodes down to 1m. There are plenty of instances where complex > junctions have many roads, footpaths, gates, bollards, cattle grids and > stiles all within a 10m radius, on both sides of a country road, > expanding the resolution to 25m would make a mess of carefully plotted > features and make it even more difficult to render at the highest zoom. > If the rendering produces a cluttered map, then that's a rendering > issue, but for routing, complex junctions need fine resolution. Yeah, but look at the figures. The Garmin coordinates are 24 bits so the angular resolution is 360/2^24 - using a circumference of 40,075Km, that yields a resolution of 2.388m. Cheers, Mark
- Previous message: [mkgmap-dev] [PATCH v3] - beware of the bollards!
- Next message: [mkgmap-dev] splitter and java 1.5?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list