nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Fonction Fanout du type d'entité ?

AdamRepsher

Bonjour encore,<\/P>

Je travaille toujours sur la deuxième formation ETL (pour les versions plus anciennes de Desktop) dans ArcGIS Pro. Je sais qu'il y a des différences, mais ce sont les seules formations ETL sur les données spatiales que je connaisse.<\/P>

travail avec Pro 2.6.3 et FME 2020.0.1.0 (20200407 - Build 20218 - WIN64)<\/EM><\/P>Formation : Contrôler les traductions de données en utilisant les processus Extract, Transform, and Load | Cours Web Esri Training<\/A><\/P>

En fin de compte, je dois utiliser la fonction "Fanout" du Writer Feature Type. <\/P>

J'ai deux Reader Feature Types alimentant un PointOnAreaOverlayer<\/STRONG>, avec sa sortie point attachée à un Point Shapefile Writer Feature Type. Le premier problème était de comprendre comment dupliquer l'interconnexion magique de la formation entre tous les attributs accumulés listés dans le PointOnAreaOverlayer et le Writer. J'ai suivi les instructions, mais après avoir utilisé "Copy Attributes from Transformer", l'attribut "Name" dans le Writer avait un nœud rouge et ne recevait pas de données de l'Overlayer lors de l'exécution. ("NAME" est le champ dans une couche polygone qui doit être capturé dans la sortie point.) J'ai trouvé l'Accumulation d'attributs de l'Overlayer - Merge Attributes et j'ai défini le Mode d'accumulation<\/U> sur "Merge Incoming". Cela a permis à l'Overlayer d'afficher l'attribut "NAME" du polygone dans la liste des attributs de sortie du point, et d'être visible pour le Writer point. Dans les versions précédentes de FME, cela n'avait pas besoin d'être fait ? - Ou plus de fonctionnalités obligeaient des couches supplémentaires de configuration ?<\/P>Passons maintenant à la vraie partie de la question...<\/U><\/P>Je dois faire un "Feature type fanout." Voici l'image de la formation montrant la simple case à cocher et le sélecteur de catégorie dans les propriétés du Writer Feature Type :<\/P><\/span><\/P>Voici les propriétés du Writer Feature Type que je vois dans Pro\/FME :<\/P><\/span><\/P><\/P>Où se trouve la fonctionnalité Feature type Fanout ?<\/STRONG><\/P>Merci,<\/P>-_Adam<\/P>

Trouver plus de publications taguées avec

Accepted answers

bharold

Adam for the first part of your question, attribute names are case sensitive so you'll need to create an attribute connection from NAME in your data to Name on the writer. This is easy manually but if you had dozens to do there is also an automated way.

You have found the feature type fanout, it is 'Fanout by Attribute' in the old UI. Here is a good topic for the current experience:

https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_Workbench/Workbench/Setting_Feature_Type_Fanout_Properties.htm?Highlight=fanout

All comments

AdamRepsher

Thank you @BruceHarold . I intend to keep using Pro since it is the way forward! Just bear with all of my questions....

bharold

Adam you found the recommended way to get the area feature attributes onto the points, maybe the merge behavior default changed between releases. Please keep using Pro anyway.

AdamRepsher

Okay - I think I got the 2nd part - just use an attribute value in the Shapefile Name parameter. THANK YOU @BruceHarold !!! That makes it incredibly easy. 👍

Back to the first part of the problem. I am aware of the case sensitivity, but didn't document that well in my question. The correct case in the field (all caps) is carried over from the Readers to the Transformer and also to the Writer when connecting them. Here is my view after following the steps in the training to connect everything (Yes, this is still me working in Pro - not as the training is done in Desktop v10.5):

My connections before "Copy Attributes from Transformer"

This is what the training says to do next:

Instructions from Training

...and their example of what it is to look like when done:

Training after instruction

BUT - The following is what I get after I complete the step of "Copy Attributes from Transformer":

My Result

So, I get the attribute carried over from the Area section of the Transformer to the writer. I think I am seeing the lack of connection of the NAME attribute because the desired action of the "Overlayer" (actually incorporating the Area's NAME into the point data) is not happening automatically, as it must have done in previous versions of Desktop/FML?

I then did a bit of hunting for an answer. Tell me if I found the right/best method to accomplish what I'm trying to do...

Found in the PointOnAreaOverlayer Parameters - the "Attribute Accumulation" section and "Merge Attributes" which I set:

Although I do not need the Point attributes added to the Area data - I DO now have the Area data's "NAME" attribute in the Point data - AND I am able to make the connection to the "NAME" attribute in the writer:

...and then make the connections...

I'm wondering if:

This is the best/most efficient way to accomplish this?
If the older versions of software just assumed that you wanted this to happen, and made it work that way automatically? (Because the Overlay tool in Modeler did do that.)

bharold

You have found the feature type fanout, it is 'Fanout by Attribute' in the old UI. Here is a good topic for the current experience:

https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_Workbench/Workbench/Setting_Feature_Type_Fanout_Properties.htm?Highlight=fanout

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.