Thanks Minko, I'll move that to a useful folder :-)
Geoff.
-Original Message-
From: Minko
Sent: Friday, December 07, 2012 8:39 PM
To: Development list for mkgmap
Subject: Re: [mkgmap-dev] line types not showing in basecamp
Geoff, Ctr-G (2x) clears the cache.
> others. It also doesn
Geoff, Ctr-G (2x) clears the cache.
> others. It also doesn't help that Mapsource/Basecamp cache the tiles
> and
> there appears to be no easy way to clear them. So sometimes you have
> to zoom
> in/out to a level not looked at before to see the changes take effect
> after
> updating a TYP file.
Yes I've had similar issues in the past. I think I remember Steve saying in
some distant discussion that it is unknown behaviour the order Basecamp and
Mapsource display lines, so overlaying one line on top of another is
particularly difficult; and I tend to use an overlay map now if I need to
On Fri, Dec 07, 2012 at 04:42:29AM -0800, gbbickerton wrote:
>I was unfortunate to use some line types which do not show in Basecamp
>initially which caused a huge amount of confusion trying to figure out
>what was wrong with my code, perhaps mkgmap could test for unusable
>types.
Did you try c
Hi all,
I've committed r252:
- remove some warnings (from eclipse juno) reg. missing close()
- don't create tiles larger than 85° lat or 90° lon
- cut large empty areas if splitting doesn't find nice solution
In most cases splitter will find a nice split within a few seconds.
A few problems remai
>
> It's a question of parsing the data.
>
> You (means mkgmap) have to rebuild superroutes, till there are only
> way-member in it.
>
> Eg:
> parse tile and read all relation (maybe store in RAM)
> if relation_A contains relations_B, replace all relations_B in this
> relation_A with the ob
Ok, so the problem of rendering those nested relations still exist, can this be
solved?
> Without it, they are processed in an arbitrary order. In this case you
> are lucky as the arbitrary order happens to work for you. With a
> different tile extract or after a few edits you may be unlucky agai
On 07/12/12 14:37, Minko wrote:
> Another test: I removed the option --preserve-element-order in my mkgmap
> options and it seems to render the relations fne now...
> Where is this option good for?
With the option it processes the elements in the order that they appear
in the input file.
Withou
Another test: I removed the option --preserve-element-order in my mkgmap
options and it seems to render the relations fne now...
Where is this option good for?
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://lists.mkgmap.org.uk/mailm
It's a question of parsing the data.
You (means mkgmap) have to rebuild superroutes, till there are only
way-member in it.
Eg:
parse tile and read all relation (maybe store in RAM)
if relation_A contains relations_B, replace all relations_B in this
relation_A with the objects the relation_B1..
I'm struggling to render nested networks of international cycling route
relations and maybe found an issue with the sort order of relation ID's.
My observation is that if the parent relation has a higher ID than the child
relation, my mkgmap style won't render the tags of the parent relation on t
Am 07.12.2012 11:12, schrieb michael lohr:
> --ignore-turn-restrictions should be kept for pure walking/cycling maps,
> unless this can be achieved in the style. i never tried but something
> like type=restriction {delete type} could maybe replace it.
I think it's the better way, to move it into
Am 07.12.2012 13:42, schrieb gbbickerton:
> I was unfortunate to use some line types which do not show in Basecamp
> initially which caused a huge amount of confusion trying to figure out what
> was wrong with my code, perhaps mkgmap could test for unusable types.
If there is a sytax-error, mkgmap
Thanks for your help I did not like the shields anyway I am using this which
works well
#My solution to colour code cycle routes
#in lines file above other highways
#types a bitmap 10 wide with a 4 wide transparent center so other ways show
through
#Colour cycleways individually
reivers=yes {
Am 06.12.2012 21:18, schrieb Steve Ratcliffe:
> I think there are a few obsolete/unworking options that can be removed
> straight away.
--adjust-turn-headings
Sometimes leads to routing errrors.
Should be removed or reworked.
Chris
___
mkgmap-dev m
--ignore-turn-restrictions should be kept for pure walking/cycling maps,
unless this can be achieved in the style. i never tried but something
like type=restriction {delete type} could maybe replace it.
--add-pois-to-lines can be used for hiking path symbols
micha
Am 06.12.2012 21:18, schri
Congratulations ! Can't wait to see the Hello World
--
View this message in context:
http://gis.19327.n5.nabble.com/House-numbers-tp5739428p5739512.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.
___
mkgmap-dev mailing list
17 matches
Mail list logo
