Hi
OK, it is probably too early, how about holding just a pointer
to the City if that is available. The index is available at
the time the NET section is written out.
I should have looked at the existing RoadDef. That is exactly how it
is done now: there is a single City and Zip in RoadDef.
] inc/address and --housenumbers
Hi Gerd
When you say city I understand it is an int that points to a table of
cities,
and this table also contains corresponding region and country info?
Yes, it is the index into LBL4, which is the section that is printed by
LblDisplay.
That contains
Hi Steve,
I am now trying to change the housenumber code so
that it produces the additional lists. If I got that right,
we need a new data structure containing
a) the list of Numbers (as we have now)
b) an optional list of zip codes , each a class with two fields:
int rNode;
String
.
Gerd
Date: Thu, 16 Apr 2015 14:51:17 +0200
From: po...@poczta.onet.pl
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] inc/address and --housenumbers
Hi Gerd,
I have compiled example with a road that goes across 3 cities, see
attached archive.
Road has 2 names, which are the same
Hi Gerd,
I just tried r451 on the img file from Andrzej
NetCheck complains, but NetDisplay seems to extract
most of the infos (it just doesn't decode the offsets into the LBL file)
I've just committed something to display the city names.
Its likely that there are off-by-one errors, I will
Hi Gerd
When you say city I understand it is an int that points to a table of
cities,
and this table also contains corresponding region and country info?
Yes, it is the index into LBL4, which is the section that is printed by
LblDisplay.
That contains a link to either a region or a country.
On 16/04/15 16:00, Gerd Petermann wrote:
reg. the field rNode : I think this can be any number node ?
Its the same as the house number nodes. So a routing node, or
a non-routing node, but not just a point.
I think the calculation of the int value for the combination of
city+region+country
Hi Gerd,
2) A road may be the border or very close to the border of a city.
Houses on the left side are in city A, houses on the other side are
in city B. I think in this case we should add the road twice to the
map so that address search works.
A road at the border of 2 cities can have 2
Hi Gerd
interesting. The current code in mkgmap doesn't allow multiple cities,
regions, or countries for one road. I'd like to know when that is possible.
That is correct it does not currently allow this.
The format itself, allows you to specify a zip, city, region and country
for the left
Hi Andrzej,
interesting. The current code in mkgmap doesn't allow multiple cities,
regions, or countries for one road. I'd like to know when that is possible.
Please post a link to such an img file.
Reg. road names: we often have 3 of 4 possible labels filled when a ref
existis.
I don't know if
Hi Steve,
would be great if you could help me with that.
I don't know much about the cgpsmapper sources.
Gerd
Date: Wed, 15 Apr 2015 15:06:36 +0100
From: st...@parabola.me.uk
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] inc/address and --housenumbers
Hi Gerd
Hi Steve,
I don't have to split a road because it is in different cities, I
just have to pass the information to the routines which build the
indexes.
At the very least you will have to insert a non-routing node at
the boundary if there is not one there already, so that the
city change
Hi Gerd
I don't have to split a road because it is in different cities, I
just have to pass the information to the routines which build the
indexes.
At the very least you will have to insert a non-routing node at
the boundary if there is not one there already, so that the
city change can be
Hi Gerd,
I see that discussion has gone further, do you still need example of a
map from cgpsmapper?
--
Best regards,
Andrzej
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On Tue, Apr 14, GerdP wrote:
2) A road may be the border or very close to the border of a city.
Houses on the left side are in city A, houses on the other side are
in city B. I think in this case we should add the road twice to the map
so that address search works. The problem: With the
11:03:16 +0200
From: ku...@suse.de
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] inc/address and --housenumbers
On Tue, Apr 14, GerdP wrote:
2) A road may be the border or very close to the border of a city.
Houses on the left side are in city A, houses on the other side
}
to the three files points, lines, and polygons.
Gerd
From: gpetermann_muenc...@hotmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
Date: Wed, 15 Apr 2015 11:21:55 +0200
Subject: Re: [mkgmap-dev] inc/address and --housenumbers
Hi Thorsten,
reg. mkgmap:street:
The default style has this rule almost
that uses the mkgmap:city info.
Gerd
Date: Wed, 15 Apr 2015 11:03:16 +0200
From: ku...@suse.de
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] inc/address and --housenumbers
On Tue, Apr 14, GerdP wrote:
2) A road may be the border or very close to the border of a city
and lines. I'll do that in the branch.
Gerd
Date: Wed, 15 Apr 2015 11:57:52 +0200
From: wmgc...@web.de
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] inc/address and --housenumbers
Hi Gerd,
the address rules were included in the finalize section for performance
reasons. I
Hi all,
the default style uses the include inc/address in the finalize rules
for points and lines. That means that OSM elements which are
not added to the map do not have corresponding tags like
mkgmap:city.
The problem: For the --housenumber option we want to
analyse all elements with
20 matches
Mail list logo
