[Tagging] [OpenStreetMap] social facility

[Sam Vekemans]

Yup, i prefer the tagging-tree approach where more tags can be used to
narrow down the specifics of what it is you are trying to map.

For the end user who is using a Garmin GPS, there are only a specific
set of key/value combinations, so i want to ensure that the key/value
used in OSM can quickly be narrowed down to the as descriptive as 2 or
3 words can be used.

However, in osm-land, it is possible to include presets when users
chose a feature to map.  ie.
You shouldn't be able to select a 'surface' key, until you have used
another key/value pair.   (highway=* landuse=* amenity=* name=* area=*
etc.) something needs to be used for the surface is chosen.   It
answers the question "Surface OF what?"

And also, 'building=yes'  is an attribute key, and can be used along
with many other tags, where the feature 'most likely' is a building.

Because in osm-land both schools of thought (less tags with use of '_'
and or ':')  are used interchangeably, we can have a 'tagging
re-direct system', which is used outside of osm-land, which will tell
the renderers and map makers (products) and map editing softwares  the
list of all of the map features that are written in multiple ways, but
mean the same thing.

So anyway, thanks for the tips :)  I'm now adding more to the
SchemaTroll 2.01 tagging schema system.    Hopefully it will work :)
Once i get somewhere cohesive, i'll write the wiki page / external
document about it.

Cheers,
Sam

P.S. So to answer the below question, Sure, yes we can make it work :)


On Tue, Sep 14, 2010 at 12:31 PM, Sean Horgan <seanhorgan at gmail.com> wrote:
> Good feedback Peter and thanks for passing along the Crossing wiki.  Some
> comments below:
>
> On Tue, Sep 14, 2010 at 10:39, Peter Wendorff <wendorff at uni-paderborn.de>
> wrote:
>>
>> Hi.
>>
>> On 14.09.2010 18:59, Sean Horgan wrote:
>>
>> [...]
>>
>> Also, if I wanted to capture specific data about that they offered, I'd
>> like to follow the amenity:recycling tagging scheme
>> (http://wiki.openstreetmap.org/wiki/Tag:amenity%3Drecycling):
>> + homeless_shelter:programs=jobs
>> + homeless_shelter:meals_served=breakfast
>> + homeless_shelter:lodging=yes
>> + homeless_shelter:emergency_medical=yes
>> Is this a good model to follow?
>>
>> I'm not sure.
>> I think, there are two general approaches to simulate a tree-style tagging
>> scheme like this.
>> The first is to use more keys (as you do here with homeless_shelter:*),
>> the second is to use more values and to concatenate multiple values by ;
>> (like you will have at
>> homeless_shelter:meals_served=breakfast;lunch
>> (compare crossing=island;traffic_signals)
>>
>
> Ok, I'm following you.  Similar to amenity:recycling, many of the examples
> in Crossing follow a yes/no model:
>
> traffic_signals:sound=yes/no
>
> traffic_signals:vibration=yes/no
>
> traffic_signals:arrow=yes/no
>
> traffic_signals:minimap=yes/no
> However, for a finite and relative small (< 10) set of values, I prefer a
> multivalued value string like "homeless_shelter:meals=breakfast;lunch" over
> something like this:
> homeless_shelter:breakfast=yes
> homeless_shelter:lunch=yes
> homeless_shelter:dinner=no
> For amenity:recycling, there is no limit to what could be recycled so I
> think it makes more sense to follow the yes/no model as a single value could
> get extremely large.  The same appears to go for traffic_signals (I never
> thought you could break those down so discretely!).
>>
>> Both are good for some reasons:
>> using less keys provides easy access for the whole group of values;
>> using less values is more easy to parse and search - there is no string
>> slicing needed.
>>
>> But:
>> I would not mix these together.
>
> I prefer consistency as well but I think I would only apply that for a
> particular tag.  To continue the meals example, homeless_shelter:meals could
> be defined as a multivalued list from a set of known values (e.g.
> {no;breakfast;lunch;dinner;takeout}) while a list of programs/services
> offered by the shelter would follow the yes/no model:
> + homeless_shelter:lodging=yes
> + homeless_shelter:meals=no
> + homeless_shelter:job_placement=yes
> + homeless_shelter:veterans_services=yes
> + homeless_shelter:emergency_medical=yes
>
>
> Feedback is greatly appreciated!
> --
> Sean
>>
>> Perhaps that's only my POV - feel free to argument against.
>>
>> regards
>> Peter
>>
>> _______________________________________________
>> Tagging mailing list
>> Tagging at openstreetmap.org
>> http://lists.openstreetmap.org/listinfo/tagging
>>
>
>
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/tagging
>
>