How does mkgmap process the addr: tags in POIs? For instance, take the
following POI (http://www.openstreetmap.org/browse/node/918409138)
addr:city=Abu Dhabi
addr:country=AE
addr:housename=Fairmont Bab al Bahr
phone:+971 2 654 3238
In Mapsource or on the GPS, the restaurant is given the
On Tue, Apr 26, 2011 at 10:06:59AM +0400, Charlie Ferrero wrote:
Does mkgmap ignore addr:housename? What about addr:full and
addr:housenumber...?
addr:street and addr:housenumber works, but addr:housenumber=12-14
(meaning two adjacent properties on the same side of the street) becomes
12 Apt.
El 25/04/11 18:57, WanMil escribió:
I get a lot of warnings of the form Non way element X in multipolygon
Y (e.g. Non way element 247735163 in multipolygon 339577) in which X is
a correct admin_centre node of a boundary multipolygon relation. Would
it be possible to detect admin_centre tag
dear Steve,
here is the output from your debug messages. Please have a look to them.
cheers
Michael
Am 25.04.2011 17:16, schrieb Steve Ratcliffe:
I have another patch. It may not fix your problem (although it does,
at least, fix a different problem - one however that I don't believe
has
Hi list
I remember many discussions and comments about how mkgmap produces
Garmin's legacy format only and the NT format is still a mystery. Today,
I was pointed at a discussion of the Polish UMP project (similar to OSM,
strongly concentrated on Poland and surrounds). As I happen to be Polish
On 26.04.2011 17:43, Bartosz Fabianowski wrote:
Hi list
I remember many discussions and comments about how mkgmap produces
Garmin's legacy format only and the NT format is still a mystery. Today,
I was pointed at a discussion of the Polish UMP project (similar to OSM,
strongly concentrated
Hi,
I created a merged map using osmosis:
$ ./osmosis --rb finland.osm.pbf --rb germany.osm.pbf --rb us-west.osm.pbf
--merge --merge --wx DE_FI_USW.osm
which results in an uncompressed XML output map DE_FI_USW.osm of ~36G in size.
So this maps contains three different countries which do not
Hi list
I remember many discussions and comments about how mkgmap produces
Garmin's legacy format only and the NT format is still a mystery. Today,
I was pointed at a discussion of the Polish UMP project (similar to OSM,
strongly concentrated on Poland and surrounds). As I happen to be
Is this only for country boundaries, or also relevant for all other
boundaries like states, cities and so on..
At the moment all boundaries tagged with an admin_level are used.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
On 26.04.2011 19:08, WanMil wrote:
Hi list
I remember many discussions and comments about how mkgmap produces
Garmin's legacy format only and the NT format is still a mystery.
Today,
I was pointed at a discussion of the Polish UMP project (similar to
OSM,
strongly concentrated on
On 26 April 2011 18:08, WanMil wmgc...@web.de wrote:
What's the difference between 'old' Garmin format and NT format?
Is it that NT maps are using the GMP subformat to group tiles into
larger packages? Or are there any other specifics?
The word on the street is that newer features like speed
On 26 April 2011 18:21, Felix Hartmann extremecar...@gmail.com wrote:
Basically no additional features require NT. (not even 3d buildings or
lanes or real junction view and so on). I think 1 or 2 special
things need NT format though.
Ah, I should have waited a minute before pressing send. Do
On 26.04.2011 19:22, Dermot McNally wrote:
On 26 April 2011 18:08, WanMilwmgc...@web.de wrote:
What's the difference between 'old' Garmin format and NT format?
Is it that NT maps are using the GMP subformat to group tiles into
larger packages? Or are there any other specifics?
The word on
See my next message. Speed limits and lane support needs NT.
On 26.04.2011 19:24, Dermot McNally wrote:
On 26 April 2011 18:21, Felix Hartmannextremecar...@gmail.com wrote:
Basically no additional features require NT. (not even 3d buildings or
lanes or real junction view and so on). I think
UMP maps do a primitive form of lane assist. The label at the top of the
nüvi screen changes from Some Street to Some Street (lane name) in
advance of a complex turn. That is all. No pretty pictures of junctions
and lanes:
http://ump.fuw.edu.pl/wiki/Asystent_Pasa_Ruchu
- Bartosz
On Tue, Apr 26, 2011 at 08:00:27PM +0300, Dominik Röttsches wrote:
I created a merged map using osmosis:
$ ./osmosis --rb finland.osm.pbf --rb germany.osm.pbf --rb us-west.osm.pbf
--merge --merge --wx DE_FI_USW.osm
which results in an uncompressed XML output map DE_FI_USW.osm of ~36G in size.
Hi
I think it would be great, to have a wiki page, with some explanations,
what to do for creating addressindex with locator-branch. Which
parameters should I use? What to write in style-file? etc.
I would do it myself, but I don't know, what have to be done.
Henning
Do you have a short draft how you want to detect that two areas are
touching?
When two nodes follwing each other from one polygon are inside the other. Or
on the outline of it.
Yeah, and you will have to test some 100 thousands of nodes, if they lie
inside one of a 10 thousands polygons.
This patch seems to work well, at least as far as Dermot and myself can
tell. Before the patch is forgotten and bitrots away, maybe it could be
committed?
- Bartosz
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Henning,
here my explanation in short (you may expand it and add some useful hints):
1. Download the locator branch
2. The style file must be complemented with some special address rules.
Have a look at this post
(http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2011q1/010656.html) how
it works.
Do you have a short draft how you want to detect that two areas are
touching?
When two nodes follwing each other from one polygon are inside the other. Or
on the outline of it.
Yeah, and you will have to test some 100 thousands of nodes, if they lie
inside one of a 10 thousands polygons.
On 26/04/2011 21:00, Dominik Röttsches wrote:
Hi,
I created a merged map using osmosis:
$ ./osmosis --rb finland.osm.pbf --rb germany.osm.pbf --rb us-west.osm.pbf
--merge --merge --wx DE_FI_USW.osm
which results in an uncompressed XML output map DE_FI_USW.osm of ~36G in size.
So this maps
22 matches
Mail list logo
