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 Type Fanout?

AdamRepsher

Hallo opnieuw,

Ik ben nog steeds bezig met de tweede ETL-training (voor oudere versies van Desktop) in ArcGIS Pro. Weet dat er verschillen zijn, maar dit zijn de enige ruimtelijke data ETL-trainingen die ik ken.

werkend met Pro 2.6.3 en FME 2020.0.1.0 (20200407 - Build 20218 - WIN64)

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

Uiteindelijk moet ik de "Fanout" functie van de Writer Feature Type gebruiken.

Ik heb twee Reader Feature Types die een PointOnAreaOverlayer voeden, met de puntuitvoer ervan gekoppeld aan een Point Shapefile Writer Feature Type. Het eerste probleem was uitvinden hoe ik de magische onderlinge verbinding uit de training tussen alle verzamelde attributen in de PointOnAreaOverlayer en de Writer kon dupliceren. Ik volgde de instructies, maar na het gebruik van "Copy Attributes from Transformer" had het "Name" attribuut in de Writer een rode node en kreeg geen data van de Overlayer bij uitvoering. ("NAME" is het veld in een polygonlaag dat moet worden vastgelegd in de puntuitvoer.) Ik vond de Attribute Accumulation - Merge Attributes van de Overlayer en stelde de Accumulation Mode in op "Merge Incoming". Dat maakte het mogelijk dat de Overlayer het polygon "NAME" attribuut liet zien in de puntattribuutuitvoerlijst, en zichtbaar was voor de punt Writer. In eerdere versies van FME hoefde dit niet te worden gedaan? - Of dwong meer functionaliteit extra configuratielagen?

Nu naar het echte deel van de vraag...

Ik moet een "Feature type fanout" doen. Hier is de trainingsafbeelding van het eenvoudige selectievakje en categoriekeuzer binnen de Writer Feature Type Properties:

Hier zijn de Writer Feature Type Properties die ik zie in Pro/FME:

Waar is de Feature type Fanout functionaliteit?

Bedankt,

- Adam

Vind meer berichten getagd met

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

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

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