Gerd,
Thanks for the quick reply. That makes complete sense that a California
extract wouldn't have information about a larger area that it is part
of. I'm not sure why it resolved having ABC instead of actual county
information, but it seems to have done that as well.
I've replaced steps 3,
Hi,
roadsAreJoined() tests all points of one MapLine against all points of
another MapLine instance.
It should first check the previously calculated bounding boxes to eliminate
many unsuccesfull loops.
Gerd
Index: src/uk/me/parabola/mkgmap/main/MapMaker.java
Hello Bill,
some of the problems are caused by the fact that you use the california.o5m
to create the
bounds for california. This extract probably doesn't contain any usable
information about admin_level=2 boundaries like "USA".
You should either use a larger extract (e.g. north america) to crea
I've been using mkgmap to compile a California map for my Garmin for a
while now, and was excited to see that addressing was being supported,
but I'm having troubles getting this new feature to work as I expect.
System Information:
OS: 64-bit Ubuntu 11.10
GPS: Garmin Montana 650 software version
Version 2232 was commited by steve on 2012-03-02 21:41:18 + (Fri, 02 Mar
2012)
280: nsis lang patches
Spanish: Carlos D?\195?\161vila
German: Henning
Dutch: Minko
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] Holes in the Sea
>
> The problem is that splitter and mkgmap don't work together at all. The
> solution would be that splitter does more checking against the possibility
of
> such empty tiles, or other way around - an improvement on how max-nodes
> are counted. The othe
The problem is that splitter and mkgmap don't work together at all. The
solution would be that splitter does more checking against the
possibility of such empty tiles, or other way around - an improvement on
how max-nodes are counted. The other possibility would be, if there was
an automatic me
I think that it has to do with the negative node-id's when you draw an island
that isn't in the OSM database. Probably it will not merge with the osm data.
Well, either way it will be an inconvenient workaround, I agree.
Maybe Wanmil's floodblocker can do something like this, but then
the opposit
On Fri, Mar 02, 2012 at 04:27:37PM +0100, Chris66 wrote:
>why is the include of the location-rules commented
>out in the default style ?
>#base-style=location
As far as I understand, the location-rules were inlined back to the
default style, because the inclusion did not work as expected.
Sorry,
Hi WanMil,
but if I code an assert statement and execute the program with -ea, I surely
want to see the assertion that happened. Instead, the program stopped
without any message.
Gerd
WanMil wrote
>
>> Hi WanMil,
>>
>> yes, your solution is better. I wanted to do it in the same way, but
>> fai
> Hi WanMil,
>
> yes, your solution is better. I wanted to do it in the same way, but failed
> to find the
> correct tile sizes for areas that cover e.g. 7 split rectangles (the middle
> is not on the grid)
>
> two small points:
> 1) the variable names midLon and midLat are a bit missleading, since
> I dont use osmosis, where do you need it for?
>
I usually use osmosis for merging, so I missed that you suggested
osmconvert.
Unlike osmosis omsconvert produces no error messages on merging the
josm-made island to the coastline-file or directly to the offshore tile. But
the output doesn´t se
Hi,
attached patch for the performance branch improves the Locator.
a) It uses a kd-tree to implement the findNextPoint() method.
This may also be usable in other routines, did not look at this until now.
The implementation is based on the demo in wikepedia:
http://en.wikipedia.org/wiki/K-d_tree
Hi WanMil,
yes, your solution is better. I wanted to do it in the same way, but failed
to find the
correct tile sizes for areas that cover e.g. 7 split rectangles (the middle
is not on the grid)
two small points:
1) the variable names midLon and midLat are a bit missleading, since you
don't spli
Hi Gerd,
that's great!
Hi WanMil,
this was a very good hint :-)
Time for african boundaries was 250 secs with /branch/performance/r2225, 267
secs with trunk,
and with this patch it is now 152 secs
wow, that's more improvement than I expected.
- use simple quadtree in BoundarySaver.splitA
Hi,
why is the include of the location-rules commented
out in the default style ?
#base-style=location
Chris
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
I have been able to do further testing on my Edge 705. Although the
routing "on the fly" works on the unit, I cannot reliably use a GPX
track file, either created from a mapping website or using a previous
ride in the device history. Either the Begin and End points merge,
either the pink line is tr
17 matches
Mail list logo
