Using this patch, I am seeing better than 20% speed improvement when
processing the Baltic map. YMMV. The amount of speed up is dependent
on the density of tags. If your nodes/way are heavily tagged, you
will see a speed benefit with this patch. It will also reduce VM
required (I don't have any
Version 1474 was commited by markb on 2010-01-08 12:38:19 + (Fri, 08 Jan
2010)
Bug fixes - tag removal crash and excessive table expansion.
No longer decrements size when a tag is removed as this causes a
problem because reducing size makes it look as if there is more
space available than
Hi Steve,
Anyway, please check the attached patch for sanity ...
Looks good to me. Thanks, will now finally gain the benefit of not
wasting gobs of memory in the hash maps!
OK - now committed.
It's just a stroke of luck that I stumbled across these issues, if I
hadn't tried to delete a
Running java -jar mkgmap.jar --version on my compiled mkgmap gives me
just svn. Shouldn't it show the svn revision?
Regards,
Carlos
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On 07.01.2010 23:13, Thilo Hannemann wrote:
The Douglas Peucker Algorithm might not be the best way to tackle the problem
of too small polygons. Right now polygons will be dropped if they have a
maximum extension of less than one map unit at the current resolution. The
code is in
The problem with the roads is that the SizeFilter is called for lines as well
as for polygons. But the call to the filter is in two different places in
mkgmap/build/MapBuilder.java. So if you make the MIN_SIZE a parameter and use
different values for lines and polygons you won't have any holes
Well speed seems improved...
however lake Neusidel / Neusiedler See in Austria is now empty in
some places where before it was filled with water. In general it seems
to be working great (and very quick). Of course missing the ways makes
it not production ready yet.
On 07.01.2010 23:39,
That patch works pretty nice. I upped the value to 40 and that gave nice
results when zoomed far out.
Here is the settings that I would find optimal
resolution 24 == 4 (I think 4 is anyhow the minimum because if less than
4 pixels than it ain't an area)
resolution 23 == 6 ( resolution 23 is not
Felix Hartmann schrieb:
That patch works pretty nice. I upped the value to 40 and that gave
nice results when zoomed far out.
Here is the settings that I would find optimal
resolution 24 == 4 (I think 4 is anyhow the minimum because if less
than 4 pixels than it ain't an area)
resolution
I've tried the patch as well and it works nicely. Smaller maps, some map
clutter removed and seems to be faster as well.
Regards
Thilo
Am 08.01.2010 um 21:48 schrieb Johann Gail:
Felix Hartmann schrieb:
That patch works pretty nice. I upped the value to 40 and that gave
nice results
I am thinking about how to close polygons that are clipped by the
bounding box of the OSM file and are therefore not complete and not
closed? At the moment these ways are not handled by multipolygon code in
the mp branch. This causes lots of areas to disappear next to the
bounding box of the
Hello WanMil,
I am thinking about how to close polygons that are clipped by the
bounding box of the OSM file and are therefore not complete and not
closed? At the moment these ways are not handled by multipolygon code in
the mp branch. This causes lots of areas to disappear next to the
That patch works pretty nice. I upped the value to 40 and that gave
nice results when zoomed far out.
Here is the settings that I would find optimal
resolution 24 == 4 (I think 4 is anyhow the minimum because if less
than 4 pixels than it ain't an area)
resolution 23 == 6 ( resolution 23
Hello,
in the archive (september 2009) I saw that there were some discussion about
inter tile routing problems. I use version 1445 and have the same problem
when doing a routing in Mapsource over 4 interceptions. 3 interceptions
working fine.
Are there some news about that issue?
Another
On 08.01.2010 23:25, Johann Gail wrote:
That patch works pretty nice. I upped the value to 40 and that gave
nice results when zoomed far out.
Here is the settings that I would find optimal
resolution 24 == 4 (I think 4 is anyhow the minimum because if less
than 4 pixels than it ain't an
Hi Stefan,
in the archive (september 2009) I saw that there were some discussion about
inter tile routing problems. I use version 1445 and have the same problem
when doing a routing in Mapsource over 4 interceptions. 3 interceptions
working fine.
Are there some news about that issue?
I
16 matches
Mail list logo
