Splitter feature request - clip to overall bounding box

Back in the Baltic... When I split my map, the outside edge is ragged, i.e. the tiles that reach the edge of the overall map don't finish at the same lat/lon. So having split the map, I then have to manually edit the kml file and tweak the coordinates for the outside edges to make them neat and tidy. Is it possible for the splitter to be told an overall bounding box for the map and make the outside edge match that (with rounding as required)? That would be a great time saver for me. Cheers, Mark

Hi Mark, I'm curious as to why you want this. I added the tile trimming as a feature back in September as a result of a suggestion from Steve and I wasn't aware there was any downside to it: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2009q3/004080.html (note the first link no longer works) Chris MB> Back in the Baltic... MB> MB> When I split my map, the outside edge is ragged, i.e. the tiles that MB> reach the edge of the overall map don't finish at the same lat/lon. MB> So having split the map, I then have to manually edit the kml file MB> and tweak the coordinates for the outside edges to make them neat MB> and tidy. MB> MB> Is it possible for the splitter to be told an overall bounding box MB> for the map and make the outside edge match that (with rounding as MB> required)? That would be a great time saver for me. MB> MB> Cheers, MB> MB> Mark

Hi Chris,
I'm curious as to why you want this. I added the tile trimming as a feature back in September as a result of a suggestion from Steve and I wasn't aware there was any downside to it:
http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2009q3/004080.html (note the first link no longer works)
I would prefer my map to have a nice rectangular outline rather than being lumpy at the edges so that when you zoom out in mapsource it's pleasing to the eye. Cheers, Mark

On 16.01.2010 13:48, Mark Burton wrote:
Hi Chris,
I'm curious as to why you want this. I added the tile trimming as a feature back in September as a result of a suggestion from Steve and I wasn't aware there was any downside to it:
http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2009q3/004080.html (note the first link no longer works)
I would prefer my map to have a nice rectangular outline rather than being lumpy at the edges so that when you zoom out in mapsource it's pleasing to the eye.
Having rectangular outline is worse if you activate several maps on the GPS IMHO. You might end up with no map data overlaying map data of other maps. I do prefer a non neat outline too (before it allways caused problems near map borders on GPS). Best would be a polygon boundary following the shape of the map like Garmin topographic maps when not compiling for a rectangular boundary box.
Cheers,
Mark _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Hi Felix,
On 16.01.2010 13:48, Mark Burton wrote:
Hi Chris,
I'm curious as to why you want this. I added the tile trimming as a feature back in September as a result of a suggestion from Steve and I wasn't aware there was any downside to it:
http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2009q3/004080.html (note the first link no longer works)
I would prefer my map to have a nice rectangular outline rather than being lumpy at the edges so that when you zoom out in mapsource it's pleasing to the eye.
Having rectangular outline is worse if you activate several maps on the GPS IMHO. You might end up with no map data overlaying map data of other maps. I do prefer a non neat outline too (before it allways caused problems near map borders on GPS). Best would be a polygon boundary following the shape of the map like Garmin topographic maps when not compiling for a rectangular boundary box.
It would at least be nice to have the option to have a rectangular outline even if that isn't the best choice for all users. For some (read me), it would be what I wanted. What I think I want is for the splitter to take a new command line option something like: --bounds=A,B,C,D Cheers, Mark

On 16.01.2010 13:59, Mark Burton wrote:
Hi Felix,
On 16.01.2010 13:48, Mark Burton wrote:
Hi Chris,
I'm curious as to why you want this. I added the tile trimming as a feature back in September as a result of a suggestion from Steve and I wasn't aware there was any downside to it:
http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2009q3/004080.html (note the first link no longer works)
I would prefer my map to have a nice rectangular outline rather than being lumpy at the edges so that when you zoom out in mapsource it's pleasing to the eye.
Having rectangular outline is worse if you activate several maps on the GPS IMHO. You might end up with no map data overlaying map data of other maps. I do prefer a non neat outline too (before it allways caused problems near map borders on GPS). Best would be a polygon boundary following the shape of the map like Garmin topographic maps when not compiling for a rectangular boundary box.
It would at least be nice to have the option to have a rectangular outline even if that isn't the best choice for all users. For some (read me), it would be what I wanted.
What I think I want is for the splitter to take a new command line option something like: --bounds=A,B,C,D
Wouldn't your request be better handled by integrating an overview map with rectangular outline? I just feel that you attack the problem at the wrong place.... (BTW the biggest speedup for maps we can integrate is still to have an overview map for mapsource that is not empty - on GPS if you go lower than resolution 18 or 17 anyhow basemap is better suited than detailed map too. Would it be so difficult to define in "options" file of style-file that the lowest resolution (actually a 2 resolution overview map would be even better) is not input into normal tile but put into overview map?)
Cheers,
Mark _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (3)
-
Chris Miller
-
Felix Hartmann
-
Mark Burton