2014-11-14 10:57 GMT+01:00 François Lacombe :
> I personnaly find some interest in man_made=technical_cabinet instead of
> man_made=street_cabinet
> The "street" term is certainly restrictive when such cabinet can be found
> far from streets.
>
> man_made=street_cabinet should be documented as exp
Hi all,
Thank you Martin
It has been documented as voted yesterday
http://wiki.openstreetmap.org/wiki/Street_cabinet
A disambiguation chapter has been added to help anyone who want to deal
with traffic signals or accepted monitoring stations
http://wiki.openstreetmap.org/wiki/Street_cabinet#Disa
How would I go about documenting the garbage/refuse cabinets? Just get a
picture and put it into the wiki, or is there some other way?
because it is a brand new proposal, I’m unsure of the procedure to extend it.
Javbw
>
> It has been documented as voted yesterday
> http://wiki.openstreetmap.
A large amount of values can be added to street_cabinet key.
I think you should only open a thread on Talk page to let other
contributors discuss about it and relay the discussion here on @tagging
http://wiki.openstreetmap.org/wiki/Talk:Tag:man_made%3Dstreet_cabinet
No need to complex proposal pr
adding to Talk page
On naming of newly voted man_made=street_cabinet
http://wiki.openstreetmap.org/wiki/Talk:Tag:man_made%3Dstreet_cabinet
A few old & new proposals for actual naming are:
man_made=street_cabinet
man_made=technical_cabinet
man_made=outdoor_cabinet
man_made=cabinet
man_made=street
2014-11-17 12:10 GMT+01:00 althio forum :
FWIW, the term "man_made=street_cabinet" has just been approved by almost
unanimous voting. Why does this discussion start now?
man_made=street_cabinet
> is implicitly rejecting 'countryside cabinet' or cabinets in
> motorways, parks, fields, train sta
2014-11-15 22:47 GMT+01:00 fly :
> The major advantage about backward/forward is the editor support once
> the way direction is reversed.
>
>
+1, also this way you give information about the direction of flow relative
to the osm way, while flow_direction=oneway doesn't imply any specific
directio
Thank you Althio,
2014-11-17 12:10 GMT+01:00 althio forum :
> man_made=street_cabinet
> is implicitly rejecting 'countryside cabinet' or cabinets in
> motorways, parks, fields, train stations, airports and so on.
>
Yeah I would rather agree.
We also have the highway=* tag to describe one and eac
2014-11-14 5:03 GMT+01:00 johnw :
> A couple more landuse cases were added. I’m going to ask now if it is a
> good idea to specifically exclude Police/fire/safety and give them their
> own landuse(s).
this can be very different from one country to another. E.g. in Italy there
are lots of diffe
2014-11-17 13:19 GMT+01:00 Martin Koppenhoefer :
>
>
> FWIW, the term "man_made=street_cabinet" has just been approved by almost
> unanimous voting. Why does this discussion start now?
>
Because of some comments written lately on friday evening when the vote was
about to end.
The only one opposi
2014-11-14 12:09 GMT+01:00 Pieren :
> I don't think we need a civic subkey in landuse. When I see the
> growing list, it will finally generate very small landuse polygons in
> OSM. This is not the intend of the OSM "landuse".
>
there is no indication of this, the wiki remains very generic and do
street_cabinet=waste had already been discussed during the proposal process,
but not yet added during the voting.
the value 'waste' is more consistent with existing amenity tagging than
refuse or garbage.
I have added it to categories and examples to the wiki, feel free to add a
picture,
some e
2014-11-17 13:53 GMT+01:00 Tom Pfeifer :
> the value 'waste' is more consistent with existing amenity tagging than
> refuse or garbage.
>
the objects that have been brought up as examples have been of private
nature, i.e. not an amenity for osm terms. I wouldn't include private waste
bin protec
On 17/11/2014 13:19, Martin Koppenhoefer wrote:
man_made=street_cabinet
is implicitly rejecting 'countryside cabinet' or cabinets in
motorways, parks, fields, train stations, airports and so on.
IMHO it is not. Don't read this "overliterally".
Indeed - like 'Openstreetmap' which,
We have finally 12 votes: 11 times “yes” and 1 time “no”. I think this
could be considered as approved …
Lukas
Lukas Sommer
2014-11-02 7:57 GMT+00:00 Lukas Sommer :
> Hello.
>
> After commenting period, now is starting the voting for the junction
> (only) tagging at
> https://wiki.openstreetmap
Martin, Jean-Marc, I appreciate the feedback. You are voicing some
good elements. I am not totally convinced yet about generic vs
specific. Fairly generic tag like 'man_made=cabinet' sounds very
sensible as first level. Furthermore I do feel other proposal I have
seen like 'street_' and 'technical_
On 17/11/2014 15:14, althio forum wrote:
Martin, Jean-Marc, I appreciate the feedback. You are voicing some
good elements. I am not totally convinced yet about generic vs
specific. Fairly generic tag like 'man_made=cabinet' sounds very
sensible as first level. Furthermore I do feel other proposal
2014-11-17 15:43 GMT+01:00 Jean-Marc Liotier :
> One may have suspected a French telco etymological bias as we call those
> cabinets 'armoires de rue' - literally 'street cabinet'... But as the
> proposal's page history and its approval signatures show, the consensus is
> actually international.
>
On Mon, Nov 17, 2014 at 3:43 PM, Jean-Marc Liotier wrote:
> I agree with your arguments - my personal choice would be technical_cabinet.
> I nevertheless chose to approve the proposal because I considered this issue
> minor compared
> to all the work that went in organizing the scheme...
> expe
On 17.11.14 16:18, Martin Koppenhoefer wrote:
>
> yes, street cabinet is the actual name for this kind of thing, so using this
> as tag seems best to describe what this proposal aims to describe. Simply
> search for "street cabinet" in google (or another image search engine) then
> research images
MK> +1, also this way you give information about the direction of flow relative
MK> to the osm way, while flow_direction=oneway doesn't imply any specific
MK> direction, it only states that the direction is not reversible.
proposal updated in this regard.
__
What about introducing a name space:
water_source:potable=designated | mineral | heilwasser (I failed to find a
good English-language analogue, could someone help please?)
water_source:sparkling=yes | no | unknown
water_source:nonpotable=compromised | designated
In principle, details regarding the
> On Nov 17, 2014, at 9:34 PM, Martin Koppenhoefer
> wrote:
>
>
> 2014-11-14 5:03 GMT+01:00 johnw mailto:jo...@mac.com>>:
> A couple more landuse cases were added. I’m going to ask now if it is a good
> idea to specifically exclude Police/fire/safety and give them their own
> landuse(s).
>
> On Nov 17, 2014, at 11:43 PM, Jean-Marc Liotier wrote:
>
> On 17/11/2014 15:14, althio forum wrote:
>
> I may have been stretching the 'Openstreetmap' case a bit.
We were discussing how to properly tag kilns, with their method of firing and
how many chimneys they have, so I don’t think you
> On Nov 17, 2014, at 9:48 PM, Martin Koppenhoefer
> wrote:
>
> there will be more people with even more ideas and classification needs.
> Therefor the foo=bar, bar=x way of subtyping, which implies there is only one
> kind of subtyping, should generally be deprecated in favor of more verbose
25 matches
Mail list logo
