Hi experts,
I am not happy with the current code regarding address data.
My understanding so far:
- we have the --bounds option to specify precompiled bounds
- we have the LocationHook that is used to assign tags
mkgmap:admin_level2 to. mkgmap:admin_level10 and
mkgmap:postcode.
- we have
sorry, pressed the send button too early.
The 2nd advantage of this approach is that the HousenumberGenerator
can easily create pseudo nodes to evaluate the tags
for a given point on the road.
This would be much better than cutting roads into peaces.
Gerd
From: gpetermann_muenc...@hotmail.com
Hi,
On Thu, Apr 16, Gerd Petermann wrote:
I think we should change that.
My proposal:
Instead of inc/address we have a file address (on the same level
like points, lines, etc)
this file is evaluated before the rules in points/lines/polygons
when it exists. Probably the class
Hi Thorsten,
my thinking was that inc/address does not set any
tags which are not prefixed with mkgmap:
I see that your inc/address is a bit different to that in the default style,
but the only significant difference that I found is this rule:
mkgmap:country=DEU | mkgmap:country=AUT |
Hi experts,
Hi Gerd,
I am not happy with the current code regarding address data.
My understanding so far:
- we have the --bounds option to specify precompiled bounds
- we have the LocationHook that is used to assign tags
mkgmap:admin_level2 to. mkgmap:admin_level10 and
mkgmap:postcode.
-
Hi Thorsten,
okay, I think I understand now. You don't use
any of the possible tricks in your style, but
you don't want to loose the possibility to do it.
Right?
I think that is a good point against my proposal.
Gerd
Date: Thu, 16 Apr 2015 09:08:22 +0200
From: ku...@suse.de
To:
On Thu, Apr 16, Gerd Petermann wrote:
Hi Thorsten,
okay, I think I understand now. You don't use
any of the possible tricks in your style, but
you don't want to loose the possibility to do it.
Right?
No, I already use some of the tricks to prevent that
inc/address set mkgmap:street is
Hi Thorsten,
okay, got it. Did not think about mkgmap:street
and even the default style has to use this trick.
Sorry for the noise.
I think what I was looking for is a set of rules
which depend only on the tags created by the LocationHook.
After the latest news regarding the img format
I try
Hi Steve,
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 am now trying to change the housenumber code so
that it produces the additional lists. If I got that right,
we
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
Hi Andrzej,
thanks a lot. The display tool does not yet show the city names or
zip codes, so I am not sure how they are stored, but I hope that Steve
is already trying to (de)code that.
I now have to think about the rules for my plausibility checks,
some are obsolete, some new are required.
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
14 matches
Mail list logo
