When trying to load the dataset with the default import settings, only BP_Plan:id is loaded - the existence of one (for hale unexpected) attribute should not keep it from loading the others.
Additional information.
When using the 'Read types and properties where the namespace does not match the schema' functionality at data import, all properties are loaded as expected.
When removing the gml:name attribute from the dataset, the data is loading as expected (also without using the functionality mentioned above.
An example dataset to reproduce the behavior is linked in WGS-455.
When trying to load an XPlanung GML containing an object with
The reason for that is the occurrence of the gml:name attribute. There are two issues involved:
Additional information.
An example dataset to reproduce the behavior is linked in WGS-455.