[OSM-talk] OSM the mediocre alternative

[Robert (Jamie) Munro]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

SteveC wrote:
> On Sun, 2007-04-22 at 12:13 +0200, Martijn van Oosterhout wrote:
>> On 4/22/07, Christopher Schmidt <crschmidt at metacarta.com> wrote:
>>> In OSM, that would be 88. 88 queries to the API, just so I can display
>>> two features.
>> That's just bad design. There's no reason why the API can't just take
>> a list of ways and return all information (segments and nodes) needed
>> to draw that way. The way it is setup now makes it really hard to do
>> anything efficiently.
>>
>> Personally I'm for dropping segments and having ways be a list of
>> points, sort of like a polyline, but much easier on editors...
> 
> This was discussed at Essen and agreed as a Good Thing. I was surprised
> there wasn't a ticket so I added one

I think that tagging segments is probably the only sensible way to
introduce house numbers to the database. If we add a tags to the segments:

numbers_left=1-7 odd
numbers_right=2-8 even

we could interpolate the other numbers in the road. If we have to tag
the whole way with house numbers, the interpolation would be nothing
like as accurate. Having a node for every house seems way over the top
in most cases. By the way, I suggest that instead of a range, a list
would be possible where a segment has non-contiguous numbering e.g.:

numbers_left=1;1a;3;5;9

I suppose we could instead put house numbers on nodes, but where a node
is a junction between more than one road, this would get very awkward.

A node for every house just seems way over the top.

Robert (Jamie) Munro
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGK0b9z+aYVHdncI0RAleYAKDZW8tjrL8j9ipyXXnhpFaObkvgKQCfaUY5
TK5O6kC0rWjcP0o2v9zIC+c=
=kpZO
-----END PGP SIGNATURE-----