This looks very useful. If the better rendering for tree_row gets anywhere, I 
would very much like to see the same applied to ways tagged as barrier=bollard 
(representing a row of bollards) as well (which are currently unfortunately not 
rendered at all). 

 

spacing=* sounds like a good key for that. 

 

I’m currently using maxwidth=* which for barrier=bollard is documented as 
specifying the maximum width that fits past the bollard (which in case of a row 
of bollards is basically the distance between them, but ignoring the thickness 
of the bollard itself).

 

From: Peter Elderson <[email protected]> 
Sent: Monday, 23 April 2018 21:24
To: Tag discussion, strategy and related tools <[email protected]>
Subject: Re: [Tagging] RFC - Key: spacing=*

 

Hi

I've done my homework and created a wiki proposal page 
<https://wiki.openstreetmap.org/wiki/Proposed_features/Key:spacing%3D*> .

 

I left out the spacing=nodes part because it causes confusion. The key is now 
explicitly meant to be a parameter of a group of objects such as a tree_row or 
orchard, not actual positions  of individual objects. or exact distance between 
them. 

Though I can thnk of other applications, the main purpose is adaptive 
rendering, starting with tree_row. For this to work, the default rendering 
style on OSM-carto will have to be adapted. 

I have bumped the discussion about rendering tree_row on the appropriate github 
forum. There is general support for the idea, several options have been 
discussed but whosgonnadoit? Now Marc Zoutendijk, a Dutch OSM-mapper, is 
looking into it. I am confident that he can go where no-one has gone before!

 

I'm looking forward to hearing your contributions, appreciate any help.

 

 

2018-04-18 21:38 GMT+02:00 Martin Koppenhoefer <[email protected] 
<mailto:[email protected]> >:



sent from a phone

> On 18. Apr 2018, at 21:23, Tobias Knerr <[email protected] 
> <mailto:[email protected]> > wrote:
> 
> The currently documented
> solution (using natural=tree) makes it obvious that the nodes represent
> real-world objects.


+1, with natural=tree_stump there is even a tag for the gaps (well, unless 
there is literally nothing)


cheers,
Martin 

_______________________________________________
Tagging mailing list
[email protected] <mailto:[email protected]> 
https://lists.openstreetmap.org/listinfo/tagging





 

-- 

Vr gr Peter Elderson

_______________________________________________
Tagging mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/tagging

Reply via email to