Yes, Urban Eye 3D is “the new kid in town”. Really great to see live changes of JOSM edits. It lacks some features but as it is integrating code from OSM2World, it will bekomme a full Building viewer. But it can’t run stand alone and aims not to become a full world viewer.
OSM2World could be it, if it would cover not only DACH countries. Could OSM support a server And it could adopt the feature of Urban Eye to refresh a gltf-tile directly from OSM tagging data. Well, both projects are Java code and do not run in the browser. They bout should shift to CodeLine, not a big thing in days of AI (I would help). A CodeLin to WASM compiler is growing, to bring OSM2World in the browser.
For JavaScript/TypeScript we have OSMgo.org as an old and abandoned 3D renderer. And we have Streets GL! Is anyone supporting it It is open source. Does it “snap” the value “East” to walls to? It looks quite well (pic above) TypeScript/AssemblyScript may allow a version, running outside the Browser. And it could get integrated in MapLibre. OSM.de;OSM.org as a “StreetView” level.
What about F4map? (forget the “East”) Is it JavaScript only or has WASM parts? Like OSM2World, it pre-renders 3D tiles alike gltf. As often seen, it is not that perfect as it seems if you go into details. We can do better. We have to describe how to convert the tagging the 3D. We can reverse engineer F4map if it extends the OSM Wiki as far as we like this extensions. Like a roof:shape without building/part walls. To prove the imaged render documentation, I also will maintain my OBI Rust code. It could get integrated in MapLibre-rs.
Honestly, f4map is nice for everything but roofs. There it creates simply a mess, even with clear stuff and rectangular roofs. It should be ignored when considering something about roofs.
The F4 map is still essentially the only online window into the 3D world for OSM, and most of those who make 3D models in OSM use it as a viewer, so it cannot be casually written off (despite of all it obvious flaws ).
Regarding roof:direction=E. I’ve tried to explain it in another thread (and remained ununderstood). Roof direction can be arbitrary for skillion roof shape, where roof direction does not really depend on the form of the building footprint.
In case of, say, gabled roof, roof direction can be normally either along or across. S3DB does not really require renderers to produce those weird twisted oblique shapes, which arose when roof direction is not along [the longest side] or across [the longest side], but something in between, see this image:
Obviously, this shape has very little to do with real buildings. So snapping to the nearest wall direction can be a good choice.
I understand this topic as a call for more precise 3D specification, which could clarify some issues, not clearly defined by the existing specification(s).
Could you add the OSM ID of your example? Is it set like “E”? In this case it looks just wrong tagged. like even snap would not definitive as the angle is about 45 degrees of the rectangle.
There is also Streets JS - It even had (and lost) the ability to instantly render OSM tagging! But Streets.gl is not maintained/updated. There was an other instance, I forgot.
Yes, clarifying is needed. I intent to clarify how to code a renderer. But as a side effect, some fuzzy tag definition will rise and sould be improved.
The “E” for example: It never die make any sense to use this tagging. Until the snapping is added. So we should check the existing renderer and add “snap” to the tagging page.
Great news! So F4 is still mantained. Are there chances that some new roof shapes will be added, like roof:shape=crosspitched, roof:shape=side_hipped and roof:shape=apse_gabled?
And it could adopt the feature of Urban Eye to refresh a gltf-tile directly from OSM tagging data. Well, both projects are Java code and do not run in the browser. They bout should shift to CodeLine, not a big thing in days of AI (I would help). A CodeLin to WASM compiler is growing, to bring OSM2World in the browser.
