Le 29. 09. 18 à 00:53, Dave Swarthout a écrit
waterway=river
name=Tanana River
waterway=section
section=bend
section:name=Harper Bend
You can't use waterway=section + waterway=river on the same way, and you
shouldn't map overlapping ways for obvious reasons.
But you can split a waterway=river
Although the whitewater proposal is here for a long time, and it being
the only documented way to tag kayaking/canoe practise on whitewater, it
is seldom used.
Probably there is simply not enough people interested in those sports
and Openstreetmap at the same time. Maybe in a few years there wil
@Joseph,
>I suppose section=* with railway=* can be treated differently than
section=* with waterway=section, but it’s not ideaI
On second thought, I agree, it's probably not a big issue.
>These proposals all appear to keep one way for the waterway=river, with
the way split for each long section
I suppose section=* with railway=* can be treated differently than
section=* with waterway=section, but it’s not ideal.
I spent some time looking at the whitewater proposals, which introduced
tags for whitewater:section_name and whitewater:rapid_name, in addition to
whitewater grades for rapids an
One other thing about the section key I just learned from Taginfo. Although
undocumented it has had some use already to describe sections of a railway.
So maybe we need to make it easier to distinguish between those uses? Or
maybe not.
On Sat, Sep 29, 2018 at 5:53 AM Dave Swarthout
wrote:
> I
It appears I was too hasty about dismissing the reach argument. Yes, that
makes sense Colin. And Joseph's suggestion to make it more general sounds
good too. I think the name part needs to be set up to distinguish the name
of the bend or reach from that of the river because both are valid for any
s
Hi,
I opened an issue on the rendering of man_made=communications_tower on
the standard layer over on OSM-carto:
https://github.com/gravitystorm/openstreetmap-carto/issues/3414 and
think there should be a discussion about the tagging as well.
The Wiki definition is: *"**a huge tower for tran
Do canals have named sections?
Waterway=section would work for canals too, if there are such a thing as
canal reaches or sections or bends
On Sat, Sep 29, 2018 at 5:32 AM Colin Smale wrote:
> On 2018-09-28 07:37, Dave Swarthout wrote:
>
> The discussion about the definition of "reach" is intere
On Sat, 29 Sep 2018 at 06:32, Colin Smale wrote:
> The point of raising the "reach" business it to help abstracting the
> proposed tagging model to make it more generic. If we consolidate all the
> thoughts expressed so far, we can say that:
> * there can be contiguous linear sections of a river
On 28 September 2018 22:14:03 BST, Simon Poole wrote:
>
>
>Am 28.09.2018 um 18:07 schrieb Bryan Housel:
>>> I actually mentioned the issue in Milano.
>>>
>>> Essentially `traffic_sign`, `traffic_sign:forward` and
>>> `traffic_sign:backward` need to be treated as "object" tags as
>things
>>> are
Am 28.09.2018 um 18:07 schrieb Bryan Housel:
>> I actually mentioned the issue in Milano.
>>
>> Essentially `traffic_sign`, `traffic_sign:forward` and
>> `traffic_sign:backward` need to be treated as "object" tags as things
>> are now.
>>
> Let’s just do `traffic_sign=*` and consider the others
Hello, I would like to continue with fire hydrants' new tags [1].
Instead of the contested check_date=*, what do you think of
working:test_date=* [2] or working_test:date=* [3], both already in use?
Which syntax do you prefer?
[1]
https://wiki.openstreetmap.org/wiki/Proposed_features/Fire_Hydra
On 2018-09-28 07:37, Dave Swarthout wrote:
> The discussion about the definition of "reach" is interesting but IMO it's
> slightly off topic. Perhaps, because of those differences in its
> interpretation, we would be best served by not using the term at all.
The point of raising the "reach" bu
On Fri, Sep 28, 2018 at 1:38 AM Dave Swarthout wrote:
>
> The discussion about the definition of "reach" is interesting but IMO it's
> slightly off topic. Perhaps, because of those differences in its
> interpretation, we would be best served by not using the term at all.
Except that I would li
Thank you for this, Bryan. One small favor: could you add a "Change
direction" button like you have for one-way streets? It makes it much
easier if I guess wrong :)
On Fri, Sep 28, 2018 at 6:58 PM Philip Barnes wrote:
>
>
> On 28 September 2018 17:31:18 BST, Kevin Kenny
> wrote:
> >On Fri, Se
On 28 September 2018 17:31:18 BST, Kevin Kenny wrote:
>On Fri, Sep 28, 2018, 5:34 AM Marc Gemis wrote:
>
>> I still highway=give_way and highway=stop with
>> direction=forward/backward (which is used by OsmAnd AFAIK).
>
>
>Me, too - I went around my neighbourhood last year adding them. OSMand
>
On Fri, Sep 28, 2018, 5:34 AM Marc Gemis wrote:
> I still highway=give_way and highway=stop with
> direction=forward/backward (which is used by OsmAnd AFAIK).
Me, too - I went around my neighbourhood last year adding them. OSMand does
indeed recognize them.
Describing what a driver might see w
> I actually mentioned the issue in Milano.
> Essentially `traffic_sign`, `traffic_sign:forward` and
> `traffic_sign:backward` need to be treated as "object" tags as things are now.
>
Let’s just do `traffic_sign=*` and consider the others an unfortunate mistake
that can go away.
> See pages 2
I actually mentioned the issue in Milano.
Essentially traffic_sign, traffic_sign:forward and traffic_sign:backward
need to be treated as "object" tags as things are now.
See pages 29 and 30
https://drive.google.com/open?id=1LVmZIaEvd1K7mYVqDLnrhC5-jHLHy0lQ
And I should note that iD has "plot" as
I still highway=give_way and highway=stop with
direction=forward/backward (which is used by OsmAnd AFAIK).
On Fri, Sep 28, 2018 at 9:26 AM Anton Klim wrote:
>
> Missed the point when direction= suddenly became a no go for traffic sign
> mapping.
>
>
> 28.09.2018, в 3:51, Bryan Housel написал(а):
Am 28.09.2018 um 03:06 schrieb Dave Swarthout:
@Joseph - I wanted to avoid using that particular top-level tag,
waterway, because there would be no simple way to add a name different
from that of the waterway=river itself. Unless we invent a new tag
something like name:bend=Harper Bend.
The k
Missed the point when direction= suddenly became a no go for traffic sign
mapping.
28.09.2018, в 3:51, Bryan Housel написал(а):
> Hey Tagging List!
>
> While reviewing a pull request to add Traffic Sign presets to iD, I came
> across a tagging issue with how traffic sign directions are tagg
22 matches
Mail list logo
