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; } } }

Feature-Typ Fanout?

AdamRepsher

Hallo nochmal,

Ich arbeite immer noch am zweiten ETL-Training (für ältere Versionen von Desktop) in ArcGIS Pro. Ich weiß, dass es Unterschiede gibt, aber dies sind die einzigen räumlichen Daten-ETL-Trainings, die ich kenne.

Ich arbeite mit Pro 2.6.3 und FME 2020.0.1.0 (20200407 - Build 20218 - WIN64)

Training: Controlling Data Translations Using Extract, Transform, and Load Processes | Esri Training Web Course

Letzten Endes muss ich die "Fanout"-Funktion des Writer Feature Type verwenden.

Ich habe zwei Reader Feature Types, die einen PointOnAreaOverlayer speisen, dessen Punkt-Ausgabe an einen Point Shapefile Writer Feature Type angeschlossen ist. Das erste Problem war herauszufinden, wie man die magische Verbindung aus dem Training zwischen allen angesammelten Attributen im PointOnAreaOverlayer und dem Writer dupliziert. Ich folgte den Anweisungen, aber nachdem ich "Copy Attributes from Transformer" verwendet hatte, hatte das "Name"-Attribut im Writer einen roten Knoten und erhielt beim Ausführen keine Daten vom Overlayer. ("NAME" ist das Feld in einer Polygon-Ebene, das in der Punkt-Ausgabe erfasst werden muss.) Ich fand die Attribut-Akkumulation des Overlayers - Merge Attributes und stellte den Akkumulationsmodus auf "Merge Incoming" ein. Das ermöglichte es dem Overlayer, das Polygon-Attribut "NAME" in der Punkt-Attribut-Ausgabeliste anzuzeigen und für den Punkt-Writer sichtbar zu machen. In früheren Versionen von FME musste dies nicht gemacht werden? Oder hat mehr Funktionalität zusätzliche Konfigurationsebenen erzwungen?

Nun zum eigentlichen Teil der Frage...

Ich muss einen "Feature type fanout" durchführen. Hier ist das Trainingsbild des einfachen Kontrollkästchens und Kategorieauswahl innerhalb der Writer Feature Type Eigenschaften:

Hier sind die Writer Feature Type Eigenschaften, die ich in Pro/FME sehe:

Wo ist die Feature type Fanout-Funktionalität?

Danke,

- Adam

Finde mehr Beiträge mit dem Tag

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

Nimm an der Unterhaltung teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

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