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

¿Desglose por Tipo de Entidad?

AdamRepsher

Hola de nuevo,

Sigo trabajando en la segunda capacitación de ETL (para versiones anteriores de Desktop) en ArcGIS Pro. Sé que hay diferencias, pero estas son las únicas capacitaciones de ETL para datos espaciales que conozco.

trabajando con Pro 2.6.3 y FME 2020.0.1.0 (20200407 - Build 20218 - WIN64)

Capacitación: Controlando Traducciones de Datos Usando Procesos de Extract, Transform, y Load | Curso Web de Capacitación Esri

En última instancia, necesito usar la función "Fanout" del Writer Feature Type.

Tengo dos Reader Feature Types alimentando un PointOnAreaOverlayer, con su salida de puntos conectada a un Point Shapefile Writer Feature Type. El primer problema fue descubrir cómo duplicar la mágica interconexión del entrenamiento entre todos los atributos acumulados listados en el PointOnAreaOverlayer y el Writer. Seguí las instrucciones, pero después de usar "Copy Attributes from Transformer", el atributo "Name" en el Writer tenía un nodo rojo y no recibía datos del Overlayer al ejecutar. ("NAME" es el campo en una capa de polígonos que debe capturarse en la salida de puntos). Encontré la Acumulación de Atributos del Overlayer - Merge Attributes y configuré el Modo de Acumulación a "Merge Incoming". Eso permitió que el Overlayer mostrara el atributo "NAME" del polígono en la lista de atributos de salida del punto, y fuera visible para el Writer de puntos. ¿En versiones anteriores de FME esto no era necesario? - ¿O más funcionalidad requería capas adicionales de configuración?

Ahora vamos a la parte real de la pregunta...

Necesito hacer un "Feature type fanout." Aquí está la imagen del entrenamiento con la simple casilla y selector de categoría dentro de las Propiedades del Writer Feature Type:

Aquí están las Propiedades del Writer Feature Type que veo en Pro/FME:

¿Dónde está la funcionalidad Feature type Fanout?

Gracias,

-Adam

Encuentra más publicaciones etiquetadas con

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

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

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