Closed synpc closed 5 years ago
I assume this is is glTF 2.0 right? Make sure you check the Generate surface normals
in the Preferences
-> KML/COLLADA/glTF Export
-> Rendering
-> Building
in the Importer/Exporter.
hi apprec prompt :)
yes, is gltf 2.0; further clarification pls: am exporting textured model (db imported with imaged textures), hence unchecked this preference - will this make difference?
sample exported folder with image
thnx again
Please first try to enable the surface normals (see picture) and check if the problem has been solved:
hi thanks for prompt; unfortunately, exporting collada with surface normals does not render textures as required
pref:
geometry only:
collada with surface:
apprec pointers to how to get textured display in webclient, similar to google earth:
TIA
hi
have experimented with the following combinations preferences and params, with the results in the web client as indicated
apprec any hlp pls thx
Could you provide us an excerpt of your dataset for testing?
hi dataset used is classified; trying to replicate problem using RTG_Schulungskurs_2016; noticed that the texture images therein is of file extension jpg, while my classified dataset is using tif - can this be the problem? does webclient accept such files, or must be in jpg? thnx again
hi converted tif image to jpg; import to fresh database export with generated surface normal and texture CAN now view textured facade in webclient will close issue thnx again
Hi, yes this is very likely the problem. I would suggest to convert the .tif texture images to .jpg and to replace them in your dataset. For the conversion there are a couple of Open Source tools that can convert.a folder of .tif files into .jpg. Finally, the CityGML file(s) need to be updated. One possibility would be to do this directly in the 3DCityDB and update all tuples in the respective table (I don‘t know the table name, but should be easily identifiable from the documentation). Another option would be to send the CityGML files through some line processor tool like „awk“ and to then search for strings like .tif“ and to replace them with .jpg“ (I have included a quotation mark to reduce the risk that some other string which might accidentially include .tif would be replaced.
If you know how to do shell programming you could also try to replace the collada2gltf binary software by a shell script with the same name, which then first checks if the input image is of type .tif and in this case calls an image conversion tool first and then feeds the generated jpg file to the original collada2gltf binary software tool.
Best regards Thomas Kolbe
Prof. Dr. Thomas H. Kolbe Chair of Geoinformatics Institute for Geodesy, Geoinformatics, and Land Management Technische Universität München Arcisstr. 21 81375 München, Germany Tel. +49 89 28923888
Am 27.03.2019 um 07:38 schrieb synpc notifications@github.com:
hi converted tif image to jpg; import to fresh database export with generated surface normal and texture CAN now view textured facade in webclient will close issue thnx again
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
hi thnx for suggestions; yes, did not prevly report this step, but i did have to manually find all the references in the raw gml pointing to the tif and change to jpg then import into database i suppose this is a learning point: documentation did not explicitly specify acceptable image format thx/rgds
hi exported using 3dcitydb importer-exporter successfully(?); kml renders correctly in google earth pro - building textures display correctly; collada glTF exports - files seem to be exported correctly (during export process, dialog popup indicates texture images being exported), however, in web client, only geometry export displays (wireframes) when added as layer; when export collada with texture, buildings display as blacked-out boxes; apprec any pointers TIA synpc
export:
google earth:
webclient collada: