pipeline and highway on the same element is a poor idea. Lets start from
fact that underground pipeline
should be tagged with location=underground.
2014-12-03 23:14 GMT+01:00 Rainer Fügenstein :
>
>
> MR> I do not know why anyone should tag one OSM way both with power=* and
> MR> railway=*.
>
> a
There are a number of possible shades of potable:
* It's not designated, but in an area where all faucet water is
potable (e.g. major cities, fountains in rome).
* It's designated potable.
* It's designated as untested (e.g. "drink at your own risk")
* It's designated non-potable by color or speci
On 4/12/2014 10:14 AM, tagging-requ...@openstreetmap.org wrote:
Date: Wed, 3 Dec 2014 22:13:43 +0100
From: Kotya Karapetyan
To: "Tag discussion, strategy and related tools"
Subject: Re: [Tagging] Feature Proposal - RFC - Water tap
Message-ID:
Content-Type: text/plain; charset="
Thank you Michael for your contribution and clear examples.
2014-12-03 23:14 GMT+01:00 Rainer Fügenstein :
>
> just imagine a city like vienna, drawing one or more man_made=pipeline
> ways parallel to nearly every highway=* - a nightmare, editing-wise.
>
> in these cases, it would be better to u
On Wed, Dec 3, 2014 at 4:37 PM, Darrell Fuhriman wrote:
> One open question for me, which we I would appreciate guidance on, is
> whether or not to import address points for each unit number in a building,
> where we have them. Right now, we are not planning to, but it would be easy
> to change t
MR> I do not know why anyone should tag one OSM way both with power=* and
MR> railway=*.
and here I contradict my own oppinion:
In many cities, there's a gas pipeline running under (almost) every
street, providing gas to domestic homes (as do water, sewage ...)
just imagine a city like vienna,
let me sum this up:
- loop=yes, a technical term in use and accepted by the pipeline
industry ("loop configuration"), was "voted down" in favour of a more
generic term, that can also be used in other areas (flow_direction=*).
and also not to have one more tag.
- mount=* was abandoned in favour o
>
> water_source:sparkling=yes | no | unknown
>>>
>>>
>>> in analogy: "water:effervescent" (or ~:sparkling)
>>>
>>
>> I don't mind using the word "effervescent"; however: is there any
>> recommendation that we should use as "simple" words as possible, to achieve
>> the above goals 1 and 3? I k
Hi,
Am 2014-11-23 um 23:09 schrieb François Lacombe:
> As suggested on Talk page of Power transmission refinement proposal, power
> lines and cable should be described with a key giving their usage in the
> network.
> https://wiki.openstreetmap.org/wiki/Talk:Proposed_features/Power_transmission_re
2014-12-03 19:19 GMT+01:00 François Lacombe :
> since all features concerned by my proposal and railway one will be tagged
> with power=* or railway=*
yes, and some will be tagged with power=* and railway=* and that's where
the fun begins...
cheers,
Martin
I understand your points but not convinced at all.
Railway guys did it right.
For me, the best example is the location=* tag as mentioned before.
It is actually used in many fields of knowledge, with different and maybe
specific values for each.
No namespace was introduced and all values shouldn'
* Richard Welty [2014-11-27 11:09 -0500]:
> actually, specifying the shield with a URL for an svg file was an older
> approach.
And, I should note, one that I consciously did not use. I believe it was
Richard Weait who pointed out that grabbing an arbitrary image, chosen by
someone else, off of
* johnw [2014-11-28 13:11 +0900]:
> > On Nov 28, 2014, at 9:53 AM, Richard Welty wrote:
> > the basic scheme doesn't require anything new or unusual in
> > route relation tagging, just care and consistency.
>
> I look forward to seeing his RFC page then ^_^
Well, the point is that you can rende
2014-12-02 21:50 GMT+01:00 Kotya Karapetyan :
>
> On Tue, Nov 18, 2014 at 11:11 AM, Martin Koppenhoefer <
> dieterdre...@gmail.com> wrote:
> I see hierarchy and encapsulation of tags as the means to achieve these
> three goals. That's why I also would like to avoid going "outside" the tag
> by usi
2014-12-03 12:35 GMT+01:00 althio forum :
> Long post to follow so this is a short version.
> (1) proposing tagging for zone like ZTL:
> highway/zone:traffic=IT:limited_traffic_zone
>
there is actually a proposal for this kind of zone, to be mapped as a
polygon, useful e.g. for rendering (with n
Long post to follow so this is a short version.
"too long; didn't read" [TL;DR]:
(1) proposing tagging for zone like ZTL:
highway/zone:traffic=IT:limited_traffic_zone
(2) proposing access=authorised
(3) I don't like acronyms
(4) attempt to modify "access" categories and labels
Long post:
Old pro
2014-12-03 6:35 GMT+01:00 Friedrich Volkmann :
> I guess that these regulations are not done by explicit listing, but by
> definition of ZTLs in the laws. So all you need is a tag like highway=ztl
> or
> highway=pedestrian+pedestrian=ztl, and some comment on the default access
> page.
>
It seem
2014-12-02 21:05 GMT+01:00 Ole Nielsen :
> On 02/12/2014 14:48, Martin Koppenhoefer wrote:
>
>>
>> In short, I think we should add more access classes to the wiki:
>>
>> - armed_forces=yes/no etc. (identifier cannot be "military" because that
>> key is taken)
>>
>>
> I think military_personnel=* i
W dniu 2014-12-03 11:02, Mateusz Konieczny pisze:
"Are there really road signs with additional plates listing all of
that stuff?"
Some egregious example from Poland:
https://www.google.pl/maps/@50.0661474,19.9390468,3a,41.6y,230.88h,84.66t/data=!3m4!1e1!3m2!1s-rGw0-IoKZGQKjyZKeRl0Q!2e0?hl=en
"Are there really road signs with additional plates listing all of that
stuff?"
Some egregious example from Poland:
https://www.google.pl/maps/@50.0661474,19.9390468,3a,41.6y,230.88h,84.66t/data=!3m4!1e1!3m2!1s-rGw0-IoKZGQKjyZKeRl0Q!2e0?hl=en
"How big are those signs, and how long does it take f
On 2014-12-03 at 06:35:29 +0100, Friedrich Volkmann wrote:
> Are there really road signs with addional plates listing all of that stuff?
often, yes
> How big are those signs, and how long does it take for a driver to read them?
enought time that you just don't stop to read them and assume that
21 matches
Mail list logo
