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

Fanout do Tipo de Feature?

AdamRepsher

Oi novamente,

Continuo trabalhando no segundo treinamento ETL (para versões mais antigas do Desktop) no ArcGIS Pro. Sei que existem diferenças, mas esses são os únicos treinamentos ETL de dados espaciais que conheço.

trabalhando com Pro 2.6.3 e FME 2020.0.1.0 (20200407 - Build 20218 - WIN64)

Treinamento: Controlando Traduções de Dados Usando Processos de Extrair, Transformar e Carregar | Curso Web Esri Training

Em última análise, preciso usar a função "Fanout" do Writer Feature Type.

Tenho dois Reader Feature Types alimentando um PointOnAreaOverlayer, com sua saída de ponto conectada a um Point Shapefile Writer Feature Type. O primeiro problema foi descobrir como duplicar a mágica interconexão do treinamento entre todos os atributos acumulados listados no PointOnAreaOverlayer e o Writer. Segui as instruções, mas após usar "Copy Attributes from Transformer", o atributo "Name" no Writer tinha um nó vermelho e não recebia dados do Overlayer quando executado. ("NAME" é o campo em uma camada de polígono que deve ser capturado na saída do ponto.) Encontrei a Acumulação de Atributos do Overlayer - Merge Attributes e defini o Modo de Acumulação para "Merge Incoming". Isso permitiu que o Overlayer mostrasse o atributo "NAME" do polígono na lista de atributos da saída do ponto, e fosse visível para o Writer de pontos. Em versões anteriores do FME, isso não precisava ser feito? - Ou mais funcionalidades exigiam camadas adicionais de configuração?

Agora para a parte real da pergunta...

Preciso fazer um "Feature type fanout." Aqui está a imagem do treinamento da simples caixa de seleção e seletor de categoria dentro das Propriedades do Writer Feature Type:

Aqui estão as Propriedades do Writer Feature Type que vejo no Pro/FME:

Onde está a funcionalidade Feature type Fanout?

Obrigado,

-Adam

Encontre mais publicações marcadas com

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

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

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