.
Elrond
Index: uk/me/parabola/mkgmap/osmstyle/RuleSet.java
===
--- uk/me/parabola/mkgmap/osmstyle/RuleSet.java (revision 1652)
+++ uk/me/parabola/mkgmap/osmstyle/RuleSet.java (working copy)
@@ -138,6 +138,12 @@
index = newIndex
On Mon, Sep 21, 2009 at 05:03:19PM +0100, Steve Hosgood wrote:
[...]
NT maps (with MDR1 using a record-length of 4 bytes) seems to be listing
the GMP subtile files. I hear that there are 8 bytes variants - don't
know about them.
The 8byte are used in mapsource.
Elrond
on the for-device one first, it
seems to have lots fewwer things needed, so we should
arrive at might work or might improve *something*
close?
Elrond
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo
road_speed=2
resolution 21]
+junction=roundabout highway=construction [0x0c resolution 24]
junction=roundabout [0x0c road_class=0 road_speed=1 resolution 21]
Any comments on this one? I'll happily commit this one, if
people like it.
Elrond
should at least think about it.
Elrond
On Sat, Aug 15, 2009 at 08:30:13PM +0200, Hanno Böck wrote:
Hi,
I just noted with a garmin map from kleineisel.de that my local supermarket
is
not listed.
The reason is that it's an area, not a point. I think this is caused by not
applying
Hi,
I have no idea on sailing (despite I'd like to somehow).
Looking at your mods...
+man_made=pier {name '${name} (${man_made})' | '${man_made}'
1. Did you miss the } at the end? Or am I missing
something obvious?
2. Shouldn't that line before the other man_made=pier line?
Elrond
change the resolution for
this item, but keep everything else.
I tried this by adding an appropiate normal rule to the
elrond style. Guess what? I forgot about the ordering
and a higher priority normal rule didn't kick in and
routing was b0rked.
Con:
- We would end up trying to support 6
bicycle = yes; add foot = yes}
[0x660f resolution 20]
+
[...]
Haven't looked to closely at the rest...
At least commit that part, it doesn't hurt anything, I'd
say.
Elrond
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http
On Tue, Jun 16, 2009 at 07:58:24AM +0200, Thilo Hannemann wrote:
Hi Elrond,
[...]
The problem of distorted polygons does not only appear in the overview
map, it appears at all zoom levels.
[...]
Hi,
Okay, about the DP code, I have some speculation, why it
performs bad. It's a variation
Hi Johann,
first some introduction to the overview map:
It's only used in mapsource.
If you have multiple tiles (for different areas) there is
exactly one polygon (rectangle) for each tile. The name for
the polygon is the name of the tile plus its map name (the
eight digit name).
It has a
Hi,
My current conclusions from both thread parts:
1) I should only disable the SizeFilter (we really, really
don't want to drop any polygon).
2) We should fix DP.
Does that make sense?
Elrond
___
mkgmap-dev mailing list
mkgmap-dev
Hi,
On Tue, Jun 16, 2009 at 10:49:45PM +0200, Thilo Hannemann wrote:
Hi,
Am 16.06.2009 um 20:39 schrieb Elrond:
My current conclusions from both thread parts:
1) I should only disable the SizeFilter (we really, really
don't want to drop any polygon).
For the overview map obviously
sure, everyone understands them and at the same time,
that they're right.
2) Some parts change some internals drastically and I feel,
I might have overlooked something in this cause.
Elrond
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
) that smaller rects might make some sense.
So this simple patch disables both filters for the overview
map.
If nobody objects or I get some Go, I'll commit it soon.
Elrond
Index: uk/me/parabola/mkgmap/combiners/TdbBuilder.java
===
--- uk/me
14 matches
Mail list logo