@SekeRob We both missed the “SOLVED” thread from @mappOG for other simple 3D render problems. Better starting a new thread! Let’s stop and continuer here.
I will replay “soon” to you your post:
p.s.: It helps, if you write the OSM ID of the building ways. There are a lot of Santa Rita on Earth.
OK, well, fixing the tag and being patient the results are in, my present quarter ‘Santa Rita’ project homing in on the end stretch. The 15 terraced houses in the row right hand bottom became indistinguishable, not even a line between the units which made me wonder whether the building:part parts were dropped and just the terrace outline rendered but the identically tagged terraces with more variations in the parts do show proper i.e. just another render quirk
at screen filling zoom, no definition at all.
Here it does show the unit borders
These were supposed to be sloped roofs towards the street… makes a rather flattish impression on me.
(The plugin that showed 3D rendering directly in JOSM stopped working some time ago).
The plugin I was referring to in my previous post was JOSM/Plugins/Kendzi3D - OpenStreetMap Wiki.
It was perfect to pan around all angles and correct on-the-fly. Sadly, it started to crash JOSM asking if wanting to remove or keep and disable. Vaguely remember it was the development version that worked as the regular would not even load.
Computers and GPUs are stupid. But manipulating the osm data isn’t a way either. The walls and roofs may in really invisible merged. Or there is a gap, a line of isolation. Anyway, yes, it would be nice to see the single houses. You only may ask the renderer to add something in the code.
It really would be help, if you mention the OSM-ID, so I could investigate.
OSM is ready, but each renderer has to handle it. Yo you know were to ask 
I am not a fan of commas, it mostly is not exact. I prefer the degree value. Do you really expect the rendere to allign to the way rectangle 
double_gabled is odd. I see multiple building parts. Otherwise you need to tag the building heights as an;value;list. May be no renderer will ever support that.
Thx for the insight. Add to that, the crosspitched in F4… comes out as regular gabled, so I’m trying the alternate word of cross_gabled to see how that’s handled. Do remember it was correctly interpreted and rendered in SteetGL, but that one unfortunately went under. The alternate fork does not seem to work for me.
The sloped roof probably need tagging as skillion with an eyeball how much height difference between low and high side… unfortunately skillion is well recognized from above, by me at least, but getting at those buildings when no ground imagery is available is not always possible.
Anyway, I’d like to keep it ‘simple’ just as the 3D topic says so it can fit in me custom preset.
edit: cross pitched
cross-gabled in F4map only produces a flat roof, returned to crosspitched, changed orientation on 1 to across and removed the orientation tag ont the other as that may be an element of misdirection. Another 24 hours wait to see what the effect might be.
(For the ‘tagging for rendered’ crowd…)
I noticed you mapped some buildings with height=0, e.g. Way: Chiesa di San Gabriele dell'Addolorata (980800003) | OpenStreetMap
with the following reasoning:
note=unless the relation base building is defined as height 0 every element gets 3D rendered the same height in a relation
Could you fix it please? Users using solely the buildings data (and not interested in 3D stuff) get the wrong data this way.
Where a building has been split into parts, a building outline has still to be drawn of the whole building way and should have the tags
building:levels=*andheight=*. These values should be the maximum of all the building parts.
I also noticed some undocumented roof:shape values that seem to be used only by you, e.g. roof:shape=more_than_4_faces
Are we sure that more established tags couldn’t be used instead?
After all, most non-rectangular buildings will technically have more than 4 “faces”, yet we still use values like gabled, hipped etc. It’s generally up to the renderer to interpret and display the shape correctly.
Think to know how the countless polluted drop-down lists get build! Maybe start with that.
There’s 3000+ ‘mixed’ too… is as good as. ;o)
At least I know the way I spell it is consistent … added it to the S3D custom preset.
F4map is not the “official renderer” of OSM. Although it’s quite good most times.
Instead of experimenting, you could just dissolve the building in parts.
It doesn’t make fun to make up new shapes, if they are not supported in reality.
I would like to have an “official” pseudo-code in the wiki to get transcode to all languages for all renderers.
Where the ‘not the official renderer’ comes from, je ne sais pas’. Got something better, easier, I’ll take it.
At any rate it is crosspitched and the ‘leave it to the renderer’ solution was to omit the general roof orientation, so now got me a roof with the correct gabled shape (with some hippish notions)… all these small nooks make for computational squeezing. It’s where this effort stops, Either there is a generalized solution or an absence of a roof:shape tag. Others are welcome to give it a go.
My English is limited. So let me try to understand.
“crosspitched” is not on the “Simple” page, so I did not mind yet. The Shape page shows more, but nothing impossible. (A cone is just a pyramid with many corners)
For gabled_height_moved we need two height or angle values, possible as a list with higher;lower walue.
There is crosspitched. Your angle shaped building is crosspitched? I can’t image how it looks. Could you please add the position/OSM ID with your examples. F4 shows it gabled at the left end, and hipped at the other. Oh, that’s side-hipped. I wonder how to tag which side is what. (sometimes _ or - is a bad mix in the names)
For the “small nooks” it gets difficult. For hipped we could follow even the smallest or just keep the (4?) roof sides plane and vary the wall hight. But at what limit of smallness?
If we did have an FOSS renderer, we could discuss details. Now we just starve hypnotised on the cobra F4.
Complex shapes may be solvable by building:part s. And always by 3dmr.eu
I see an L-shaped hipped and a small flat square. If L-shape is not supported, it may be done by two hipped rectangles, partly overlaying. OSM-ID?
This is my roof shape wiki ref… 4D
https://wiki.openstreetmap.org/wiki/OSM-4D/Roof_table
There’s nothing to be seen on those 2 crosspitched buildings, both ends should show as were it gabled roofs. A shot from a different angle
Next in Bing suppressing the data layer. The right building has the pitch to the side instead of the end. Also hippish on the other end although straight gabled pitch.
The shape is not ‘simple’ thusly accept the curve ball into left field causing the aberrations. StreetGL has/had them too.
I see the crosspitched. Not the two L shapes! Each L is a bunch of 6 about square crosspitched, merged together. But some are only semi cross, just 3 ^ and one -
IF crosspitched did work, you would have to map the squares/ectangles as single buildings or parts.
To get it rendered now, I would map each of the 2 times 6 “squares” each as 2 parts of gabled, along and across at the same place.
OSM ID?
Your OSM-4D looks interesting. Later, it’s to late here.
Notice one of the authors of the 4D wiki is Kendzi, the person who also did the £D plugin for JOSM, sadly who’s plugin gone demised,
I did read 4D wiki long ago. As I am not a fan of more data in OSM, I liked 3dmr.eu or WikiMedia may be. Anyway, if you offer a renderer, your ideas may spread.
OSM editors could mask out the “disturbing” data.
Fresh off the press, the church has the documented roof shape of apse_gabled… flat as a pancake. I’ll try the removing of orientation to find out if it’s another case of ‘just leave it to itself’ to find the best fit.
I thing there no use of abse_gabled in OSM. What shall this be?
F4map could be done with a part gabled and a part pyramide.
