-
Notifications
You must be signed in to change notification settings - Fork 819
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
render trees with variable size according to diameter_crown=*
#4690
Comments
Would require revisiting the idea of ground unit rendering - see #1290. The current semi-transparent fill style of tree rendering is poorly suited for this because it would obscure everything under the trees (which can in areas with many trees be a large percentage of the map area). It also increases the likeliness that tree symbols are confused with mapped woodland geometries (especially when you have multiple overlapping trees). See also discussion on #4448.
|
I like the idea rendering bigger and older trees more prominently. The current rendering looks great on tree rows, but not so much if you have one big important tree. Would it be technically possible to render according to diameter_crown but decrease the size if there are features nearby? |
This is not practical. |
Some quick testing assuming the crown diameter is represented true to scale suggests that this really only shows a noticeable difference at zoom 19. There are considerable issues with this inter alia:
Broadly speaking I think this is largely a specialised requirement which lies outwith the general terms of reference of Carto-OSM. One minor remark is that people do continue to map trees as areas, often using natural=wood, example in Cardiff. Summary: I don't think this is appropriate for Carto-CSS, but could be added to a repertoire of desiderata for any specialist render for woods and trees. If wanted in Carto-CSS, then much more research on rendering on various backgrounds is needed. |
I would agree on all points. The Catalunya 1:1000 maps indeed show some interesting design ideas - thanks for pointing to those. We should strive for displaying some more widely tagged properties of trees (#4690 (comment) - in particular leaf_type and leaf_cycle come to mind). If we manage to do that in a way that works well, if mappers more widely come to tag sizes of trees in some form and if we in general make progress in developing a viable concept for the highest zoom levels (z19+), we can think about if and how something in this direction would also be possible here. I am closing this as declined for these reasons. |
what about rendering trees according to their crown diameter?
something like this:
The text was updated successfully, but these errors were encountered: