Re: [Tagging] how to care about different seasonal road close?

2017-03-16 22:23 GMT+01:00 yo paseopor : > Idea: > > access:conditional=no @ (winter) > access:conditional=no @ (snow) > note=check availability access during first trimester > +1 I remember also a past discussion on this: https://lists.openstreetmap.org/pipermail/tagging/2016-November/030681.ht

Re: [Tagging] Is there a way to make tags better?

2017-03-16 18:55 GMT+01:00 Janko Mihelić : > What about using an existing solution, Wikibase (of which Wikidata is an > example)? > > [...] > > And countless other examples... > +1 I was thinking about this for the wiki translations. A tag description has to be translated, of course, in every la

Re: [Tagging] The direction=* tag

2017-03-16 5:13 GMT+01:00 Tod Fitch : > The “direction” tag [1] has different uses that seem disjoint to me. > >1. To specify the orientation (compass point or degrees from north) of >an object (adit or cave entrance, etc.). > > "orientation" would have been a better descriptor IMHO, but t

Re: [Tagging] The direction=* tag

On 2017-03-16 04:13, Tod Fitch wrote: The “direction” tag [1] has different uses that seem disjoint to me. 2. To specify direction (clockwise/counterclockwise) around a roundabout (not sure why this is needed as it should be apparent from local laws or specified with a “oneway=yes”).

Re: [Tagging] Vertical farming

2017-03-15 13:43 GMT+01:00 Dave Swarthout : > How about this then for the basic tagging? > > building=commercial > building:use=agriculture (1744 uses) > farming:system=vertical_farming (0 uses) > produce=marijuana > > I would still use a more specific building value (there are many types of comm

Re: [Tagging] The direction=* tag

Jumping in here to give a perspective from a routing engine (OSRM, https://github.com/Project-OSRM/osrm-backend#open-source-routing-machine). We do not handle direction tags on nodes which indicate a property for a way or a turn at an intersection. The example with stop signs and give yield signs i

Re: [Tagging] The direction=* tag

From a data consumer point of view, what type of tagging would be reasonable to indicate the, for lack of a better work, direction of travel a stop, give way or traffic light has effect? > On Mar 17, 2017, at 3:54 AM, Daniel Hofmann wrote: > > Jumping in here to give a perspective from a routi

Re: [Tagging] The direction=* tag

On the routing engine side these tags will be translated to turn penalties for specific turns, so the matching equivalent would probably be from,via,to relations. Which is not a feasible modelling in OSM realistically speaking. Simple stop signs could go on ways, but fail to capture more complex si

Re: [Tagging] The direction=* tag

Thank you for the insight. I don’t know that it is off topic though as any tagging scheme should be both achievable by a typical mapper and useful to any anticipated data consumers. Something that is easy for taggers but not useful to data consumers is just noise. Something that is useful for a

Re: [Tagging] water=pool

On Tue, Mar 14, 2017 at 11:21:17AM +, ael wrote: > On Mon, Mar 13, 2017 at 10:40:24PM +0100, Richard wrote: > > On Sat, Mar 11, 2017 at 08:24:35PM +1100, Andrew Harvey wrote: > > when using natural=water + water=pool they would become distinct (though > > adjacent) > > water body from the rive

Re: [Tagging] water=pool

On Thu, Mar 16, 2017 at 06:33:13AM +0700, Dave Swarthout wrote: > I agree about the tag water=pool. Potentially very misleading. > > Stream_pool seems okay, or perhaps waterway_pool to avoid a possible > semantic conflict when applying the tag to rivers. Are there plans to add > "riffles" as well?

Re: [Tagging] The direction=* tag

I don't agree with this: marking the direction of the traffic sign is not noise, for a driver can be VITAL, also with the meaning of the traffic sign (the main purpose of a traffic sign). Why? Because in a way with two directions we need to know to what direction traffic sign it is for. It is not t

Re: [Tagging] Vertical farming

On 17-Mar-17 09:55 PM, Martin Koppenhoefer wrote: 2017-03-15 13:43 GMT+01:00 Dave Swarthout >: How about this then for the basic tagging? building=commercial building:use=agriculture (1744 uses) farming:system=vertical_farming (0 uses) produ

Re: [Tagging] water=pool

Thanks for all the input. There are mixed viewpoints, but I'm leaning towards using and documenting on the wiki water=stream_pool as "A small and usually deep collection of fresh water, supplied by a spring, or occurring along a stream or river. Water velocity in the pool is typically much lower th

Re: [Tagging] The direction=* tag

If micro mapping, then the stop sign is usually not in the center of the traveled way (though I have occasionally seen some there). For micro mapping, place a node for the sign where it exists on the side of the road and then use the compass direction to indicate how it is facing. As it is detac

Re: [Tagging] The direction=* tag

On 03/17/2017 05:24 PM, Tod Fitch wrote: > The “highway=stop | give_way” tag on a node on way might be used by > map rendering, which probably doesn’t care if it has forward or > backward tagging. OsmAnd does a callout for highway=stop but unfortunately ignores the direction=* tag as of the versio

Re: [Tagging] The direction=* tag

> > But at present I am pretty sure that map rendering can’t use > “direction=forward | backward”. It can (and my rendering does) use the > compass points and/or degrees values for rotating icons in the point > symbolizer. As you can see Kendzi3D plug-in [1] and a style for JOSM [2] do it with f

Re: [Tagging] Vertical farming

Adding information about building level or height is fine, if one has the data in hand but IMO it is optional information, like operator and website, etc. The core tags are what we're discussing here. @Martin, I fully realize "commercial" buildings have many variations and styles, as your link po