Re: [Tagging] [Talk-us] destination:street

[Marc Gemis]

tools such as http://osm.mueschelsoft.de/cgi-bin/render.pl support the
semi-column notation, not the number notation. I assume most
destination signs in Germany and neighbouring countries are using the
semi-column notation.



On Sat, Jan 21, 2017 at 11:00 PM, yo paseopor  wrote:
> With destination:x you mark in a easy way the correspondence with other
> tags.Destination:2 goes with distance:2 and with destination:symbol:2 for
> example. It is an easy way to see the correspondence. For people like me (we
> have less idea to program something like a preset or a style in JOSM, for
> example) it is easier to identify , clarify and verify the :2 value than the
> second of a list of 5 with semicolons. Also these values are easier to be
> followed.
>
> And also you can read it at
> https://wiki.openstreetmap.org/wiki/Semi-colon_value_separator#When_NOT_to_use
>
> Cheers (Salut i Senyals)
> yopaseopor
>
> ___
> Tagging mailing list
> Tagging@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
>

___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Re: [Tagging] Exit list signs?

[yo paseopor]

But you put these nodes for a way. A road traffic sign without a way is
also meaningless. So I have to mark in which direction will be showed of
the way the traffic sign is owned by. If you put a stop sign in a road with
oneway=no ...will stop the two directions at the same time at the same
place? Meaningless. Also it will be interesting to say in which side of the
road will be the traffic sign if I put it as a node in the way.

Also :forward and :backward scheme are used by ways so we can use the same
tags and propierties talking about the same things (traffic signs informs
you about things will happen in the way you are driving - in the way you
are mapping)

Cheers (salut i senyals)
yopaseopor
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Re: [Tagging] Exit list signs?

[John F. Eldredge]

As far as I know, a node does not have a direction, so "forward" or 
"backward" are meaningless. A way has a direction, a node does not.



On January 21, 2017 3:48:33 PM yo paseopor  wrote:


I think Traffic sign is a NODE, IN the way, as I map stop,give way,or city
limit. But putting a traffic sign does not free you of putting tags and
values in segments of a way as maxspeed (I map the traffic sign as a node
but I repeat the maxspeed=value in the segment). A good solution for making
standard and international would be to use the same propierties as the way
for the traffic_sign node for the future standarization and
internationalization. Also for exit_to signs.

Cheers (salut i senyals)
yopaseopor



--
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Re: [Tagging] [Talk-us] destination:street

[yo paseopor]

With destination:x you mark in a easy way the correspondence with other
tags.Destination:2 goes with distance:2 and with destination:symbol:2 for
example. It is an easy way to see the correspondence. For people like me
(we have less idea to program something like a preset or a style in JOSM,
for example) it is easier to identify , clarify and verify the :2 value
than the second of a list of 5 with semicolons. Also these values are
easier to be followed.

And also you can read it at
https://wiki.openstreetmap.org/wiki/Semi-colon_value_separator#When_NOT_to_use

Cheers (Salut i Senyals)
yopaseopor
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Re: [Tagging] Exit list signs?

[yo paseopor]

I think Traffic sign is a NODE, IN the way, as I map stop,give way,or city
limit. But putting a traffic sign does not free you of putting tags and
values in segments of a way as maxspeed (I map the traffic sign as a node
but I repeat the maxspeed=value in the segment). A good solution for making
standard and international would be to use the same propierties as the way
for the traffic_sign node for the future standarization and
internationalization. Also for exit_to signs.

Cheers (salut i senyals)
yopaseopor
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Re: [Tagging] [Talk-us] destination:street

[Marc Gemis]

Why is destination:X better than a list with semi-colons ?

I think that semi-colons in the destination tags are already to
wide-spread to be stopped. Data consumers like OsmAnd have no problem
with the semi-colons.

m

On Sat, Jan 21, 2017 at 3:21 PM, yo paseopor  wrote:
> Other solution
> destination=Main Street
> destination:2=7th Avenue
> destination:3=Downtown Mappersville
> destination:4=Karte County Courthouse
> ... and so on.
>
> (for legible reasons a "standard" traffic sign does not show more than 3/4
> items by direction at sign).
> also this will be "portable" to other countries and other signs systems
> (based on Vienna convention for example).
>
> yopaseopor
>
> ___
> Tagging mailing list
> Tagging@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
>

___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

[Tagging] charging stations: CCS socket wiki conflict

[lucas-osm]

Howdy,

on charging stations we distinguish between socket types like Type1, Type2, 
Chademo etc.
But currently the english wiki version differs from the german one on tagging 
the CCS (combined charging system) socks.
The english version uses socket:type2 and socket:type2_combo (CCS) to 
characterize the models. The german however uses socket:type2 and socket:combo2.

These tow different special tags describing the same socket have led to some 
confusion among some german mappers. I’ve already seen some stations containing 
both tags.

Looking at the history it seems like the user Mentor changed the tag 
socket:combo2 to socket:type2_combo in June 2015. According to his comment that 
time the tag was unused, so I assume he adapted the type1_combo style to the 
type2 socket to use an uniform style. But sadly he forgot to edit the other 
languages as well.

Usage according to taginfo:
   socket:type2_combo 135
   socket:combo2 72

So my question is how should we proceed? Should we stay with those tow 
different tags? Or only use one? But which one? I’d suggest staying with the 
english socket:type2_combo, to be consistent between Type1 and Type2 sockets.


Lucas

___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Re: [Tagging] Exit list signs?

[Martin Koppenhoefer]

sent from a phone

> On 21 Jan 2017, at 10:23, yo paseopor  wrote:
> 
> You can use traffic_sign:forward (or backward) if it is correct=US:(get the 
> code in the MUTCD) and then apply all the other tags and values of exit_to 
> scheme.


how would you do this? on a way or on a node? Is the node part of a way or 
isolated?


cheers,
Martin 
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Re: [Tagging] [Talk-us] destination:street

[yo paseopor]

Other solution
destination=Main Street
destination:2=7th Avenue
destination:3=Downtown Mappersville
destination:4=Karte County Courthouse
... and so on.

(for legible reasons a "standard" traffic sign does not show more than 3/4
items by direction at sign).
also this will be "portable" to other countries and other signs systems
(based on Vienna convention for example).

yopaseopor
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

[Tagging] advertising

[Paul Desgranges]

Hello all,

This mail to launch some discussions on advertising 
 tag. 


I have personnaly been slowly working on this tag during the last two 
years, with the idea that at the end, if we could have advertising 
devices properly specified in OSM, and one day all advertising devices 
stored in OSM, it could bring the necessary tools and information to 
citizens to have some control on advertisings in the public space...


So I spent time on discussing with and presenting to different kinds of 
people, specifying, prototyping and experimenting ways of mapping 
advertising devices  on OSM, 
and then, after these design steps, I performed during the last 6 months 
many little addings and changes on advertising wiki pages. These addings 
were done without discussing them with "tagging" list  (except one), and 
I received recently (only recently) an indignant mail from someone 
exposing that all these new points should never have been commited to 
OSM wiki without being discussed and approved first by OSM community. He 
is right. I recognize my clumsiness, hope it is not too late to have 
these discussions, not to late to find a consensus and decide of what 
can be kept and what can be improved. So I wish we can start from now on 
'tagging' list several little threads on advertising tags... Depending 
on results of threads discussions, what is not commonly shared and 
accepted will be removed or changed, so that the way of mapping 
advertising devices is improved at the end. If this overall work can be 
done slowly by surely during 2017, that could be fine.


So I will try to animate one first thread and see how it goes... There 
are many things to discuss...


This first thread can be for example related to the way the advertising 
devices are supported .


I ll start this first thread next week to take into account your 
potential returns on this preliminary introduction mail first, if any.


Thank you

Paul


___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Re: [Tagging] [Talk-us] destination:street

[Paul Johnson]

On Fri, Jan 20, 2017 at 2:13 PM, yo paseopor  wrote:

> Little apreciation:
> Please, no multiple values,no semicolon.Better subtags
>

That doesn't always work.  Fictional example, but one that does come up
routinely, particularly around small to moderate sized towns and rural
America (imagine a big-green-sign).

Main Street
7th Avenue
Downtown Mappersville
Karte County Courthouse

There you'd have a perfectly valid reason to have multiple destinations and
destination:streets...
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Re: [Tagging] Feature Proposal - RFC - dog toilets

[David Bannon]

Thanks Joost, I'd prefer option one or four. wrt lack of porcelain, the 
term "toilet" can also be used to refer to the room where the porcelain 
thing is located. So dog_toilet seems quite accurate.


But dog* or pet* ?  I do see people traveling with a cat but would be 
very surprised if a cat was comfortable using a doggy smelling place. I 
cannot image any other pet being very keen either. So rather than your 
99% dog use, I'd suggest its 100% dog for practical purposes.  Anyone's 
experience different ?


David


On 20/01/17 19:36, joost schouppe wrote:

Hi,

There were some previous discussions on how we could tag designated 
areas for dogs to urinate/defecate. They are quite common, but 
unfortunately there are many different tags going around for lack of 
documentation.


I have added a section to an old proposal page with these options 
(also links to the previous discussions I know of here). I'm not sure 
how we can get the comments here to translate to reducing the proposal 
to just one tagging option? Maybe have a pre-vote?


https://wiki.openstreetmap.org/wiki/Proposed_features/Dog_Poop_Area

Description:
This is an area designated for pets (dogs) urinate and excrete. Unlike 
dog_park label, the main objective of the area is not that dogs play. 
It is usually small and fenced areas, but can also just be a 
designated patch of grass by the side of the road. It is known as 
pee-can in some countries.




Joost Schouppe
OpenStreetMap  | 
Twitter  | LinkedIn 
 | Meetup




___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Re: [Tagging] Exit list signs?

[yo paseopor]

You can use traffic_sign:forward (or backward) if it is correct=US:(get the
code in the MUTCD) and then apply all the other tags and values of exit_to
scheme.

Also you can put the codes via Traffic Signs US JOSM preset.
In a future the preset will help you to add the other tags and values as It
does in Spain.

Salut i senyals
yopaseopor
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging