Uh, not really. Original phrasing of that principle was very unfortunate, and thus many people misunderstood it. The more correct term is “Don’t mistag for the renderer” or “Don’t lie to the renderer”.
Tagging correct data for a renderer (or router or any other data consumer), even if that data is used only by one single data consumer at some point in time, is not only fine, but encouraged. In fact, entering correct data which will be used by random data consumers is the whole point of OSM existence.
What is not okay, and the reason why that principle exist, is clearly given as an example on wiki above:
For example, if landuse=industrial shows up as a pink area on one of maps, and you have a flowerbed full of pink roses, then tagging your flowerbed as landuse=industrial would be incorrect and must be avoided. Instead, you should accurately tag the flowerbed with landuse=flowerbed and improve the renderers so they understand how to show it.
Screenshot from development version, just an experiment, very far from release readiness.
However, UrbanEye3D 2.0 with trees and some other improvements will be released shortly after the new version of JOSM. JOSM guys are a bit behind schedule: 26.03
The new version of the plugin 2.0.0 Trees, Roads and Rivers is out!
this is a big update for the plugin and I have worked on it about 3 months. I hope you will like it. Here’s what’s new.
What’s New
1. 2D Ground Plane
Buildings no longer float. The ground surface is displayed with “flat” objects - roads, lawns, rivers, and lakes. This flat layer is rendered based on downloaded OSM data using a custom MapCSS style. Alternatively, a satellite background can be enabled, as before.
Height is taken from the height tag. If height tag is missing, the circumference tag is used to estimate height.
Two tree textures are included: broadleaved and needle-leaved (based on the leaf_type tag).
More textures could be added for various species/genus – if you’re good with graphics, feel free to contribute!
3. Whole Multipolygons
Missing members of multipolygons and building relations can be downloaded automatically. Without this, the map often looked broken – like buildings cut in half or water spilling everywhere. The Building relation, which seemed completely useless, turned out to be good for something.
You can turn it off in the plugin preferences if multipolygons in your area are too large.
4. Background Processing
The UI no longer freezes when you load a large area. Everything is calculated in the background. It still takes time to render a big area, but at least JOSM stays responsive.
Contribute
This is a one‑person project, so any help is welcome:
Textures for more tree species. See some details here.
Since you added the trees, I see your plugin on the way from an object viewer to a full area viewer. If so, the 3D view you render could not only be used as edit-helper but to use the 3D view in applications. Exporting an area “tile” as a gilt/GLB file would enable that.
