Re: [Tagging] Feature Proposal - RFC - (consulate)-->(office=diplomatic)

2018-11-11 Thread Colin Smale
On 2018-11-11 21:51, Graeme Fitzpatrick wrote: > Just for the sake of asking a theoretical question that I know would probably > never appear in real life :-) > > Would / could you also use the multi-letter codes as you show eg NATO, WTO, > SEATO? > > & a mixture of them, so the British Amba

Re: [Tagging] How to include the new speed limits of Madrid (Spain)?

2018-11-11 Thread Alejandro Moreno
Thanks OSMDoudou. I have read discussion and I have seen that there aren't a clear conclussion. I'll be aware if something new is defined. El lun., 5 nov. 2018 16:17, OSMDoudou < 19b350d2-b1b3-4edb-ad96-288ea1238...@gmx.com> escribió: > It reminds of this earlier discussion: > https://lists.op

Re: [Tagging] Reversible Road tagging

2018-11-11 Thread Paul Johnson
lanes=* should be the total number of lanes... if it's a one-lane road with two way traffic, I'd go with... lanes=1 lanes:both_ways=1 On Sun, Nov 11, 2018 at 4:01 PM Richard wrote: > On Sun, Nov 11, 2018 at 12:27:57AM -0600, Paul Johnson wrote: > > Are we talking a 1 lane or a 3 lane road? Bec

Re: [Tagging] Feature Proposal - RFC - (consulate)-->(office=diplomatic)

2018-11-11 Thread Allan Mustard
Yes, absolutely.  For example, the Turkmen ambassador in Brussels is accredited to both Belgium and the European Union. It's not hypothetical at all, but rather very much real life. On 11/12/2018 1:51 AM, Graeme Fitzpatrick wrote: > > > On Sun, 11 Nov 2018 at 21:42, Allan Mustard

Re: [Tagging] Reversible Road tagging

2018-11-11 Thread Richard
On Sun, Nov 11, 2018 at 12:27:57AM -0600, Paul Johnson wrote: > Are we talking a 1 lane or a 3 lane road? Because that looks like it's > describing a 3 lane road. looks like 1 lane to me but the example would not work for other reasons. We could do lanes=0 # this is "default" for routers/app

Re: [Tagging] How to tag named group of named water areas?

2018-11-11 Thread Paul Allen
On Sun, Nov 11, 2018 at 8:59 PM Graeme Fitzpatrick wrote: > > > On Sun, 11 Nov 2018 at 22:16, Paul Allen wrote: > >> >> It's vile. There are cheat sheets, but it's still vile. However, >> there's also a visual editor. Which >> isn't vile, but is somewhat sub-optimal (I usually end up editing

Re: [Tagging] How to tag named group of named water areas?

2018-11-11 Thread Mateusz Konieczny
11. Nov 2018 02:40 by daveswarth...@gmail.com : > I've been a programmer in my earlier life so I'm not a newbie when it comes > to looking at and interpreting code but the markup language for the Wiki is, > IMHO, simply horrible.  Yes, it can rival and win wi

Re: [Tagging] How to tag named group of named water areas?

2018-11-11 Thread Graeme Fitzpatrick
On Sun, 11 Nov 2018 at 22:16, Paul Allen wrote: > > It's vile. There are cheat sheets, but it's still vile. However, there's > also a visual editor. Which > isn't vile, but is somewhat sub-optimal (I usually end up editing the > source despite it being vile). > Got a link to them, Paul? >

Re: [Tagging] Feature Proposal - RFC - (consulate)-->(office=diplomatic)

2018-11-11 Thread Graeme Fitzpatrick
On Sun, 11 Nov 2018 at 21:42, Allan Mustard wrote: > >- target =* where * is >the two-character ISO 3166-1 alpha-2 code > for the receiving >(accrediting) country or organization or t

Re: [Tagging] How to tag named group of named water areas?

2018-11-11 Thread Richard
On Sun, Nov 11, 2018 at 08:40:44AM +0700, Dave Swarthout wrote: > Yes, the Wiki is far from perfect. That's a big reason we have these > endless debates. But how should we go about fixing it? An additional issue > for me is the difficulty of adding information to the Wiki. I've been a > programmer

Re: [Tagging] Estimated values for height

2018-11-11 Thread Sergio Manzi
Yes, agreed, but in our user case we are importing official government data about historical/monumental/landmark trees and one of the fields that will be imported is the survey date (survey:date). If, at a second time, someone will update info about the tree height I *hope* he/she will have the

Re: [Tagging] Estimated values for height

2018-11-11 Thread Andy Townsend
On 11/11/2018 15:12, marc marc wrote: taginfo only count the old/ugly schema with the source on objects in stead of changest. for a source tag, it's a count a bad pratice :) No, putting a source on an object is not "bad practice".  If the source for all of the objects in a changeset is the sa

Re: [Tagging] Feature Proposal - RFC - (consulate)-->(office=diplomatic)

2018-11-11 Thread Allan Mustard
Proposed primary (first-level) key in the current version of the proposal is office=diplomatic.  On 11/11/2018 4:56 PM, Sergio Manzi wrote: > > Hello Allan, > > sorry, I'm a late comer to the discussion, so there might be something > I've/am missed/missing, but... > > From your description I under

Re: [Tagging] How to tag named group of named water areas?

2018-11-11 Thread marc marc
Le 11. 11. 18 à 13:15, Paul Allen a écrit : > On Sun, Nov 11, 2018 at 1:42 AM Dave Swarthout wrote: >> I've been a programmer in my earlier life so I'm not a newbie when >> it comes to looking at and interpreting code but the markup language >> for the Wiki is, IMHO, simply horrible. >

Re: [Tagging] Estimated values for height

2018-11-11 Thread marc marc
taginfo only count the old/ugly schema with the source on objects in stead of changest. for a source tag, it's a count a bad pratice :) don't forget that : - tree is growing, so next year, the information that the measurement was made by a laser with the accuracy of the device will all be out of

Re: [Tagging] How to tag named group of named water areas?

2018-11-11 Thread Paul Allen
On Sun, Nov 11, 2018 at 1:42 AM Dave Swarthout wrote: > Mateusz, > > I've been a programmer in my earlier life so I'm not a newbie when it > comes to looking at and interpreting code but the markup language for the > Wiki is, IMHO, simply horrible. > It's vile. There are cheat sheets, but it'

Re: [Tagging] Feature Proposal - RFC - (consulate)-->(office=diplomatic)

2018-11-11 Thread Sergio Manzi
Hello Allan, sorry, I'm a late comer to the discussion, so there might be something I've/am missed/missing, but... From your description I understand that "embassy=*", "consulate=*" and "liaison=*" will be new first level keys: wouldn't it be better to make them secondary level keys under the

Re: [Tagging] Feature Proposal - RFC - (consulate)-->(office=diplomatic)

2018-11-11 Thread Allan Mustard
Here, please take a look at the updated Tagging section of the proposal and see if that solves the issue.  I include a link to the Wikipedia article on ISO 3166-1 alpha-2 codes. https://wiki.openstreetmap.org/wiki/Proposed_features/office%3Ddiplomatic#Tagging *Current Proposal:* * establish fo

Re: [Tagging] Feature Proposal - RFC - (consulate)-->(office=diplomatic)

2018-11-11 Thread Allan Mustard
Colin is correct.  I have added target=* to the proposal.  country=* is already there.  If there are multiple target countries (the U.S. Embassy in Colombo, for example, also covers the Maldives in addition to Sri Lanka) would it not be possible to tag as target=LK;MV ?  On 11/11/2018 3:52 PM, Col

Re: [Tagging] Feature Proposal - RFC - (consulate)-->(office=diplomatic)

2018-11-11 Thread Allan Mustard
Host might be a nicer word, but in diplo-speak it is possible to have a different host from the entity to which the mission is accredited (think of the various missions to the World Trade Organization in Geneva: target=WTO, host=CH. On 11/11/2018 11:49 AM, Graeme Fitzpatrick wrote: > > > On Sun, 1

Re: [Tagging] Estimated values for height

2018-11-11 Thread Sergio Manzi
Hello everybody, I'm the one who, in the Italian mailing list, first brought out the issue about how to tag estimated heights (/in our context it was about trees height/). My first proposal has been to use a new sub-key in which to store estimated values, as in "height:estimated=10". Then I sa

Re: [Tagging] Feature Proposal - RFC - (consulate)-->(office=diplomatic)

2018-11-11 Thread Colin Smale
On 2018-11-11 11:27, Warin wrote: > On 11/11/18 20:05, Colin Smale wrote: > > On 2018-11-11 07:49, Graeme Fitzpatrick wrote: > > But wouldn't it be covered by the name eg "Australian Embassy to Russia"? > > We should not rely on free-text fields like "name" to convey information that > belo

Re: [Tagging] Feature Proposal - RFC - (consulate)-->(office=diplomatic)

2018-11-11 Thread Warin
On 11/11/18 20:05, Colin Smale wrote: On 2018-11-11 07:49, Graeme Fitzpatrick wrote: But wouldn't it be covered by the name eg "Australian Embassy to Russia"? We should not rely on free-text fields like "name" to convey information that belongs in a structured form... The text clearly ident

Re: [Tagging] Estimated values for height

2018-11-11 Thread bkil
Yes, that sounds reasonable. Also there's height:accuracy if you know your error. On Fri, Nov 9, 2018 at 11:42 AM Dave Swarthout wrote: > You can also use height=* for both and add a "source:height=estimated / > measured" tag with that to have a value that is usable by the apps and > tools but s

Re: [Tagging] Feature Proposal - RFC - (consulate)-->(office=diplomatic)

2018-11-11 Thread Colin Smale
On 2018-11-11 07:49, Graeme Fitzpatrick wrote: > But wouldn't it be covered by the name eg "Australian Embassy to Russia"? We should not rely on free-text fields like "name" to convey information that belongs in a structured form...___ Tagging mailing l