Skip to main content
Solved

Citygml LoD2 from shapefile with floor, wall and roof features

  • November 22, 2016
  • 8 replies
  • 115 views
J

Hi all,

I'm trying to create a workflow for creating LoD2 CityGML from a shapefile of building footprints (and forcing a height attribute) and I am struggling with few issues. I would like to have the buildings composed of wall, roof and floor surfaces but I haven't been able to work out how to compose the surfaces within a single building while also generating the relevant semantic feature types for these surfaces. I'm aiming for something similar to what I want is the LoD2 sample in CityGML 2.0 examples: http://schemas.opengis.net/citygml/examples/2.0/building/Building_LOD2-EPSG25832.gmlSo far, I am simply offsetting a the shapefile to create floor and roof geometries. I also generate a UUID for an gml_id (for the Building) which I thought I could reference from the roof and floor surfaces LoD2 features in order to nest them. However, upon running the workspace, it appears only the Building feature is written out and the RoofSurface and FloorSurface features are ignored.

Can anyone identify what I should be doing? Or point me to a relevant workspace for this? All the workspaces I have found in the forum are either for simple LoD 1 buildings (no roof/ wall semantics) or start from IFC.

 

I have attached my workspace. Thanks

Best answer by juanchuchow

Hi Julian,

The gml_parent_id for the RoofSurface and FloorSurface need to point back to the gml_id of the Building, e.g.,

Buildling -> gml_id : "id-building-1", then

RoofSurface -> gml_parent_id : "id-building-1", and

FloorSurface -> gml_parent_id : ""id-building-1".

Regards,

Juan

View original
1 Attachments
Did this help you find an answer to your question?

8 replies

juanchuchow
Safer
Forum|alt.badge.img+1
  • juanchuchowSafer
  • Safer
  • Best Answer
  • November 22, 2016

Hi Julian,

The gml_parent_id for the RoofSurface and FloorSurface need to point back to the gml_id of the Building, e.g.,

Buildling -> gml_id : "id-building-1", then

RoofSurface -> gml_parent_id : "id-building-1", and

FloorSurface -> gml_parent_id : ""id-building-1".

Regards,

Juan

juanchuchow
Safer
Forum|alt.badge.img+1
  • juanchuchowSafer
  • Safer
  • November 22, 2016
juanchuchow wrote:

Hi Julian,

The gml_parent_id for the RoofSurface and FloorSurface need to point back to the gml_id of the Building, e.g.,

Buildling -> gml_id : "id-building-1", then

RoofSurface -> gml_parent_id : "id-building-1", and

FloorSurface -> gml_parent_id : ""id-building-1".

Regards,

Juan

Also make sure that the gml_id for the Building, RoofSurface and FloorSurface are unique, I don't think you'll need to set them for the child RoofSurface and FloorSurface, the CityGML writer may auto generate the gml_id, but you do need it for the Building as it's need to be referenced by the gml_parent_id

 

 

J
  • julian_
  • Author
  • November 23, 2016

Thank you. Yes, I had not been assigning the gml_parent_id correctly. I had been creating a new attribute called gml_parent_id and then assigning that the gml_id. However, instead I needed to use AttributeRenamer transformer to rename the gml_id to gml_parent_id in the child roof / floor / wall surfaces workflows.

 

N
julian_ wrote:

Thank you. Yes, I had not been assigning the gml_parent_id correctly. I had been creating a new attribute called gml_parent_id and then assigning that the gml_id. However, instead I needed to use AttributeRenamer transformer to rename the gml_id to gml_parent_id in the child roof / floor / wall surfaces workflows.

 

Can you give me fixed file? thanks

 

 

A
Forum|alt.badge.img

Hi Julian!

I am having the same problems you got when building a working FME workbench for the CityGML format. It is taking me a loong time to get this working.. Is that possible for you to share the one you built? Here is my email abel.gonzalez.c"at"gmail.com

Thanks in advance!

Abel

A
  • ajgzzc
  • July 25, 2017

I am quite new to FME.

How can I generate CityGML file with number of storey attribute values from shp file?

Could you share the .fmw file?

Thanks!

fmelizard
Contributor
Forum|alt.badge.img+17
  • fmelizardContributor
  • Contributor
  • July 25, 2017
ajgzzc wrote:

I am quite new to FME.

How can I generate CityGML file with number of storey attribute values from shp file?

Could you share the .fmw file?

Thanks!

Hi @ajgzzc. Have you taken a look at the workspace included in the question, as well as the response from juanchuchow1323?

 

If you have further questions, I would suggest posting your question as a new question as you will likely get more responses this way. Including the following details in the new question will help the FME community help you. Please provide details including:

 

  • The version of FME you are using, including build number and edition
  • A small sample of your data, or screenshots of the data in the FME Data Inspector
  • A description of your expected output, with screenshots if possible
  • Your FME workspace
  • Your FME translation log file
  • Any other information that may be useful to share
As you are new to FME, I would suggest you review some FME Tutorials.

 

Kind regards,

 

Natalie
D
julian_ wrote:

Thank you. Yes, I had not been assigning the gml_parent_id correctly. I had been creating a new attribute called gml_parent_id and then assigning that the gml_id. However, instead I needed to use AttributeRenamer transformer to rename the gml_id to gml_parent_id in the child roof / floor / wall surfaces workflows.

 

Please share me the fixed .fmw at

Thanks in advance!

Reply


Most helpful members this week

Community Stats

30,846
Posts
116,934
Replies
38,667
Members
Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.