Steve Ratcliffe wrote:
A quick test with the attached patch shows that the boundaries shown in
mapsource now line up with the map. The places where there are no
tool-tips near the boundaries still exist though. I've not tried
routing to see if it makes a difference.
The attached patch
Hi
// TODO need to change this
private final int topBits = 15;
the first level in the overview map?
If so, then could it not be read directly from the detailed maps, rather
than being a constant? I noted the TODO.
Yes that is exactly right. It should be calculated so that the whole
area
On 18/07/09 13:09, Steve Ratcliffe wrote:
Hi
I've run your example and looked at the bounding boxes of everything
important that I know about.
First the actual bounds as given in the input files.
All the bounds below I believe should be exactly equal to this.
Also the first number on the
Mark Burton schreef:
OK - I have looked at your example and can confirm there is a problem
in that mapsource doesn't display the region near the tile boundary,
it has a gap of 200m or so. Don't know whether this is just mapsource being
it's usual crap self, or the problem also exists on the
On 17/07/09 22:59, Valentijn Sessink wrote:
Steve Ratcliffe schreef:
That is intentional; the bounds should not overlap and should meet exactly.
Are you really (as in really-really-really) sure about the fact that the
Oh, I'm not usually sure about anything.
I do know what you are
Steve Ratcliffe schreef:
So you will probably also find that in the area that disapears, if
you hover over a road you do not also get the usual pop-up that
tells you the name of the road.
Yes, but actually I blamed Wine instead of you ;-)
(I feel I actually can safely blame whoever I want,
Hi,
Since you know what you're talking about: is there a discussion,
explanation or otherwise for the reason that you did not let the maps
overlap? An overlap of 300 meters sounds like a good idea for the
routing - but as said before, I'm saying this from a position of
blessful ignorance.
Hi all,
I tried to line up Splitter with the map boundaries; instead of having
(hexadecimal showing)
63240008: 251000,25800 254800,38800, I had to use
63240008: XX,X 254c00,X). Now the tool tips would not show
up in the +-250 meters around the boundary.
Then I used:
63240008:
Steve Ratcliffe schreef:
0010: 52.470703,3.339844 53.701172,5.668945
0008: 52.163086,3.339844 52.470703,5.009766
So top matches bottom, but not the same as the bounds.
This could explain mapsource, but as it is not used
on the device can't explain the problem in the GPS.
In fact, I think
Hello list, I'm having a great time corresponding to myself here :)
but these are my observations so far.
Running Splitter, then Mkgmap.jar, then MapSetToolKit.exe, then
Mapsource, the resulting submaps are shifted from their bounding box:
they are about 2.4 kilometers left, up, from the map
Hi
Since no one replies to my mail, I'll do it myself ;)
Thanks for studying the problem so closely - it is very useful.
What I found is the following. Splitting a file with a border will
produce a file that has the exact bounds, without the overlap, in the
resulting map.
That is
Hi Valentijn,
Did anyone else notice this problem before? Were you able to reproduce
it? If it helps, I can prepare a map that will have a routing problem
just at the edge (there's a biking tunnel that MapSource avoids, no
matter how hard I try, while letting mkgmap render the map without a
Hi Mark,
Mark Burton schreef:
I believe (because the ML is not showered with emails complaining about
it failing) that inter-tile routing is generally working OK.
It really does work great. In fact, it took me quite a while to come to
the conclusion that the map edge seemed to be involved and
2009/7/18 Garvan maew garvan.m...@online.com.kh
Did anyone else notice this problem before? Were you able to reproduce
it? If it helps, I can prepare a map that will have a routing problem
just at the edge (there's a biking tunnel that MapSource avoids, no
matter how hard I try, while
Hello list,
When trying to use a built map, I'm getting a bit odd results around the
edges of tiles - at least, I think it's the edges. It's not exactly on
the boundaries, but about 2.5 kilometers below the grey lines that show
up in Mapsource (I assume these are the tiles). But strangely, the
15 matches
Mail list logo
