I have been able to add custom properties to specific objects through automapping rules, but i can’t seem to be able to add them to the Layer output. Is this the expected behavior?

I guess that’s because the automapping system uses several custom properties of its own for configuration purposes. It could be changed such that any unrecognized custom properties on the output layers are just copied over.

So how should it behave? Ignore custom properties on input layers if they don’t match any existing one? Or only match input layers if they have the same unknown custom property values as the workmap? And copy custom property values to output layers?

[image] Galdred: Ignore custom properties on input layers if they don’t match any existing one? Or only match input layers if they have the same unknown custom property values as the workmap? Hmm, the second option is an interesting alternative. You have much more extensive experience with t…

I did some cleanups to the automapping code today: 076382c AutoMapper: Fixed object groups always getting added a2fd1aa AutoMapper: Simplified some code a6dc53d AutoMapper: More code cleanups Some observations: There seems to be no custom properties being read for layers at all. The system …

That makes sense to me. I don’t think it is worth bothering with custom properties at the input level then. I don’t have a strong opinion about point 2.

You guys probably know the inner workings of the tool much better than i do, but what i was thinking is that it would be nice to add custom properties on the output layers of the rules. Not necessarily copying them from the input layers, but for my use case i believe that could work too. I’m not su…

@TitoOliveira I never suggested to copy properties from the input layers. I tried to explain the possible confusion that may result if users try to rely on copying of properties from output layers.

I see, got it. I think the behavior that you marked me would be fine. I can see that it requires the user to be better aware of the custom properties he defines across multiple rulesets. But even so it’s a better workflow than having to manually place them after the automapping, imo. And it also w…

[image] TitoOliveira: I can see that it requires the user to be better aware of the custom properties he defines across multiple rulesets. But even so it’s a better workflow than having to manually place them after the automapping, imo. And it also won’t affect anyone who’s not using them, righ…

Automapping rules doesn't support adding custom properties to the Layers?

Questions

bjorn (Thorbjørn Lindeijer) April 3, 2017, 7:21am 4

Hmm, the second option is an interesting alternative. You have much more extensive experience with the automapping system than I do, so maybe you can decide?

Yes, I think that’s a sensible thing to do.

Development Updates

Topic		Replies	Views
Trying to understand / solve an issue with automapping. Hope someone can help Questions	3	1528	December 31, 2017
Automapping, possible to use output layer from rule to another rule? Questions	1	789	January 1, 2018
Automap rules that apply to multiple layers? Questions	1	456	June 12, 2021
Match multiple layers with Automapping Questions	6	223	January 21, 2025
Automap rules : input multiple layers Questions	17	5295	April 7, 2017

Automapping rules doesn't support adding custom properties to the Layers?

Related topics