Why does OBJECTID appear in the output in step 5?

Why does OBJECTID appear in the output in step 5?

• A. The Parks dataset defines this attribute in its MITAB schema
• B. The CommunityMap [FILEGDB] Schema Source has a table named Parks that has this column.
• C. All GML feature types must contain this attribute.
• D. All feature types, regardless of format, must contain this attribute.

Answer: (B)

ObjectID appears because it is defined by the source schema you’re using. The CommunityMap [FILEGDB] Schema Source includes a Parks table that has an OBJECTID column, and FME preserves that schema attribute in the output. So, in step 5 you see OBJECTID simply because the schema source defines it. This isn’t a universal requirement for all formats (MITAB, GML, or other formats don’t mandate an OBJECTID), but it is present here due to the specific FILEGDB schema you loaded.

ObjectID appears because it is defined by the source schema you’re using. The CommunityMap [FILEGDB] Schema Source includes a Parks table that has an OBJECTID column, and FME preserves that schema attribute in the output. So, in step 5 you see OBJECTID simply because the schema source defines it. This isn’t a universal requirement for all formats (MITAB, GML, or other formats don’t mandate an OBJECTID), but it is present here due to the specific FILEGDB schema you loaded.