The patch to support different min sizes for lines and polys has now be
committed. I added a couple of options so that the default values (1
and 8 as per the original patch) can be changed if required.
Mark
___
mkgmap-dev mailing list
0 In article 4ba7d179.7030...@kleineisel.de,
0 Ralf Kleineisel URL:mailto:r...@kleineisel.de (Ralf) wrote:
Ralf Creating a gmapsupp.img with several family-IDs does work for me
Ralf when I use an options file with the -c option.
That's a bit more difficult for me - I'd have to generate it on the
This patch squashes spaces in label strings so that High Street
becomes High Street.
Is there any reason why we would want to preserve multiple spaces?
Mark
diff --git a/src/uk/me/parabola/imgfmt/app/Label.java b/src/uk/me/parabola/imgfmt/app/Label.java
index 149205b..ec2b11a 100644
---
WanMil wrote:
Hi Steve,
I have just started to have a look on the internals of the garmin
fileformat. The wiki
(http://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/Format) tells me
that there are the formats
TRE
NOD
MDR
SRT
GMP
DEM
The documentation of the garmin-img sourceforge
Toby Speight schrieb am 23.03.2010 11:03:
That's a bit more difficult for me - I'd have to generate it on the
fly, as I don't know how many tiles the splitter is going to throw out.
Unless there's a way around that?
If you are always splitting the same areas, you can use an area list as
Hi,
Is there a way to suppress the names of POIs displayed on the device
screen, without affecting the routing instruction names and the search
entity names.
I thought I remembered a discussion around this, but can only find the
diplay_name discussions that refers to names displayed in routing
Du Plessis, Bennie (bennie.duples...@sappi.com) wrote:
Hi,
[snip]
Also with POIs with custom symbols, I don't want to see the names, until
asked for;)
I have a feeling this is done in the TYP file but cannot determine how.
(I use TYPViewer to convert TYP to TXT and modify it, and
Torsten Leistikow (de_m...@gmx.de) wrote:
Toby Speight schrieb am 23.03.2010 11:03:
That's a bit more difficult for me - I'd have to generate it on the
fly, as I don't know how many tiles the splitter is going to throw out.
Unless there's a way around that?
If you are always splitting the
Torsten Leistikow escribió:
Toby Speight schrieb am 23.03.2010 11:03:
That's a bit more difficult for me - I'd have to generate it on the
fly, as I don't know how many tiles the splitter is going to throw out.
Unless there's a way around that?
If you are always splitting the same
On 03/23/2010 05:11 PM, Toby Speight wrote:
That's true - until the area density grows too big and it needs
resetting.
If that happens I just split the offending tile into half by inserting
another line in the template file by hand.
___
mkgmap-dev
Version 1623 was commited by markb on 2010-03-23 20:15:14 + (Tue, 23 Mar
2010)
Squash spaces in label strings.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On 23.03.2010 10:07, svn commit wrote:
Version 1621 was commited by markb on 2010-03-23 09:07:10 + (Tue, 23 Mar
2010)
Add --min-line-size and --min-polygon-size options.
Allow the user to specify the minimum size of line and polygon features.
Features smaller than that at a given zoom
Moin,
I want to create two symbols for a single element (tagged with key=value), and
both symbols shall have different name (alpha and bravo).
If my points style looks like the following
key=value {name 'alpha'} [0x6005 resolution 20 continue with_actions]
key=value {name 'bravo'}
Hello Felix,
Could it be that the new for polygons 8 is much much bigger compared
to the old (using patch) 8???
Or that the patch was not enacted on resolution 24??
Err, why?
Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Felix,
Or that the patch was not enacted on resolution 24??
Yes, that's true and looking at the code, I think that for polygons it
probably should always be done and, furthermore, should be done after
the polygon splitting so that any tiny polygons produced by the
splitting get removed. i.e.
On 23.03.2010 21:56, Mark Burton wrote:
Felix,
Or that the patch was not enacted on resolution 24??
Yes, that's true and looking at the code, I think that for polygons it
probably should always be done and, furthermore, should be done after
the polygon splitting so that any tiny
Version 1624 was commited by markb on 2010-03-23 21:52:40 + (Tue, 23 Mar
2010)
Revert Add --min-line-size and --min-polygon-size options.
Let's just pretend this never happened.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
On 23.03.2010 22:52, svn commit wrote:
Version 1624 was commited by markb on 2010-03-23 21:52:40 + (Tue, 23 Mar
2010)
Revert Add --min-line-size and --min-polygon-size options.
Let's just pretend this never happened.
___
mkgmap-dev mailing
18 matches
Mail list logo
