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

再びこんにちは、

私はまだArcGIS Proの古いバージョン向けの2回目のETLトレーニングを進めています。違いがあることは承知していますが、これが私が知っている唯一の空間データETLトレーニングです。

Pro 2.6.3およびFME 2020.0.1.0（20200407 - Build 20218 - WIN64）で作業中です。<\/EM><\/P>トレーニング： Extract, Transform, and Load Processesを使用したデータ変換の制御 | Esri Training Web Course

最終的には、Writer Feature Typeの「Fanout」機能を使用する必要があります。

私は2つのReader Feature TypesをPointOnAreaOverlayerに接続しており、そのポイント出力はPoint Shapefile Writer Feature Typeに接続されています。最初の問題は、PointOnAreaOverlayerとWriterにリストされているすべての蓄積された属性間のトレーニングでの魔法のような相互接続をどのように複製するかでした。指示に従いましたが、「Copy Attributes from Transformer」を使用した後、Writer内の「Name」属性に赤いノードが表示され、実行時にOverlayerからデータを取得しませんでした。（「NAME」はポイント出力でキャプチャする必要があるポリゴンレイヤーのフィールドです。）OverlayerのAttribute Accumulation - Merge Attributesを見つけ、Accumulation Modeを「Merge Incoming」に設定しました。これにより、Overlayerはポイント属性出力リストにポリゴンの「NAME」属性を表示し、ポイントWriterから見えるようになりました。以前のFMEバージョンではこれを行う必要はありませんでしたか？それともより多くの機能が追加設定を強制していたのでしょうか？

さて、本題に入ります…

「Feature type fanout」を行う必要があります。以下はWriter Feature Type Properties内のシンプルなチェックボックスとカテゴリピッカーのトレーニング画像です：

こちらは私がPro/FMEで見ているWriter Feature Type Propertiesです：

Feature type Fanout機能はどこにありますか？

ありがとうございます。

-アダム

タグ付けされた投稿をもっと見る

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

会話に参加する

サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか？無料アカウントを登録してください。

クイックリンク

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