[mkgmap-dev] roadtrip no longer happy

[Greg Troxel]

I updated mkgmap to r1337, and found that my overview img/tdb changed
names.  I adjusted gmapibuilder invocation to reference those, and that
succeeded.  But on loading into roadtrip I get a "The map you selected
contains some errors and cannot be displayed.  The default map is being
shown instead." popup.

The test map fails more spectactularly, crashing roadtrip and then I
have to rm it from ~/Library before I can start it.

(script I used attached; test data was josm-downloaded bits of my town,
and then cloudmade massachusetts.osm.bz2)

Has anyone had recent success with roadtrip?

I probably should try bisecting svn to find when this behavior started.




do-mkgmap
Description: Binary data
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Do we write the region and/or country index wrongly? Still not able to search addresses outside of current maptile on etrex vista hcx

[Gert Münzel]

Sorry an addition/correction i have to make
Gert Münzel  *on* /Sat Oct 31 19:52:51 GMT 2009/
> afaik(at this time)
> 1. one can have more then one mapset with address index one gps
> 2. Address search only works for a tile
> 3. the map which covers  the wider area will be taken for address search 
> if there are more then one map(out of different mapsets) for a region
> 4. transparent maps can't be used on GPS for adress search
to 3.
on some examples this was true. But i tested this again with Metroguide tiles 
and openmtbmap DE
together on gps.
The smaller(less wide area) MG tile rules over the openmtbmap.
Not before you move the cursor in the wider area of the openmtbmap DE tile you 
can search in it.


to address search in other tiles by moving position:
there is no need to temporarily set your position to the other tile 
while gps receiver is in off mode(as i thought first).
Simply moving the cursor to the other tile is enough(on my 60csx, should 
be the same on Vista hcx and similar devices)

cheers
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Do we write the region and/or country index wrongly? Still not able to search addresses outside of current maptile on etrex vista hcx

[Gert Münzel]

Gert wrotes *on* /Fri Oct 30 22:10:42 GMT 2009/
> >/ Together with an other mkgmap map address search don't work for any of 
> />/ the maps.(e.g openmtbmap De + own mkgmap created trailmap)
> />/  
> /  >>This seems to be related to my trailmap. No idea why.
>   
Meanwhile , after some more test it seems to me that transparency of a 
map prohibits address search.
If i disable the tranparency of my map, address search works for it, 
also if i have tiles from another map with index( e.g. //openmtbmap De) 
//on my gps together with it.
Curiously i can always only address search on my trail map and not on 
the openmtbmap, although both maps are in the same region where i located.
I played already around with setting of Drawprioity and mapid, but can't 
find out the reason for this behaviour.
As far as i can see its related to the effect, that you only can search 
in the region(however it is defined)/tile where you are located.
My trail map covers a wider region then a single tile of the 
//openmtbmap De. //If i move my location on gps while gps receiver is 
off, to a region which is covered from a tile of the openmtbmap De, 
immediately the address search works for this map and no more for my 
trail map.

afaik(at this time)
1. one can have more then one mapset with address index one gps
2. Address search only works for a tile
3. the map which covers  the wider area will be taken for address search 
if there are more then one map(out of different mapsets) for a region
4. transparent maps can't be used on GPS for adress search

cheers


___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] AssertionError: NET 1 offset too large

[dom Team OiD]

I had the same problem with the netherlands coutry map and europe. Teh 
europe map failed at the same koords like the netherland.
So this tile must have any information which causes ths error.
A reduction of nodes  of the splitted tiles helped to solve the problem 
for the netherlands map,
but not fore europe. Currenty I'm running a build ad reduced the nodenum 
to 60.
I will post the result.

Marco

Mark Burton schrieb:
> Hi Robert,
>
>   
>> it's the tile with 220462 ways!
>> 
>
> Yes but tile 63250390 has even more ways so it's not the number of ways
> that matters (directly) but how much stuff is output for each way. 
>
> For each way, its name(s), info about what levels it appears in and
> address information is output. All of this is variable length so you
> can't really predict when it will reach the overflow threshold.
>
> So if you set the limit at X ways, some maps would be OK but others
> would fail depending on whether lots of ways had long names or address
> info specified.
>
> Not sure how to solve this one at the moment.
>
> Cheers,
>
> Mark
> ___
> mkgmap-dev mailing list
> mkgmap-dev@lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>
>   
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] AssertionError: NET 1 offset too large

[Mark Burton]

Hi Robert,

> it's the tile with 220462 ways!

Yes but tile 63250390 has even more ways so it's not the number of ways
that matters (directly) but how much stuff is output for each way. 

For each way, its name(s), info about what levels it appears in and
address information is output. All of this is variable length so you
can't really predict when it will reach the overflow threshold.

So if you set the limit at X ways, some maps would be OK but others
would fail depending on whether lots of ways had long names or address
info specified.

Not sure how to solve this one at the moment.

Cheers,

Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] AssertionError: NET 1 offset too large

[Robert Joop]

On 09-10-31 18:24:41 CET, Mark Burton wrote:
> 
> This looks to me that there is simply too many roads in the tile. Can
> you tell the splitter to limit the number of ways in a tile?

unfortunately the splitter does not seem to offer that option, it seems
that one can only limit the number of nodes.

but your diagnosis looks rather likely: i've counted the number of ways
in the tiles:

% for f in *.osm.gz; do echo -n "$f ";zcat $f|egrep '^http://www.openstreetmap.org/browse/way/6926238)

(a pretty short way, btw, just five nodes)
...it was easy to find the problematic tile:

% zegrep "^

it's the tile with 220462 ways!

rj
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

[mkgmap-dev] Commit: r1337: Fix test for generation of warning message.

[svn commit]

Version 1337 was commited by markb on 2009-10-31 18:06:35 + (Sat, 31 Oct 
2009) 

Fix test for generation of warning message.

Also, set result to false so that the turn restriction is not output
when the restriction has a via way.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Turn restrictions in foot mode

[Mark Burton]

Hi Chris,

I took another look at the turn restriction exception stuff but could
not find a way of excepting foot traffic. Sorry, it remains a mystery.

Cheers,

Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] AssertionError: NET 1 offset too large

[Mark Burton]

This looks to me that there is simply too many roads in the tile. Can
you tell the splitter to limit the number of ways in a tile?

Cheers,

Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

[mkgmap-dev] Commit: r1336: Output info to identify road that fails assertion "NET 1 offset too large".

[svn commit]

Version 1336 was commited by markb on 2009-10-31 16:40:56 + (Sat, 31 Oct 
2009) 

Output info to identify road that fails assertion "NET 1 offset too large".
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] AssertionError: NET 1 offset too large

[Robert Joop]

On 09-10-31 17:10:19 CET, dom Team OiD wrote:
> Yes,
> 
> and it's always the same tile. It's a part of netherlands.

it may be the same data, as my bbox surrounding germany includes the
eastern half of the netherlands.

can you give me the tile's bbox coordinates?
with both your and my tile's bbox coordinates, the intersection of them
is likely to contain the data that triggers the bug...?

rj
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] AssertionError: NET 1 offset too large

[dom Team OiD]

Yes,

and it's always the same tile. It's a part of netherlands.
Using the europe.osm source data.
I already changed the splitter and mkgmap settings.
Marco

Robert Joop schrieb:
> On 09-10-30 18:47:07 CET, dom wrote:
>   
>> I tried it out again with assertions and I got the following error.
>>
>>
>> Doing europe.osm map now...
>> java.lang.AssertionError: NET 1 offset too large
>> at
>> uk.me.parabola.imgfmt.app.net.RoadDef.writeRgnOffsets(RoadDef.java:322)
>> 
>
> i get the same error, with two different combinations of splitter and
> mkgmap.
> i've cut a bbox (left=5.5 bottom=46.5 right=15 top=55, that's roughly
> DE and AT) from the last planet.osm using osmosis 0.30.
>
> the assertion fails with both
> - splitter r97 and mkgmap trunk r1334
> - splitter r74 and mkgmap trunk r1144 + sea5 patch
>
> the latter worked fine before with other large bbox excerpts from older
> planets.
>
> producing maps from smaller extracts works fine with both combinations.
>
> the splitter was given a --max-nodes=100.
>
> any ideas?
>
> rj
> ___
> mkgmap-dev mailing list
> mkgmap-dev@lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>
>   
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

[mkgmap-dev] FW: Contour Rendering Error with MP files.

[Hilton Long]

 

On Fri, Oct 30, 2009 at 11:24:20PM -0400, Hilton Long wrote:

> The problem DOESN'T EXIST and all contours display correctly if the 

> map is compiled with R1127.

 

This disagrees with the subject. Which one did you mean, 1127 or 1227?

 

Best regards,

 

Marko

 

Marko,

The last build on my machine which renders the contours correctly is R1173.

It shows the following image.

 

http://www.gpsfiledepot.com/hosting/viewer.php?image=334

Show the contours rendered correctly.

 

R1187 (next build I have) through 1311 render as follows:

 

http://www.gpsfiledepot.com/hosting/viewer.php?image=336

Shows the error at normal zoom.

 

http://www.gpsfiledepot.com/hosting/viewer.php?image=337

Shows the last zoom level where the error is visible.

 

The contours show up correctly in the IMG file viewed in GPSmapedit, but
they don't show in MapSource or on my GPSmap60CSX.

 

Regards,

Hilton

 

<>___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] [PATCH] Display road name instead of ref in routing directions

[Ralf Reimann]

2009/10/31 Clinton Gladstone 


> And the question is, is this also true for other countries?
>

Yes Clinton, your English is much much better than mine.   :-)
Really good translation.   ;-)

Ralf
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

[mkgmap-dev] AssertionError: NET 1 offset too large (was: Re: Creating defect tiles.)

[Robert Joop]

On 09-10-30 18:47:07 CET, dom wrote:
> I tried it out again with assertions and I got the following error.
> 
> 
> Doing europe.osm map now...
> java.lang.AssertionError: NET 1 offset too large
> at
> uk.me.parabola.imgfmt.app.net.RoadDef.writeRgnOffsets(RoadDef.java:322)

i get the same error, with two different combinations of splitter and
mkgmap.
i've cut a bbox (left=5.5 bottom=46.5 right=15 top=55, that's roughly
DE and AT) from the last planet.osm using osmosis 0.30.

the assertion fails with both
- splitter r97 and mkgmap trunk r1334
- splitter r74 and mkgmap trunk r1144 + sea5 patch

the latter worked fine before with other large bbox excerpts from older
planets.

producing maps from smaller extracts works fine with both combinations.

the splitter was given a --max-nodes=100.

any ideas?

rj
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] [PATCH] Display road name instead of ref in routing directions

[Clinton Gladstone]

On Oct 30, 2009, at 23:56, Felix Hartmann wrote:

>> In Germany the label of the primaries is shown on the road signs  
>> (B57, B58...), but not the labels of the secondaries (like L237,  
>> K39 and so on). How is this handled in other countries?
> This is not related to type of road, but type of symbol. :box  
> and :hbox cannot display certain types of labels (see older messages  
> from me) - other like :oval have no restrictions and you can input  
> more or less whatever you like.

I think Ralf was talking about the "real world" here, not the one in  
our GPS devices. ;-)

That is, when you are outside and looking at the physical signs on the  
road, the 'ref' number of secondary roads does not usually appear on  
the signs, however the 'ref' of primary highways is generally printed  
on the signs (at least in Germany).

This makes a difference for routing directions: when should the ref be  
used and when should the name be used?

- For motorways, we almost always want the ref: A35 instead of  
"Autoroute des Cigognes"; A1 instead of "Autostrada del Sole".

- This is also probably true for trunk roads.

- For primary highways, either the ref or the name or both could be  
most appropriate: "B58", or "Weseler Strasse", or "Weseler Strasse  
(B58)"?

- Generally for secondary and lower roads, we want the name; the ref  
is secondary: "Bahnhofstrasse" instead of "K 4256".

And the question is, is this also true for other countries?
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Can you set background colour in a TYP file?

[Nop]

Hi!

Charlie Ferrero schrieb:
> Did you ever get to the bottom of this?  I have also had zero success in 
> getting a white background.  I've tried setting both 0x4b and 0x4a 
> polygons to white and neither has an effect.

You cannot change the color of the Background - it appears to be 
hardcoded into most Garmin units.

But: The background is just a large rectangle which is added by mkgmap. 
If you suppress this yellow rectangle with --transparent and just add a 
rectangle of your own with a different id, you can set your own custom 
background.

Doing this automatically is a feature of OSM Composer. I gave my hiking 
map light gray background.

bye
Nop

___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Can you set background colour in a TYP file?

[Morten Kjeldgaard]

On 31/10/2009, at 10.40, Charlie Ferrero wrote:

> Did you ever get to the bottom of this?  I have also had zero  
> success in
> getting a white background.  I've tried setting both 0x4b and 0x4a
> polygons to white and neither has an effect.

Me too. I thought I was just being stupid as usual... :-)

-- Morten

___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Turn restrictions in foot mode

[Felix Hartmann]

Chris-Hein Lunkhusen wrote:
> Hi,
> I tested some turn restrictions in Mapsource and found that they
> are used in all modes (car/bicycle/foot).
>
> Is there an option to disable them for foot ?
>
> In Germany the traffic signs for T.R. are only valid for vehicles.
>
> Chris
>
>   
Probably not easily. I think the only way would be to workaround like 
for bicyclerouting, by creating ADDITONAL ways with different 
restrictions on top. However for proper foot routing, just like for 
proper bicyclerouting you would need to create maps dedicated only to 
pedestrians autorouting using car/motorcycle mode instead of foot. 
Additional ways with different restrictions road_speed, road_class and 
oneway direction would be great anyhow (but not yet possible).
> ___
> mkgmap-dev mailing list
> mkgmap-dev@lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>   
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Turn restrictions in foot mode

[Mark Burton]

Hi Chris,

> I tested some turn restrictions in Mapsource and found that they
> are used in all modes (car/bicycle/foot).
> 
> Is there an option to disable them for foot ?
> 
> In Germany the traffic signs for T.R. are only valid for vehicles.

When I added the exceptions to the turn restrictions recently I could
not find a way of excepting foot traffic. There almost certainly is a
way to do that, I shall revisit that code and see if I can find what
needs to be done.

Cheers,

Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

[mkgmap-dev] Turn restrictions in foot mode

[Chris-Hein Lunkhusen]

Hi,
I tested some turn restrictions in Mapsource and found that they
are used in all modes (car/bicycle/foot).

Is there an option to disable them for foot ?

In Germany the traffic signs for T.R. are only valid for vehicles.

Chris

___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Can you set background colour in a TYP file?

[Charlie Ferrero]

Mark Burton wrote:
> Hi,
> 
> Just playing around with TYP files and wondered if it is possible to
> change the "Garmin yellow" background to anything else using a TYP file?
> 
> If not, is there any other way of doing that?
> 
> Cheers,
> 
> Mark
Hi Mark,

Did you ever get to the bottom of this?  I have also had zero success in 
getting a white background.  I've tried setting both 0x4b and 0x4a 
polygons to white and neither has an effect.

--
Charlie
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] R1228 thru R1311 don't compile MP contours correctly

[Marko Mäkelä]

On Fri, Oct 30, 2009 at 11:24:20PM -0400, Hilton Long wrote:
> The problem DOESN'T EXIST and all contours display correctly if the map is
> compiled with R1127.

This disagrees with the subject. Which one did you mean, 1127 or 1227?

Best regards,

Marko
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev