thanks for clearing that up. I didn't know enough about the indexes. So
style-file command is enough for anything that I can imagine.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi
> I think you did not understand what I meant.
Maybe, that's the problem with talking about options that don't exist :)
There are two indexes that we might be talking about.
1. A road index in the .img. If there are 2000 "Path" roads then there
will be 2000 entries "Path" in this index.
2.
On 11.11.2011 11:34, Steve Ratcliffe wrote:
>
> Hi
>
>> What happens when a user simply rebuilds the address index of existing
>> .img files without using a style-file when mkgmap:noindex=true had been
>> set for problematic cases?
>>
>> a) will it then slow down if many roads have the same name
Hi
> What happens when a user simply rebuilds the address index of existing
> .img files without using a style-file when mkgmap:noindex=true had been
> set for problematic cases?
>
> a) will it then slow down if many roads have the same name
> b) doesn't matter, the names are now in such a positi
Actually I just thought about one possible problem, as I don't know how
the mkgmap:noindex=true will be implemented.
What happens when a user simply rebuilds the address index of existing
.img files without using a style-file when mkgmap:noindex=true had been
set for problematic cases?
a) will
On 31/10/11 10:40, WanMil wrote:
> I think it's a good idea to use a flag like 'mkgmap:noindex=true' which
> can be set in the style file. That provides the best flexibility.
The option appears a popular choice!
It might be a good addition, although I think it would have
to work with all element t
maybe it would be a good idea to have a command line switch *and* a
style rule.
the command line switch would have to default to "no-index=false",
otherwise indexing in all older styles would break. a 2nd optinon
"no-index=true" could automatically add a no-index tag to all lines
which then c
Perhaps if the name is set to a constant by a rule, that should default
mkgmap:no-index to true.
pgpFoxIITDr9v.pgp
Description: PGP signature
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-de
Yes that is probably best.
I set names pretty extensively, and even I would only need about 80
additional lines of code in my lines style with mkgmap:noindex=true (as
I have to duplicate all lines where names are set to have one with
name!=* set mkgmap:nopreviousname=yes and then check that con
I think it's a good idea to use a flag like 'mkgmap:noindex=true' which
can be set in the style file. That provides the best flexibility.
WanMil
>
> Hi
>
> I would like some opinions please from those that make maps.
>
> If you have a style that say sets the name of every path to 'Path'
>
>
it would make a lot of sense if such names do not find their way into
the index. to control that behaviour flagging those ways via the style
file feels like the most flexible method.
Am 29.10.2011 15:57, schrieb Steve Ratcliffe:
Hi
I would like some opinions please from those that make maps.
Hi,
On Sat, Oct 29, Steve Ratcliffe wrote:
> If you have a style that say sets the name of every path to 'Path'
>
>eg: highway=path | highway=footway | highway=track {name 'Path' }
>
> or anything similar that results in thousands of roads with the same
> name, then mkgmap appears to freez
Am 29.10.2011 15:57, schrieb Steve Ratcliffe:
Hi
I would like some opinions please from those that make maps.
If you have a style that say sets the name of every path to 'Path'
eg: highway=path | highway=footway | highway=track {name 'Path' }
or anything similar that results in thousands
Hi
I would like some opinions please from those that make maps.
If you have a style that say sets the name of every path to 'Path'
eg: highway=path | highway=footway | highway=track {name 'Path' }
or anything similar that results in thousands of roads with the same
name, then mkgmap appears
On 20/10/11 21:36, WanMil wrote:
> I can confirm that behaviour. Although in real mkgmap does not freeze
> (endless loop) but is working very very hard. Possibly the mkgmap code
> is not very optimal for the special test case.
>
> @Steve, the code requires a very long time in the
> NETFile.simplify
I can confirm that behaviour. Although in real mkgmap does not freeze
(endless loop) but is working very very hard. Possibly the mkgmap code
is not very optimal for the special test case.
@Steve, the code requires a very long time in the
NETFile.simplifySortedRoads method because I think there
here: www.geocaching-dresden.de/mkgmap/style.zip
i found a workaround just now: the style contains a file called "lines
workaround", which does the naming of the roads in a separate step - no
freezing.
micha
Am 20.10.2011 17:58, schrieb WanMil:
i'm trying to create a lines-only routable ma
> i'm trying to create a lines-only routable map. from a certain amount of
> lines in the style mkgmap starts turning out 2 empty img files (empty
> means 0 bytes, not empty maps), then memory usage freezes pretty much,
> cpu usage oscillates wildly and nothing more happens.
>
> this problem is tie
i'm trying to create a lines-only routable map. from a certain amount of
lines in the style mkgmap starts turning out 2 empty img files (empty
means 0 bytes, not empty maps), then memory usage freezes pretty much,
cpu usage oscillates wildly and nothing more happens.
this problem is tied to --r
19 matches
Mail list logo
