On Thu, 2015-01-29 at 08:43 +0100, Mateusz Konieczny wrote:
> Yes, my opinion is that all highway=proposed should be removed.
I think this is an absolutely awful idea.
> "after it is obvious the proposed road will never be built" sounds
> nice but
> always there will be somebody convinced that pr
2015-01-28 19:25 GMT+01:00 Frederik Ramm :
>
> If there used to be a castle and now there's a ruin, then we tag that as
> a ruin (with potential add-on info about its former castle status).
>
> If there used to be a building but all that is left is a clearing in the
> forest, then the clearing wil
2015-01-29 8:43 GMT+01:00 Mateusz Konieczny :
> OSM should map current situation - not what was there or what will be.
>
what was there and what will be is part of the current situation.
>
> "after it is obvious the proposed road will never be built" sounds nice but
> always there will be som
2015-01-29 5:41 GMT+01:00 johnw :
> if this is the proper term used for pipelines, then this would be the
> right one,
>
> Otherwise, =multi (like sports) would be the best.
>
> but you would not need such a tag, since it would be
>
> substance=gas
> substance:detailed=multiphase_gas
>
> if you ke
Warin <61sundow...@gmail.com> wrote:
>> removed:
>> (features that do not exist anymore but may still be seen on other
>> sources)
>> [@Martin: leave a mention to the other sources]
>
> I see no harm in leaving them in OSM. Untill something is built there or the
> landuse/cover changes. Leave it th
2015-01-28 19:57 GMT+01:00 Dan S :
> Hi - my 2p: yes sounds fine. I agree with others who said that
> culture=* seems a decent choice (since more flexible and less awkward
> than ethnicity=*)
>
I don't like "culture" as it is way too generic IMHO, it can mean a lot of
different stuff, and you ca
2015-01-25 12:29 GMT+01:00 Andreas Goss :
> And see also for repairs:
>> http://wiki.openstreetmap.org/wiki/Tag:craft%3Dwatchmaker
>>
>
> Or this http://wiki.openstreetmap.org/wiki/Tag:craft%3Dclockmaker -__-
>
> Still don't get the difference...
a watch is small and you have it on your wrist o
2015-01-26 2:44 GMT+01:00 johnw :
> Or does this go back to it should be "shop:jewelry=watches" or
> "shop=jewelry + jewelry=watches " problem?
this would only make sense if all shops selling watches could be considered
jewellery shops (btw: jewelry is American English, but we're using BE in
OS
Sent from my iPhone
> On Jan 29, 2015, at 8:33 PM, Martin Koppenhoefer
> wrote:
>
> shop=watches is fine, is documented and this discussion could have already
> ended some time ago ;-)
> http://wiki.openstreetmap.org/wiki/Tag:shop%3Dwatches
>
> cheers,
> Martin
Martin always goes right to
+1 to use wikidata.
I had once thinking about same purpose. :)
https://wiki.openstreetmap.org/wiki/Proposed_features/enshrine
But many place of worship in Japanese have multiple dedication gods.
And when we would like to express using semi-colon (;),
multi-lingual approach would be fail into compl
Am 29.01.2015 um 10:59 schrieb Martin Koppenhoefer:
> 2015-01-29 5:41 GMT+01:00 johnw mailto:jo...@mac.com>>:
>
>> if this is the proper term used for pipelines, then this would be
>> the right one,
>>
>> Otherwise, =multi (like sports) would be the best.
>>
>> but you would not need such a tag,
"If the proposal was from between 1960 and 1969, "within 25 years" would
have been no later than the end of 1994, possibly as early as 1985"
Every few year local government releases new plans - so in 1994 it was
planned
to start around 2020. Currently there are plans to start construction in
2030
Eric SIBERT wrote:
> I started modifying the wiki following our recent discussion.
>
> For cuisine=*, I added:
> ...
> For shop=convenience, I added (in Tags used in combination):
> ...
+1
> And latter go on with culture=* for nonfood services?
+1
Hi Martin
Martin Koppenhoefer wrote:
> The f
Richard Z. wrote:
> thank you all for the unexpected attention, the problematic text snippet
> was cut&paste from [[Comparison of life cycle concepts]] where it must
> have been lurking for some time.
[[Comparison of life cycle concepts]] is meant as an overview.
I approve very much your edit for
Mateusz Konieczny wrote:
> Yes, feature that does not exist anymore (or even never existed!) or
> is only proposed has no place in OSM.
+1. No place on rendered map and apps. +/-1. No place on DB.
> With possible caveat that features that are extremely likely to be added
> (recently destroyed bu
> I'd like to repeat once again that "substance" doesn't seem to be a nice
> key descriptor for values like ...
during the draft stage, I (we) couldn't come up with an expression that
covered everything that might one day be transported in a pipeline.
content ... too static
medium ... too spooky
On Thu, Jan 29, 2015 at 4:07 PM, Rainer Fügenstein wrote:
> during the draft stage, I (we) couldn't come up with an expression that
> covered everything that might one day be transported in a pipeline.
"fluid"?
___
Tagging mailing list
Tagging@openstre
Throwing out my ideas...
Disclaimer:
These are generic proposals for pipeline sub-tagging with example values
for illustration.
I do not want to derail this towards water/drinking_water and multi-values
(semicolon or namespaced). ;)
I propose 3 keys: use/purpose (as main subtag), state/phase and
> and what exactly is a neutron bean?
correction: should read "neutron beam"
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
On 30/01/2015 5:07 AM, Rainer Fügenstein wrote:
I'd like to repeat once again that "substance" doesn't seem to be a nice
key descriptor for values like ...
during the draft stage, I (we) couldn't come up with an expression that
covered everything that might one day be transported in a pipeline.
On 29/01/2015 3:41 PM, johnw wrote:
substance=fuel
substance:detailed=drinking_water
isn't it just as error prone as
substance=fuel
fuel=drinking_water
?
As the error is on one line it is easier for a human to pick up, either
as it is made or on checking.
An error that is a relation b
On 29 January 2015 at 22:54, Warin <61sundow...@gmail.com> wrote:
> On 30/01/2015 5:07 AM, Rainer Fügenstein wrote:
>>>
>>> I'd like to repeat once again that "substance" doesn't seem to be a nice
>>> key descriptor for values like ...
>> content ... too static
>> medium ... too spooky
>> product
On 28/01/2015 10:57 PM, Martin Koppenhoefer wrote:
if you want the "liquid" information, use
aggregate_state=liquid
IMHO for pipelines it would be more interesting to tag the pressure
and the inner diameter of the tube.
Agreed in part.
If 'we' tag what we see at the site .. then the pipe
On 29.01.2015 13:24, Satoshi IIDA wrote:
> +1 to use wikidata.
> I had once thinking about same purpose. :)
> https://wiki.openstreetmap.org/wiki/Proposed_features/enshrine
Sorry that I missed your proposal.
Indeed, it seems that the wikidata id makes the tagging of related enshrines
superfluous,
24 matches
Mail list logo
