Itās a tpyo, you meant building:facade:material, right?
How about building:facade:color and building:roof:color with maybe 16 predefined colors red, blackā¦and if it begins with # then use it as Hex code value?
Thanks a lotā¦I will keep you updated. The first results look pretty impressive
I played a bit with the dormer rowsā¦Looks promising. I have seen that pitched roof dormers were mentioned in some places in the wiki. Do you plan to support it?
I am wondering if the same as you are doing with dormer rows would be possible for windows.
Unfortunately I see only 2.0 roofs when looking around, maybe I will try a more interesting place later
ā¦but I will not upload the building:facade:material=plaster, it is not the reality but good for presentation.
For now only dormers type āaā and ā-ā are supported. I plan to support some more types in near future. I think that we can add roof window (skylight) as new type of dormer?
By plaster material I mean: http://en.wikipedia.org/wiki/Plaster
Yes I know that texture shouldnāt contain windows. But there isnāt any schema for tagging windows for now.
It is only example. It is not live. Unfortunately I donāt have time and server to continue it. Titles can be generated by command line program which as input can use xml data and title number.
Currently example titles are generated only for Nowe Kramsko and Warsaw at zooms 17, 18. As background it is used osmapa.pl.
That doesnāt quite work for me. Loading the xml file causes an error:
javax.xml.bind.JAXBException: "kendzi.josm.kendzi3d.dto.xsd" doesnt contain ObjectFactory.class or jaxb.index
Happens as well when the plugin tries to load its built-in texture library, hence I only get placeholder textures. I tried the latest versions of Java 7 and 6 under both Windows 7 and Linux with no luck.
Is there a todo-list or a better place than github issues list? In josm trac thereās so far just one āplugin crashedā ticket for kendzi3d. If there is some better place, I could write each of the things needing attention as a separate ticket somewhere, but Iāll start with some of them here. I know this is still in the early stages and already gives nice results with very few tags only, but communication shall make me tag them franticallyā¦
Iāve been tagging facade colours, building:levels and roof shapes, and I already have identified lots of minor glitches in rendering - and inconsistent documentation on supported tags. Even the presets linked to in the other thread on this forum use roof:orientation=, but the plugin seems to respect building:roof:orientation= only. I would believe some of these āissuesā have been discussed in the 3d workshop, but thereās little documentation of the results.
Also; for a long time the osm wiki page listed the shape pitched (and still does), but itās now āgabledā at least in the plugin; is this an agreement between other osm 3d-stuff developers, that is, from the workshop?
If I model a building with several building:part=yes ways (as horizontal slices), and I also have the building=apartments way, at the moment the JOSM plugin does not recognize this and draws both the building=* way and the building:parts, with them partially covering each other. I also think that the building=* way should have the total number of floors in the building:levels=* tag, to classify the building as having that number of floors. Currently, it just changes how much of the building gets this overlapping walls problem. So will the plugin eventually supress the building=* way automatically, or if it is tagged with building:parts=horizontal?
Where a building has one wall with a different colour, how should it be modelled (as in how it might be eventually supported)? Just an extra way with plain building:facade:color=#fffff? Doesnāt work yet. Another common case Iāve come across is that the longer walls are one colour and the āendsā of a building are of another colour?
Hello Alv,
i would say - lets write tickets together on the separate wiki subpage. I hope we can find helpers for this tool. LetĀ“s comunicate together- if possible in german language.
The specification (roof table) from the wiki page is still incomplete because i have not enough time for finishing the description of all that 3D aspects like texturing+ multitexturing specification, street area in 3d, OSM4D specification for the developers etc.etc.
What I would suggest is the detailed specification of user interface and description of wishful functions for the new version of the Plug In.
What do You think about? Best regards,
Marek
It was problem with classloader. It was solved in v88
āOfficialā todo and issues list is on github, but you can write proposal wherever you like I will try to answer.
Most of agreements from workshop is write here [1] .
On 3d workshop we agree for using roof:orientation (fixed in v100)
We agree to use name gabled but both should work in plugin. But for me pitched roof have only one surface like this [2]
From the meeting. All parts and outlines from single building should be added to relation type=building . This allow to render building outline or building parts if they exist. So one of both will be rendered outlines or parts. But this hasnāt been implemented yet. Read [3] and [4]
We didnāt discuss on this. So it isnāt implemented. But probably in future it will be done by splitting building outline (or part) to single walls and connecting them together using relation.
I have solution for walls with different colors and textures but please, wait a few days and I specify this in the wiki.
And Alv - thank You for all sugestions, comments, and angagement. Please help to make it better: Kendzi do really great job, but it is really lot to do. Support is helpful, ideas are helpful.
Best regards,
Marek
