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
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.
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.
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.
I exporter is fixed in v231. You can try convert output to x using blender.
I saw discussion about hipped roof:
Both roofs you can test in kendzi3d:
First example can be tag with roof:shape=hipped. It generate square like roof even for non square building outline. Maybe it should be named square hipped?
Second with tag roof:shape=9.0. It generate roof with const angles. For square like outline, output will be same as for hipped roof.
Roof type 9.0 need some better name but I donāt known how it should be named.
Kendzi, o-sewa ni narimasu I am your debtor.
Export to collada works, and I even can open results in Deep Exploration. I still need to do some testing, but looks i can do what i need)
ā
The first pic is rather about translation of the word hip into russian.
if you ask my opinion, it is quite simple:
what is now called hipped should be renamed to primitive_hipped or be dropped. I do not know any building to which it can be applicable.
roof:shape=9.0 should be renamed to hipped. It is realy what is needed.
It also works with simple rectangular buildings.
Both buildings on the screenshot have roof:shape=9.0, but should have roof:shape=hipped.
I think, that it is incorrect rendering. When I write building:levels=1 + roof:height=3, I want to say, that building have one level and roof with height with 3 meters, and a roof is above base of building. I think, that approximate height of building (if there is no roof:height building:height or height) should be calculated as building:levels3 + roof:height (or roof:levels3, if there is no roof:height).