Real time 3D map using WebGL

It was proposed to add nodes with tags roof:direction=begin|end or some relation with roles
roof:direction:begin and roof:direction:end

Wouldn’t it be possible (and in most cases even easier) to calculate this from N/NE/E/SE/S/SW/W/NW-Values?

In case there’s a communication problem: The question was, if a ball was placed on the center of a building with “roof:shape”=skillion direction=N and it’s Way-Segments pointing to 10°/100°/190°/280°, would it roll to 10° or to 0°?

Right, that was my question. I think it would roll to 0°. Because this is set with the direction tag.

But the point is, maybe there are some roofs, where the roof direction goes not to one wall. But this are very few roofs, for sure.
But very often a building is not exactly to 0°,90°…, and the roof has its lowest side at one wall. So there has to be a tag that says ‘This roof goes down to this wall’.

It will roll to 0° in F4maps, if you want it to roll to 10° you can specify the roof:slope:direction with clockwise angle in degree from north. My algorithm doesn’t try to snap on edge direction (i’m not sure but i think kendzi3D use a snap method).

I suggest to use N/NE/…-Values for an approximate direction, which should be used to calculate something to fit to the rest of the object and numerical values (in degree clockwise relative to north) for an exact direction which should be used without additional calculations.

wiki-F4:

I think, that getting information about material (and, consequently, about colour) of roof from tags building:material or material is incorrect:
wiki:

I see, that, for example, building:colour=floralwhite + building:material=brick is rendered by F4 as building with floralwhite facade and firebrick roof. It is a mistake! Information about material and colour of roof can be got only from tags roof:material and roof:colour, because building:material and building:colour show material and colour only of facade.

  1. Do you support tag roof:direction (as a tag roof:slope:direction)? They said me, that now it is better to use roof:direction instead of roof:slope:direction.

  2. Could you explain, why this building is not rendered?


    building=apartments + building:parts=horizontal + building:levels=9: building:part=yes + building:levels=1, building:part=yes + building:levels=3 + building:min_level=1, building:part=yes + building:levels=5 + building:min_level=3, building:part=yes + building:levels=7 + building:min_level=5, building:part=yes + building:levels=8 + building:min_level=7, building:part=yes + building:levels=9 + building:min_level=7.

  3. I noticed, that map shows name:en instead of name (if name:en exists). Could you, please, transfer this feature to separate option, which can be switched on and off by user? In many cases people want to see name, but not name:en.

roof:ridge=yes is used 5.000 times :slight_smile:

Dinamik

  1. the osm spec has changed, when i did the material/colour code the spec was :
    “building:facace:colour/material” specify wall colour/material.
    “roof:colour/material” specify roof colour/material.
    “building:material” cover the entire building (it was explained as a shortcut for wall+roof tags).

[Edit: building:material & material tags won’t be used anymore for roof on next release]

  1. no, we don’t support tag roof:direction but i could do it in the futur

  2. i need my database request expert to understand what happened to this building, it looks like something filters it from my buildings request.

[Edit: during import, multipolygon lines order makes a self-intersecting polygon so that it is not rendered, we’re fixing it and it should be ok on the map on next release]

  1. this could be discussed, we already talk a lot about that within the team, we plan to use the browser language to choose the best matching name to display.

chris66

Our database relation import does not allow us to handle these tag for now.

+1

N/NE/…-Values for snap on a line near to this direction, and 0-360° for exact directions is a tagging that I would prefer.

We just released a beta version of our ground elevation processing (use the big green button on the top right to enable it).

We’re already aware that many glitch are still present, we’re working hard to try to fix it.

Could you, please, give a link to place, where it is possible to see the result of this ground elevation processing?

We get elevation data for the entire world, you can see it everywhere check on some hilly spots like The French Alps.

Interesting, but height for the buildings on slopes has become ambigous:
http://map.f4-group.com/#elevations.enabled=true&lat=56.3298368&lon=43.9981801&zoom=19&camera.theta=66.535&camera.phi=-168.632

Looks that some change in tagging scheme will be necessary.

We know that buildings are not so close to reality anymore when built on a sloppy spot.

For now buildings:parts are not aligned anymore with their “brothers”, we’re working on a fix to get every parts of a building inheriting from their outline building position.

A little buggy, but looking awesome!

That’s still some kind of “beta version” we got lot of work in progress stuff waiting to be released…

Looks interesting :slight_smile:
Sadly the SRTM is in to low resolution at least for my part of the world, so it looks more odd and a lot of details are missed :confused:
So there is still a need of getting a crowdsourced alternative, like http://www.opendem.info

As you started this thread with the intention to get feedback/interaction with the rest of the (3D) OSM community:
Personally, I would really like to please you, to work first on a maximum compatibility with other viewers esp. on the S3DB schema!
Even your visual progress is impressive (and as coder I understand, thats more interesting to work on bleeding edge features), it’s getting really worse for the whole community, if we get different ‘flavours’ of micromapping and everybody has a slightly different interpretation of our tags. If we (the 3D community) want to motivate other mappers to enrich their regions, we have to offer unique tagging guides, otherwise we will get very cluttered results, that are spread all over the world :roll_eyes:

I agree, but there is the problem that S3DB is a very basic minimum consensus. The world, (and the tagging, of course) is much more complex.
So you are right: We’re at the beginning of 3D-Mapping in OSM. When I fly true the F4 map all around germany, or around the world, there are very few buildings which have 3D tags.
I think, this is good: We see, what we tag, although we are just at the beginning. So we now have the chance to see the problems, to find solutions, and create a ‘complete’ tagging scheme.
So ‘we’ have to do our work. We have to create a Wiki-Page, that is standard, that is the base for all 3D tagging and that include all 3D tags. One starting page, an this has to be the base for all renderers.
So this is the 2nd step. But when I understand the post #11 by cmif4, the base for their rendering is the S3DB scheme.

What are the problems actually, where does f4 map differ from S3DB?

I’ve found, that natural=stone at areas (outlines of big stones) are rendered as areas with many small stones. I think, that is is incorrect rendering: areas with many stones are tagged with natural=bare_rock. Natural=stone - one stone.
outline, link:

Yep, it’s Simple 3d buildings and a first step to get away from the basic LOD1 extruded buildings that we had before.
As you might know, we collect our experiences/impressions from the practical tagging with the schema here:
http://wiki.openstreetmap.org/wiki/Talk:Simple_3D_Buildings
And some started to play with other approaches e.g. to describe roofs more detailed.
So there is no reason, why this shouldn’t result in a complex 3d buildings schema :wink:

Not sure if ''complete" is a good target, as describing 3d this way will always be a compromise between comfort of mapping/tagging and the level of details that you can realise.

Here I have to disagree with you, we currently don’t lack of wiki pages
http://wiki.openstreetmap.org/wiki/3D
http://wiki.openstreetmap.org/wiki/3D_Development
http://wiki.openstreetmap.org/wiki/Micromapping
IMHO currently it makes no sense to start a list for 3D tags beside buildings, as there are currently to much differences at OSM-3D, O2W Maps, F4, Kendzi on what is how interpreted (e.g. nature, city furnitures, materials, …)

Please check the thread backwards to find some problems. Mostly it’s the way how building:parts are mixed and support of all roof types.
A visual check can be done by having a look at the already tagged areas (even with support of our community)
http://wiki.openstreetmap.org/wiki/Simple_3D_Buildings#Demo_areas