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_ce
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 Ap
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 address:
On 25.04.2011 23:06, Clinton Gladstone wrote:
> On Apr 25, 2011, at 19:21, WanMil wrote:
>
>> I have committed changes to the locator branch which implements the
>> usage of separate precompiled splitted boundary files.
> This seems like a quite plausible approach. I'll try it out.
>
> By the way
On Apr 25, 2011, at 19:21, WanMil wrote:
> I have committed changes to the locator branch which implements the
> usage of separate precompiled splitted boundary files.
This seems like a quite plausible approach. I'll try it out.
By the way, for others who attempt this, there were a few typos i
Version 1925 was commited by marko on 2011-04-25 19:45:25 +0100 (Mon, 25 Apr
2011)
Translate landmark=chimney as man_made=tower.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi!
> * Why do you want to use the merge for landuse types only? Why not for
> buildings?
I think about towns with many separate stand-alone buildings. When the are all
merged, the whole town is a single building. For rows of flats it's OK.
> Do you have a short draft how you want to detect t
> Hi!
>
> Did you ever think about merging areas mapped to the same garmin type when
> they touch?
> I'm thinking about an algorithm that for each zoom level checks, if two areas
> touch, and when yes merge them when they have the same garmin type.
>
> The motivation: At the moment, areas that ar
Hi!
Did you ever think about merging areas mapped to the same garmin type when they
touch?
I'm thinking about an algorithm that for each zoom level checks, if two areas
touch, and when yes merge them when they have the same garmin type.
The motivation: At the moment, areas that are mapped with
I have committed changes to the locator branch which implements the
usage of separate precompiled splitted boundary files.
How does it work?
* 1st step: Extract the boundary data
Download an osm dump (e.g. the europe extract from geobfabrik).
Extract the boundary data using osmosis:
osmosis --rb
> 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 when the MP is processed to
>
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 ever been reported).
And here it is attached...
..Steve
Index: src/uk/me/parabola/imgfmt/sys/Directory.java
===
Hello
> Exception in thread "main" java.lang.AssertionError
> at uk.me.parabola.imgfmt.sys.Directory.sync(Directory.java:160)
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 ever been reported
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 when the MP is processed to
avoid
14 matches
Mail list logo
