[OSM-talk] Prolification of the amenity tag
80n80n at gmail.com
Wed Nov 29 11:01:44 GMT 2006
This looks like a candidate for using a tag prefix to demarcate it from the
main map features collection.
Anyone can use a wiki username as a prefix without risk of conflict with
some other tag that has the same name but a different purpose. The owner of
that wiki username can then dictate policy about how those tags can be used.
So, if you wanted to create a set of wardriving tags for example, register a
wiki username, such as wd, or war, or wardrive, and then add tags like
war:amenity=wifi, war:channel=6, war:encryption=WAP, etc. You can also
document the tagging scheme on the war user page so that others can
understand the meaning of these tags and create them when appropriate.
I don't think there should be any rigid limits put on what data can be
stored although it seems like in many cases it is better to store a link to
some external source than to store the data in OSM where it most likely
wouldn't get updated and will become stale. In the above example the
detailed attributes of the wifi source might be better described by
reference to some external web site. But that decision is entirely up to
the person collecting and maintaining the data.
On 11/29/06, Andy Robinson <Andy_J_Robinson at blueyonder.co.uk> wrote:
> >-----Original Message-----
> >From: talk-bounces at openstreetmap.org [mailto:talk-
> >bounces at openstreetmap.org] On Behalf Of bvh
> >Sent: 29 November 2006 9:49 AM
> >To: talk at openstreetmap.org
> >Subject: [OSM-talk] Prolification of the amenity tag
> >While this mail has been triggered by the proposal for
> >amenity="wifi", it is more about the amenities tag in general and
> >that is why I bring it up here instead of on the wiki.
> >My take on the amenities tag is that recent proposals have drifted to
> >uses that are better served outside the openstreetmap database.
> >For starters a (maybe) trivial conclusion : we do not want to tag
> >everything that has a location (even if we could). So the question
> >is where do we draw the line?
> >My take on it is that we should try to tag everything that is needed
> >to find your way (the purpose of a map, no?) So it's perfectly
> >reasonable to tag football stadiums and churches because by virtue
> >of being easily recognizable they serve as a point of reference
> >out there in the field.
> >However, amenities="wifi", ="park_ride", ="clinic" etc don't share
> >that purpose. There is little value to add them to a map.
> >That is not to say there is no value in knowing where these things are.
> >But that purpose is better served with a seperate project
> >(let's call it openyellowpages). And certainly in Web 2.0 spirit
> >of things there would be a mash-up so that if a user searches for
> >all wifi zones in her neighbourhoud she'd get back a map from
> >openstreetmap and an overlay from openyellowpages.
> >So, I'll be voting against nearly all amenities proposals that are
> >currently being considered and I hope to find some people who think
> >the same about this.
> >(Coincidently don't we need a page in the wiki with refused proposals?
> >one thing we can immediatly add is flight paths.)
> While I agree on gpx uploads of flightpaths being withheld from OSM I do
> that only because it confuses. However with respect to other geo data that
> represents physical features (and the wifi access point hardware is a
> physical feature) then why do we care what type of geo data the database
> holds. I'm concerned that we are not thinking outside the box if we set
> restrictions based on traditional mapping. If my kids want to produce a
> of all the bubble gum machines in the area why would I not want to let
> (tooth decay permitting!), they would be producing an innovative map and
> which has value to a certain group of society. It was the potential for
> innovation in mapping that drew me to OSM in the first place.
> The counter argument is that the location of bubble gum machines should be
> held in someone else's database. Fine if it exists and is free and open.
> in reality few sites are collecting data right now in the way OSM does and
> think we should encourage others to go forward with this rather than block
> them from the head start they can gain by using existing OSM data. Look at
> Freethepostcode, ok its not within the OSM database as such but its
> on the same principals and we now have the NPE site collecting and
> from the same idea. OSM is the ideal jumping off point from which to
> a specific area of mapping.
> Thus personally I believe that there should be few restrictions on the
> of geo data but that the way information is tagged and associated needs
> additional work. Bubble gum machines are arguably not an amenity although
> think wifi access points certainly are in our modern world. Improvements
> the extensibility of the Map Features tagging schema is something I'm
> working on and hopefully will make some of these issues less contentious.
> >cu bart
> >talk mailing list
> >talk at openstreetmap.org
> talk mailing list
> talk at openstreetmap.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the talk