Doesn’t kendzi (or f4 map) support building parts as lines? I’ve got a building with a glass front (not over the complete height). So I drawed a line on this building site, and set building:part and materiel=glass but this didn’t work. On kendzi plugin the building was completely gone.
Afaik that’s exactly what I would expect: “building:part”=* as a non-closed way is not defined and if there’s a “building:part”=* within (since it’s not defined I’d say it is not wrong to interpret it as “within”, but in this case that’s what you want anyway) the Buildings outline the latter should be ignored (aka “be completely gone”).
You should think about current SB3D buildings as of solids. You can change in kendzi3d material of one of walls by tagging building as multipolygon and as member you need to add all it’s walls. One of them you can tag with different building:material tag.
Ok, i’ve done now. but i doesn’t work.
I’ve got a line with building:material=glass. Another line for the rest of the building with building:facade:colour=#XXXXXX. Both are part of a relation. type=multipolygon. the lines have role=outer.
where do i tag the height and min_height? at the keys for the multi polygon? i did, but i don’t see the wall i’ve tagged.
Here is an example:
http://www.openstreetmap.org.pl/kendzi/Kendzi3d/examples/multipolygon%20glass%20wall.osm
Tags height and min_height should be put on multipolygon it self
Result:
Hi, one more enhancement request for Kendzi)
Is it possible to support color names, from this list:
https://github.com/One-com/one-color/blob/master/lib/color-namedColors.js
For example, firebrick is quite popular colour already.
done in v217
kendzi,
-
There is link to message here and link to osm-file with examples is broken there.
-
About deactivation of volume rendering of building outlines - I want to add, that joining to relation type=building is not the only simple method to recognize building, which has dividing to parts. Another variant is detecting a tag building:parts= . On the one hand, if you don’t want, of course, you can not add this tag, but, on the other hand, you can use this tag right now in that buildings, which already have it (more that 1.000 buildings have this tag at this moment).
Could you, please, deactivate volume rendering of buildings (building= ), which also have tag building:parts= ?
Great! Thanks!
kendzi, could you please check out this building. When in Josm the plugin doesn’t render it untill you remove roof:material tags or ** roof:colour** tags. Can’t figure out what’s wrong with it.
Added it in v220. If there is building:parts=* tag and there is no tag building:part=* building will not be rendered.
However i think all parts should be put to relation too.
Bug fixed in v222. But i think it should be used tag steel not stal
You are right, of course. Thanks.
Thank you! Of course, these things are not mutually exclusive.
–
As I see, this building:part is not rendered because of building:part=dormitory. I think, plugin should work with all building:part= (if we can use building=commercial and building=dormitory, we should also have possibility to use building:part=commercial and building:part=dormitory, if they are parts of building=yes.
There is also a case when building:part=no. Please consider it also 
Tags building:part=no and building:parts=* were added in v224.
I don’t see rendered building:part=yes (without building=yes) in v224, only building=yes (without building:parts=) and building=yes + building:part=yes (without building:parts) are rendered.
Check in v226, if it isn’t working please send example.
Hi kendzi,
There is menu item in the plug-in “3d->Adv->Export models to files”. Does it work? I only get message about unexpected error…
Is it possible to support *.x file format as export format?
http://en.wikipedia.org/wiki/.x
http://msdn.microsoft.com/en-us/library/windows/desktop/bb172982(v=vs.85).aspx
I need models in x format because, because models in this format are required for the CityGuide. CityGuide is navigation program with support of OSM-maps, it is capable of 3d rendering, but it requires models in this format.
I am now searching for a way to obtain models from OSM, at least for the most notable buildings.
This option should work. It provide very basic support for exporting models to collada file. Output location is hard-coded to C:\out\export.0.dae /multiText/out.dae. Output directory have to exist before you start export.
If it is not working please send me an exception.
The bigest problem with exporting models from application is that I’m using multi-layer-textures for windows or colored walls. Unfortunately I didn’t find any universal 3d model format which support it. It is theoretically possible to do with collada, but non of viewer I test is supporting it. X3D file have support for multi-layer-textures but it don’t work with blender or few viewer I test. The most popular 3d file format like OBJ don’t support multi-layer-textures at all.
I check X-file format, it seam like some binary blob from Microsoft DirectX, I don’t plan to add exporter for it, but it should be possible to convert it from collada to X.
So if you have any idea witch file format could be used, please write.
Documentation on MSDN is very unfrendly. There is several variants of format, both binary and text - http://msdn.microsoft.com/en-us/library/bb173014.aspx
Check also these page with examples of it:
http://paulbourke.net/dataformats/directx/
http://ru.wikipedia.org/wiki/X_(%D1%84%D0%BE%D1%80%D0%BC%D0%B0%D1%82_%D1%84%D0%B0%D0%B9%D0%BB%D0%BE%D0%B2) (in russian)