[OSM-dev] SVN rails_port questions: browse, relicensing

2009-02-03 Thread Frederik Ramm
Hi, I was looking for the source code that is behind the www.openstreetmap.org/browse functionality but could not find it. I'm not a rails expert but I think that since I cannot find anything in config/routes.rb, it is probably not implemented in rails, is it? The reason is that I want to

Re: [OSM-dev] Osmosis: Extracting by polygon

2009-02-03 Thread Brett Henderson
Rolf Bode-Meyer wrote: Hello! I'm on my first steps with osmosis. I managed to create a polygon file from the outer way on a multipolygon in the OSM data. So osmosis now should extract exactly the area bounded by that way. And indeed it mostly does, but some nodes of the way of the

Re: [OSM-dev] SVN rails_port questions: browse, relicensing

2009-02-03 Thread Frederik Ramm
Hi, Frederik Ramm wrote: I was looking for the source code that is behind the www.openstreetmap.org/browse functionality but could not find it. I'm not a rails expert but I think that since I cannot find anything in config/routes.rb, it is probably not implemented in rails, is it?

Re: [OSM-dev] SVN rails_port questions: browse, relicensing

2009-02-03 Thread Thomas Wood
http://trac.openstreetmap.org/browser/sites/rails_port_branches/api06/app/controllers/browse_controller.rb 2009/2/3 Frederik Ramm frede...@remote.org: Hi, I was looking for the source code that is behind the www.openstreetmap.org/browse functionality but could not find it. I'm not a rails

Re: [OSM-dev] Osmosis: Extracting by polygon

2009-02-03 Thread Rolf Bode-Meyer
2009/2/3 Brett Henderson br...@bretth.com: Check the definition of insideness in the above link, just because a point lies on the boundary doesn't necessarily mean it will be considered inside the shape. Reading that and comparing the results I see they're matching. So I comprehend what's

Re: [OSM-dev] Osmosis: Extracting by polygon

2009-02-03 Thread Karl Newman
On Tue, Feb 3, 2009 at 6:23 AM, Rolf Bode-Meyer rob...@gmail.com wrote: 2009/2/3 Brett Henderson br...@bretth.com: Check the definition of insideness in the above link, just because a point lies on the boundary doesn't necessarily mean it will be considered inside the shape. Reading

Re: [OSM-dev] One value per key? Why not one pair per object?

2009-02-03 Thread Jochen Topf
On Mon, Feb 02, 2009 at 03:25:57AM +0100, Stefan de Konink wrote: What is the motivation to go to the one value per key thing again. Practically everything we have been doing with OSM tags until now has assumed that keys are unique. Nearly all the software I have seen (like editors, renderers,

Re: [OSM-dev] One value per key? Why not one pair per object?

2009-02-03 Thread Ed Loach
Practically everything we have been doing with OSM tags until now has assumed that keys are unique. Nearly all the software I have seen (like editors, renderers, etc.) treat keys as if they are unique. I wondered the other day when I was adding the tag for the (maritime) museum to the

Re: [OSM-dev] One value per key? Why not one pair per object?

2009-02-03 Thread Matthias Julius
Jochen Topf joc...@remote.org writes: On Mon, Feb 02, 2009 at 03:25:57AM +0100, Stefan de Konink wrote: What is the motivation to go to the one value per key thing again. Practically everything we have been doing with OSM tags until now has assumed that keys are unique. Nearly all the

Re: [OSM-dev] One value per key? Why not one pair per object?

2009-02-03 Thread Stefan de Konink
Matthias Julius wrote: Key uniqueness robs us of some cool things but we get simplicity in return which is a price worth paying in this particular case, I think. Using the misused thing called relations we are able to do most of the things we want. But if there was a vote I would go for the

Re: [OSM-dev] One value per key? Why not one pair per object?

2009-02-03 Thread Dave Stubbs
2009/2/3 Matthias Julius li...@julius-net.net: Stefan de Konink ste...@konink.de writes: Frederik Ramm wrote: Stefan de Konink wrote: What is the motivation to go to the one value per key thing again. Opposed to unique(objectid - key - value)? As a client programmer, I say that unique keys

Re: [OSM-dev] Osmosis: Extracting by polygon

2009-02-03 Thread Stefan Keller
It's only a polygon because the tags say it is (polygon is not a fundamental primitive object in OSM), and Osmosis is tag-agnostic. Pleeease, add polygon as a fundamental primitive object in OSM! You can take 'polygon' from Simple Features for SQL (see

Re: [OSM-dev] One value per key? Why not one pair per object?

2009-02-03 Thread Matthias Julius
Stefan de Konink ste...@konink.de writes: Frederik Ramm wrote: Stefan de Konink wrote: What is the motivation to go to the one value per key thing again. Opposed to unique(objectid - key - value)? As a client programmer, I say that unique keys make everything simpler for me. It is much

Re: [OSM-dev] Osmosis: Extracting by polygon

2009-02-03 Thread Brett Henderson
Rolf Bode-Meyer wrote: Reading that and comparing the results I see they're matching. So I comprehend what's going on. But I must confess I don't agree that this is going on (though that won't help anything I guess). Either one counts the whole border as being part of the result or none of

Re: [OSM-dev] One value per key? Why not one pair per object?

2009-02-03 Thread Matthias Julius
Stefan de Konink ste...@konink.de writes: Matthias Julius wrote: Key uniqueness robs us of some cool things but we get simplicity in return which is a price worth paying in this particular case, I think. Using the misused thing called relations we are able to do most of the things we want.

Re: [OSM-dev] Osmosis: Extracting by polygon

2009-02-03 Thread marcus.wolschon
On Wed, 4 Feb 2009 00:30:42 +0100, Stefan Keller sfkel...@gmail.com wrote: It's only a polygon because the tags say it is (polygon is not a fundamental primitive object in OSM), and Osmosis is tag-agnostic. Pleeease, add polygon as a fundamental primitive object in OSM! I remember someone