Re: [OSM-dev] support for osm2pgsql with relation type=route

2008-04-14 Thread 80n
On Mon, Apr 14, 2008 at 6:48 PM, Robert (Jamie) Munro <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Jon Burgess wrote: > | This should avoid problems like the roundabout next to Heathrow T5[1] > | which has both highway= and landuse= tags. Because of the landuse

Re: [OSM-dev] support for osm2pgsql with relation type=route

2008-04-14 Thread Dave Stubbs
On Mon, Apr 14, 2008 at 6:48 PM, Robert (Jamie) Munro <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > Jon Burgess wrote: > | This should avoid problems like the roundabout next to Heathrow T5[1] > | which has both highway= and landuse= tags. Because of the lan

Re: [OSM-dev] support for osm2pgsql with relation type=route

2008-04-14 Thread Robert (Jamie) Munro
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jon Burgess wrote: | This should avoid problems like the roundabout next to Heathrow T5[1] | which has both highway= and landuse= tags. Because of the landuse tag | this is currently only appearing in the polygon table but it really | needs to appear i

Re: [OSM-dev] osm2pgsql fails on current data

2008-04-14 Thread Andy Allan
On Mon, Apr 14, 2008 at 4:43 PM, Marcus Wolschon <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > Hello Martijn. > > | highway=unclassified;cycleway > > This at least is not unreasonable. > It is an unclassified road featuring a bicycle-lane. No. Your example

Re: [OSM-dev] osm2pgsql fails on current data

2008-04-14 Thread Marcus Wolschon
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Martijn. | highway=unclassified;cycleway This at least is not unreasonable. It is an unclassified road featuring a bicycle-lane. | sport=baseball;basketball For me this makes perfect sense. I have seen my fair share of sport-fields that are

Re: [OSM-dev] osm2pgsql fails on current data

2008-04-14 Thread Martijn van Oosterhout
On Mon, Apr 14, 2008 at 12:31 PM, Lauri Hahne <[EMAIL PROTECTED]> wrote: > But unfortunately there are cases when it's necessary to have multiple > values. The most common of these is if two refs share a road. A road > near me actually officially has two refs and two int_refs. Google > renders

Re: [OSM-dev] osm2pgsql fails on current data

2008-04-14 Thread Dave Stubbs
On Mon, Apr 14, 2008 at 11:31 AM, Lauri Hahne <[EMAIL PROTECTED]> wrote: > On 14/04/2008, Martijn van Oosterhout <[EMAIL PROTECTED]> wrote: > > You're right, I was thinking too far ahead. I won't complain if they > > enter "6;8" and they shouldn't complain when it's treated as if they > > had

Re: [OSM-dev] osm2pgsql fails on current data

2008-04-14 Thread Lauri Hahne
On 14/04/2008, Martijn van Oosterhout <[EMAIL PROTECTED]> wrote: > You're right, I was thinking too far ahead. I won't complain if they > enter "6;8" and they shouldn't complain when it's treated as if they > had entered "6". I was thinking that we should point out that using > semicolons is nic

Re: [OSM-dev] osm2pgsql fails on current data

2008-04-14 Thread Tom Hughes
In message <[EMAIL PROTECTED]> Martijn van Oosterhout <[EMAIL PROTECTED]> wrote: > On Sun, Apr 13, 2008 at 10:30 PM, Frederik Ramm <[EMAIL PROTECTED]> wrote: >> 3. "work with what we've got" and fix the data we get out of the >>system to suit our needs. >> >> Dave's patch is in the s

Re: [OSM-dev] osm2pgsql fails on current data

2008-04-14 Thread Martijn van Oosterhout
On Sun, Apr 13, 2008 at 10:30 PM, Frederik Ramm <[EMAIL PROTECTED]> wrote: > 3. "work with what we've got" and fix the data we get out of the >system to suit our needs. > > Dave's patch is in the spirit of option 3, and frankly I think that > way is the only acceptable way. You're right, I