Version 2738 was committed by gerd on Sun, 06 Oct 2013
Drop points that lie outside of tile boundaries without producing
a severe error message.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Gerd,
Am 06.10.2013 13:58, schrieb GerdP:
4) For each generated polygon the POIGenerator creates a POI, the
position is calculated using method Way.getCofG(). This method
calculates the average latitude and longitude values of all points
of
Hi Gerd,
great! I have merged the changes to the mergeroads branch and it runs
fine for me. I didn't yet check a style that uses continue statements
but your work seems to be *very* reasonable :-)
WanMil
Hi all,
I think I understand now most of the miracles related to
short arcs and I am
Version 2742 was committed by gerd on Sun, 06 Oct 2013
make sure that point in road has highway count = 1 when
CoordPOI is replaced by Coord.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Hi WanMil,
I noticed that the branch had one more call to incHighwayCount().
I can't think of a situation where this causes problems, but
the call was correct.
Please merge again.
Gerd
WanMil wrote
Hi Gerd,
great! I have merged the changes to the mergeroads branch and it runs
fine for me.
Hi all,
I am still thinking about how to simplify setting the access tags in the
mergeroads branch.
Felix posted his concerns that the new handling requires much more style
coding.
At the moment my favourite changes are to add two more actions:
1. addaccess:
This adds the given value to all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 06.10.2013 20:06, schrieb WanMil:
What is your opinion about the two new actions? Do they help? Are
they sufficient? Are any other actions required?
Hi,
what about the following behavior:
all access-values are by default unset. You can set a
It's quite the same as your proposal, but without new special options.
Hi Henning,
you're right, but that's exactly what I don't like.
You propose to have a special handling for
set mkgmap:access='xxx' and
add mkgmap:access='xxx'
I think special handlings are better documented and more
On Sun, Oct 06, WanMil wrote:
It's quite the same as your proposal, but without new special options.
@All other: what do you think/prefer?
I don't mind implementing the set/add mkgmap:access behaviour if the
list favours that variant. I am just thinking about what is the most
intuitive
Hi
On the weekend went bushwalking with the Garmin Rino 650 and 62S to experiment
with the search features. I stripped all but a single OSM generated map from
the Rino 650 and used Garmin Topo, Shonky, and OSM on the 62S.
The Rino 650 search finds nothing under all POI but if I go down to say
10 matches
Mail list logo