Currently my Garmin displays not the Elbe River at
http://www.informationfreeway.org/?lat=53.55294476877115&lon=9.737941940023477&zoom=14&layers=BF000F
And when I look to the Coast, I'll not see Water.
Are there People working on that?
Greetings Sven
Hi Marko,
On Sat, Jul 18, 2009 at 2:49 PM, Marko Mäkelä wrote:
> I would prefer to have only the major things (bus stations and train stops)
> in one menu and all the others (bus stops, tram stops) in the other menu.
> In this way, it should be easier to plan long journeys when travelling by
> tr
Hi Maning,
On Sat, Jul 18, 2009 at 12:49:17PM +0800, maning sambale wrote:
> used this in my
> highway=bus_stop [0x2f17 resolution 21]
>
> But it didn't appear in mapsource
On today's ride, I noticed that the Edge 705 renders 0x2f17 as a white
tiny square, similar to amenity=recycling (0x2f15, p
This is again overview map fault. Simply create bigger overview map, and it
will work
2009/7/18 maning sambale
> Here's areas.list result from splitter
>
> # List of areas
> # Generated Mon Jul 13 21:55:45 PHT 2009
> #
> 63240001: 215040,5447680 to 600064,5754880
> # : 4.614258,116.894531
Here's areas.list result from splitter
# List of areas
# Generated Mon Jul 13 21:55:45 PHT 2009
#
63240001: 215040,5447680 to 600064,5754880
# : 4.614258,116.894531 to 12.875977,123.486328
63240002: 215040,5754880 to 600064,5900288
# : 4.614258,123.486328 to 12.875977,126.606445
632
Using the same data without splitting routing is OK (Screenshot-2.png)
Now trying with tiled data (screenshot-5.png), mapsource cannot route
(screenshot-3.png).
If I zoom a little bit closer the other tile disappears
(screenshot-6.png). I can confirm this both in mapsource and roadtrip
On Sat, J
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
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 first line should be the same as the
third numbe
Mark Burton wrote:
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 gps.
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: 251000,2
This issue of the area near a tile boundary not being drawn is weird
because when I was first working on the inter-tile routing, I never
noticed this occurring. So either I was lucky and just didn't come
across it or something has changed since then to introduce this issue.
So, a question to ever
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 ignoranc
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,
> Yes, I noticed that - but could not reproduce it yesterday. Please
> notice however, that the route you found has both starting points at the
> lower map. That may or may not have anything to do with it. Your picture
> also shows that the upper map vanishes (which you confirmed already).
Well,
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 talking
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
Valentijn Sessink wrote:
But a few
days ago I noticed that the map dissapeared at the same spot where the
routing went wrong when I biked around with my Garmin Nuvi.
This is what I noticed a few days ago as well. While zoomed in pretty
far (~20 m) on my GPSmap 60CSx the map disappeared and I ha
17 matches
Mail list logo
