dd-bim / City2BIM

Library for Geo data in BIM integration, plug-in for Revit
GNU General Public License v3.0
50 stars 12 forks source link

CityGML import - parameter fieldName is not acceptable #49

Closed Moschi87 closed 2 years ago

Moschi87 commented 2 years ago

We got new workstations and installed City2BIM for Revit 2021. Every time we try to import a CityGML file we get the following error message:

Revit_exception_fieldName_not_acceptable

Can someone check if this is a bug? We can reproduce the exception on multiple workstations (Windows 10 and Windows 11 with latest updates). (The installations on our old workstations worked well and without any problems)

Hutsimbl commented 2 years ago

Hi,

Moschi87 commented 2 years ago

Thank you for the fast answer.

It happens with all GML files. Since we are from Saxony too we often have to deal with the CityGML data from Saxony: https://www.geodaten.sachsen.de/downloadbereich-digitale-3d-stadtmodelle-4875.html

No need to use a special file for testing. There are no ä, ö or ü in the filenames. I can also confirm the error with the same files which worked before on the old workstation. Maybe your Addin needs some older package of .NET or something like this? But to me the error sounds like Revit API itself is unhappy with some names.

I will drop you an email tomorrow if you want to call me for further information.

UPDATE: I just tried other CityGML data, this time from Berlin. I had a successful import! https://www.businesslocationcenter.de/berlin3d-downloadportal/#/export

Maybe you can check with the data from Saxony (link above)?

Hutsimbl commented 2 years ago

I can confirm the issue with the fieldnames.

CityGML files from saxony contain 2 attributes with hyphens. It seems, this character is not allowed in field names for the extensible storages in Revit.

If I change the attribute names in the CityGML file from

the import works.

Maybe you can use this as a quick workaround?

Moschi87 commented 2 years ago

Thanks for your help. I was able to use your workaround successfully :)

Very strange behavior: Todas I was able (only once) to import the original file without error directly after importing some "good" GMLs like from Berlin. Maybe you can add a "search and replace" in the processing before you feed in the field name?

Hutsimbl commented 2 years ago

hopefully resolved with #50 and #51 new release uploaded