If it's only a problem of routing, wouldn't it be better to let the router
do the job? The way would have to be tagged with something like
"numbering=distance", with the correct orientation (from start to end), and
then it would be easy for a program to find out where #23 is.
2009/10/11 John Smith
2009/10/12 Simone Saviolo :
> If it's only a problem of routing, wouldn't it be better to let the router
> do the job? The way would have to be tagged with something like
> "numbering=distance", with the correct orientation (from start to end), and
> then it would be easy for a program to find out
Martin Koppenhoefer wrote:
> 2009/10/10 OJ W :
> > multiple plans would overlap each other and look weird?
>
> look weird where? I guess these would not be rendered in standard maps
> (or just in advanced planning phases and for main plans like
> motorways, airports, etc.).
>
> I made a proposal:
On Mon, Oct 12, 2009 at 4:15 AM, John Smith wrote:
> The only problem then is how to tag the start/end of a numbering
> section, based on that document major roads are broken up into
> sections of 100km.
Relation: node for start, node for end, list of ways to connect from
start to end
__
On Monday 12 October 2009 14:34:42 Anthony wrote:
> On Mon, Oct 12, 2009 at 4:15 AM, John Smith
wrote:
> > The only problem then is how to tag the start/end of a numbering
> > section, based on that document major roads are broken up into
> > sections of 100km.
>
> Relation: node for start, node
2009/10/12 Cartinus :
> On Monday 12 October 2009 14:34:42 Anthony wrote:
>> On Mon, Oct 12, 2009 at 4:15 AM, John Smith
> wrote:
>> > The only problem then is how to tag the start/end of a numbering
>> > section, based on that document major roads are broken up into
>> > sections of 100km.
>>
>>
2009/10/12 Anthony :
> On Mon, Oct 12, 2009 at 4:15 AM, John Smith wrote:
>> The only problem then is how to tag the start/end of a numbering
>> section, based on that document major roads are broken up into
>> sections of 100km.
>
> Relation: node for start, node for end, list of ways to connect
On Monday 12 October 2009 15:02:11 John Smith wrote:
> 2009/10/12 Cartinus :
> > On Monday 12 October 2009 14:34:42 Anthony wrote:
> >> On Mon, Oct 12, 2009 at 4:15 AM, John Smith
> >
> > wrote:
> >> > The only problem then is how to tag the start/end of a numbering
> >> > section, based on that d
2009/10/12 Cartinus :
> And how are you going to find the start and end of those sections without
> surveying? You won't, not unless you have some external data to import (and
> you didn't mention anything about that).
Long sections of highways are an exception rather than the rule, and
more likel
On Mon, Oct 12, 2009 at 9:02 AM, John Smith wrote:
> 2009/10/12 Anthony :
>> On Mon, Oct 12, 2009 at 4:15 AM, John Smith
>> wrote:
>>> The only problem then is how to tag the start/end of a numbering
>>> section, based on that document major roads are broken up into
>>> sections of 100km.
>>
>>
2009/10/12 Anthony :
> On Mon, Oct 12, 2009 at 9:02 AM, John Smith wrote:
>> 2009/10/12 Anthony :
>>> On Mon, Oct 12, 2009 at 4:15 AM, John Smith
>>> wrote:
The only problem then is how to tag the start/end of a numbering
section, based on that document major roads are broken up into
>
2009/10/12 Anthony :
> Surveying a few points every 100km is easier than surveying every
> house. And it's likely that most of the starting/end points will
> already be in the database (e.g. the intersection of X Street and Y
> Street).
>
Most roads won't be 100km long, and the start points will
On Mon, Oct 12, 2009 at 10:04 AM, Peter Childs wrote:
> 2009/10/12 Anthony :
>> Surveying a few points every 100km is easier than surveying every
>> house. And it's likely that most of the starting/end points will
>> already be in the database (e.g. the intersection of X Street and Y
>> Street).
I'll have to admit that I haven't been surveying for *missing* numbers - I
have been only collecting the beginning and end of each group. A search by
address number would yield quite an accurate location. But the reverse
case, using my data in the OSM database as a postal mailing address
va
On Mon, 12 Oct 2009, Cartinus wrote:
> > > The only problem then is how to tag the start/end of a numbering
> > > section, based on that document major roads are broken up into
> > > sections of 100km.
> >
> > Relation: node for start, node for end, list of ways to connect from
> > start to end
>
>
On Tue, 13 Oct 2009, Peter Childs wrote:
> 100km is the distance from hmm Washington
> to Baltimore or London to Oxford (give or take) if your going to only
> survey a few points in that distance,
Each main road in my area will be easily 70 to 140km in length
eg Hay to Balranald is 129km.
The popu
On Mon, Oct 12, 2009 at 4:48 PM, Mike N. wrote:
> There are plans in the US to import Tiger address interpolation
> information - which is intentionally obfuscated for privacy reasons by law.
> Tobias mentioned a possible tag interpolation:complete=yes to represent
> fully accurate address inte
Mike N.:
> Tobias mentioned a possible tag interpolation:complete=yes to represent
> fully accurate address interpolation, which sounds like a simple solution.
> If it is necessary to tag estimated address interpolation differently, it
> would be good to know before the Tiger address interpolat
> 2) define a way to enter estimated/incomplete interpolation.
> The way to enter incomplete interpolation info could resemble the
> Karlsruhe schema (incomplete_interpolation=* or whatever) or it could be
> combined with a dedicated TIGER addressing scheme as Anthony suggests. I
> don't know anyt
19 matches
Mail list logo
