Tutorial Help! about 3dcitydb HOT 18 CLOSED

The exported KML can be 2D if you select the "Footprint" display form. But interestingly, the exported CityGML should never be 2D, since the CityGML-Exporter does not do any 3D -> 2D projection.

Could you share your 3D CityGML file converted from IFC? It would help us to reproduce and solve the issue.

PS: The tutorial here (https://github.com/3dcitydb/tutorials) is a good leaning material for getting startet with 3DCityDB.

from 3dcitydb.

Hi,
really thank you for the help. I practiced with the tutorial, but once i used my case study, I ran into problems.
At the wetransfer link --> https://we.tl/t-PvKZH6POO1 you can download all my files:
-IFC
-FME WORKBENCH
-Citygml as FME OUTPUT
-Citygml as 3DcityDB Output.
-KML after FME
-KML after 3dcitydb

Ps: my case study is only a single building because I'm also having difficulty understanding how to enrich the database, not being present in the tutorial.

Thanks

from 3dcitydb.

Many thanks for sharing the datasets! I've also reproduced the problem. The triangulated surface geometries in the CityGML data from FME are not completely imported into the database. Consequenlty, the exported KML and CityGML data are not correct.
We'll look into the problem and try to solve it as soon as possible.

from 3dcitydb.

THANK YOU,
I AM WAITING FOR YOUR USEFUL HELP.

from 3dcitydb.

@yaozhihang
I found another issue. I can't publish my SPSHG on Google Fusion Tables reported in exercise 5 because Fusion Tables API have been discontinued. they suggest finding alternatives such as BigQuery, Cloud SQL, Maps Platform, and Data Studio. Do you have any suggestions for me? I don't know which one can I use and how.Thank you

from 3dcitydb.

There are already two alternatives (Google Sheets and PostgreSQL database with a RESTful API). You may get more details from this website: https://github.com/3dcitydb/3dcitydb-web-map/releases

from 3dcitydb.

Hello @yaozhihang!
I am also encountering some difficulties in setting up the connection between my PostgreSQL database (containing the cityGML model) and the web-map client.
The postgREST API interface seems not to respond to the query when I select a building. I believe I am doing something wrong and I would greatly appreciate your help to find out what it is.

Following the advice of Prof. Kolbe I created the following view "all_building_attribute":

Then, following postgREST tutorial I created the roles and the usage privileges:

The .conf file to start the connection works fine:

But when I try to see the "all_building_attributes" view, it seems the table does not exist:

Therefore also when I paste the URL in the "Thematic data URL" field in the web-map client, it does not display the data.

Can you help me with this?
Thank you for your time

from 3dcitydb.

Ciao @matteomandrile
mi sembri leggermente più avanti di me. Posso chiederti se il tuo citygml viene da un file IFC? Ho utilizzato FME per la conversione, secondo quanto riportato nella community, ma qualcosa non sta funzionando come dovrebbe.

from 3dcitydb.

Ciao @GiuliaSpi
no, ho costruito il modello partendo da dati GIS (shapefile, e csv) e database spaziali. Dovrò però fare presto una conversione da IFC a CityGML portandomi dietro dati riguardanti le performance energetiche. Purtroppo no saprei aiutarti a riguardo, non ho ancora toccato l'argomento.
Invece, riguardo il plug-in Spreadsheet Generator sono riuscito a usare Google Sheet.

1. segui il tutorial per la creazione del template, esportazione e condivisione aperta (pubblica) dello spreadsheet.
   

2. Come accennato da @yaozhihang, nelle note per la release del 3dcitydb-web-map che trovi qui è spiegato come "leggere" i dati nella tabella Google Sheet attraverso il web-map client. Non è triviale, ma seguendo i passi che ti riporto sotto dovresti riuscire, investendo un po di tempo nel capire il meccanismo OAuth.

It is now possible to access own private/non-public Google Spreadsheets using OAuth. The following steps explain how to enable OAuth for your project and use it in the Web Client (this is not the requirement of the web client, but rather a standard procedure when using OAuth):

Make sure you really have read/write access to the table;
Register your project using Google Developer Console;
Search and activate Google Sheets API for your project;
Create and copy your client ID from the credentials page;
Insert the trusted redirect URIs,
or the URIs in which the web client is running. For example if you are using the latest web client from our 3DCityDB server,
then you should insert the following URI:
https://www.3dcitydb.org/3dcitydb-web-map/latest/3dwebclient/index.html
Paste your client ID in the web client's URL using the parameter googleClientId, such as
https://www.3dcitydb.org/3dcitydb-web-map/latest/3dwebclient/index.html?googleClientId=<YOUR_CLIENT_ID>
You can then log into Google by clicking the button marked with a key symbol, which can be found in the top right area of the screen;
When logged in, you can click the button again to log out;
If the parameter googleClientId does not exist in the client URL, then this button shall not be displayed (backward compatible to earlier versions of the web client).

Spero sia d'aiuto!

from 3dcitydb.

Ciao @matteomandrile, ti ringrazio.
Avevo già tentato di seguire le indicazioni riportate da yaozhihang ma alla fine non sono riuscita ad installare la parte di Google Sheet. Riproverò anche con l'aiuto delle tue indicazioni.
In ogni caso "una conversione da IFC a CityGML con dati riguardanti le performance energetiche" è esattamente quello che sto investigando anche io. Per farlo ho usato FME ed ho creato un workbench di conversione. Come ho descritto a yaozhihang trasferendo il citygml apparentemente corretto dopo la conversione su 3dcitydb, una volta riesportato perde le sue informazioni 3d.
@yaozhihang hypothesis is "The triangulated surface geometries in the CityGML data from FME are not completely imported into the database. Consequently, the exported KML and CityGML data are not correct.
We'll look into the problem and try to solve it as soon as possible."

So now, I'm waiting for his suggestion, in the meantime, if you are interested I can send you the FME workbench, and maybe we can continue to discuss it, wanting to achieve the same goal

For now, I'll try again to use Google Sheet.

Thanks

from 3dcitydb.

@GiuliaSpi, thanks for reporting the bug with importing your dataset. The current CityGML import assumes a gml:CompositeSurface as shell of a solid but your dataset uses a gml:TriangulatedSurface. Though being very uncommon, using a gml:TriangulatedSurface is technically allowed. A fix is proposed here 3dcitydb/importer-exporter#130. You can test the fix by building a new version of the Importer/Exporter following this guide.

Some more general guidelines:

• Pick the appropriate issue tracker. For instance, your bug of the Importer/Exporter tool should be reported in the Importer/Exporter issue tracker rather than here.
• Create one issue per bug or feature request instead of discussing multiple topics in one issue. You can link issues if you think they are related to each other.
• Stick to English language so that others can follow and benefit from the discussions.

from 3dcitydb.

I've really appreciated your suggestions. Thank you.

from 3dcitydb.

Hello @clausnagel,
Thank you for your fix and suggestion. I will post my previous question in the 3dcitydb-web-map client issue tracker!

from 3dcitydb.

Thanks @GiuliaSpi and @matteomandrile, much appreciated. We will look into your further issues.

from 3dcitydb.

Fixed missing import of TriangulatedSurface with 3dcitydb/importer-exporter#130. The fix will be part of the next release of the Importer/Exporter.

from 3dcitydb.

Hello @clausnagel ,

I built a new version of the Importer/Exporter and it is still throwing errors:

I am trying to import a building created by converting an IFC to CityGML, following the same tutorial as @GiuliaSpi, therefore I am also generating triangulated Surfaces:

However if I search in the file the complete XLink reference that is generating the error, it appears that it refers to
<app:target>#fme-gen-9e016599-d8c6-4e4c-b097-13892c78010a_16301</app:target>

In the DB, the building appears to be correctly imported:

But the Export file (17 MB) does not show any geometry in FZK

I attach the "imported" file generated from the IFC->CityGML conversion (FME) and the "exported" file from the imp/exp Tool.
test.zip

Do you have an idea why this is happening?

from 3dcitydb.

The errors messages are correct because, as the log messages say, your file contains a lot of references that cannot be resolved.

An <app:target> must reference an existing surface geometry object. Take your example <app:target>#fme-gen-9e016599-d8c6-4e4c-b097-13892c78010a_16301</app:target>. There is no surface geometry with gml:id fme-gen-9e016599-d8c6-4e4c-b097-13892c78010a_16301 in your file. So the <app:target> property points to nowhere and cannot be resolved. Hence the error message. This needs to be fixed in your import dataset.

I also have no issues with visualizing your Bellevue_LOD2City_export.gml export dataset with the FZKViewer. I tested with both version 5.3.1 and 6.0 of the software.

from 3dcitydb.

Thank you for your explanation, I have resolved the issue by changing the CityGML Geometry Setter parameter City GML Lod Name from lod2Solidto lod2MultySurface.

from 3dcitydb.