Skip to main content
Solved

feature class import

  • January 3, 2018
  • 7 replies
  • 60 views
L
Forum|alt.badge.img

Hi guys,

i am trying to import some surveying data into a file geodatabase which requireds to have some standardised schema and unique identifiers.Because there are about 200 feature classes to read and 30 feature classes to write it's not very realistic to set up tester for each of them..

I have created a lookup table which include the feature classes names for the both source (from surveyed data) and final dataset. as well as the required field name and value for unique identifier

Because there are other fields required in the final dataset, i have created a fie geodatabase with all reuqired schema so hopefully there is a way i can just import the source data into it.

Thanks in advance and a late happy new year to everyone :)

Best answer by takashi

Hi @lisasays, if you have a chance to create a lookup table that defines how to map the source feature classes to destination feature classes, the SchemaMapper (Feature Type Mapping) transformer may be used effectively.

There are many use cases of the transformer. These articles could be a good starting point to learn about the transformer.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

7 replies

jneujens
Forum|alt.badge.img
  • jneujens
  • January 3, 2018

You can use the schema reader to read the schema of your file geodatabase?

 

Or read your file geodatabase 'as a resource'. Have a look at 'adding a reader as a resource' in FME workbench. In that case, you could use this schema when dynamically writing output data.

 

 

Another way would be to use a AttributeValueMapper. In the transformer properties, you can import the value from your lookup table into the transformer. I am assuming this will save you a lot of time.

 

 

If anything is unclear, give me more details so I can provide a better answer or give an example. =)
takashi
Celebrity
  • takashiCelebrity
  • Best Answer
  • January 3, 2018

Hi @lisasays, if you have a chance to create a lookup table that defines how to map the source feature classes to destination feature classes, the SchemaMapper (Feature Type Mapping) transformer may be used effectively.

There are many use cases of the transformer. These articles could be a good starting point to learn about the transformer.

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
M
Forum|alt.badge.img+2
  • markatsafe
  • January 3, 2018

Hi @lisasays and Happy New Year. From what you have described, @takashi 's suggestion to use the SchemaMapper looks like the best approach.

Also, here are a couple of other suggestions you might consider:

  • Dynamic Workspace. If you do use the SchemaMapper, then you might be able to use a dynamic workflow. This would result in a much simpler workspace and avoid having all 200 odd feature classes as feature types on your canvas.
  • Use a geodatabase or Esri XML Workspace Doc. as the template for your target geodatabase. This will let you create a consistent Geodb

So a combination of SchemaMapper, Dynamic Workflow and Esri XML Template will probably create a simple workflow.

All these might be new concepts to you so don't hesitate to add more comments to this post

L
Forum|alt.badge.img
  • lisasays
  • Author
  • January 4, 2018

Thanks guys, schema mapper is working great and hopefully i can get this done soon.. I had another issue when write the record into my exsisting file geodatabase. i found the fields i created in attribute mapper couldnt get imported into my exiisting file geodatabase..

When i inspect the "mapped" output in schema mapper i can see those fields were created. however cant see those values in the feature classes.

M
Forum|alt.badge.img+2
  • markatsafe
  • January 4, 2018

Thanks guys, schema mapper is working great and hopefully i can get this done soon.. I had another issue when write the record into my exsisting file geodatabase. i found the fields i created in attribute mapper couldnt get imported into my exiisting file geodatabase..

When i inspect the "mapped" output in schema mapper i can see those fields were created. however cant see those values in the feature classes.

@lisasays SchemaMapper doesn't expose the attributes you've mapped. For example, if you use schemamapper to rename an attribute MaterialType -> MATERIAL, you won't see MATERIAL in the workbench. But if you view the feature in Data Inspector then you'll see that it is there. This means that on your geodb writer feature type the MATERIAL attribute port will be red, but that's OK - it should still get loaded into your target geodb.

 

If you do need to use the attribute in workbench, then you need to add an AttributeExposer and then just add MATERIAL. That will make the attribute 'visible' in workbench.

 

L
Forum|alt.badge.img
  • lisasays
  • Author
  • January 5, 2018
@lisasays SchemaMapper doesn't expose the attributes you've mapped. For example, if you use schemamapper to rename an attribute MaterialType -> MATERIAL, you won't see MATERIAL in the workbench. But if you view the feature in Data Inspector then you'll see that it is there. This means that on your geodb writer feature type the MATERIAL attribute port will be red, but that's OK - it should still get loaded into your target geodb.

 

If you do need to use the attribute in workbench, then you need to add an AttributeExposer and then just add MATERIAL. That will make the attribute 'visible' in workbench.

 

Thanks a lot @MarkAtSafe, my issue is even those values can be seen in the inspector but still they couldn't get written into my existing feature classes on writer - in the existing feature classes it has those fields matching the ones created by schema mapper already

 

M
Forum|alt.badge.img+2
  • markatsafe
  • January 5, 2018

Thanks guys, schema mapper is working great and hopefully i can get this done soon.. I had another issue when write the record into my exsisting file geodatabase. i found the fields i created in attribute mapper couldnt get imported into my exiisting file geodatabase..

When i inspect the "mapped" output in schema mapper i can see those fields were created. however cant see those values in the feature classes.

@lisasays you might have to send an example. But the usual culprit would be an upper/lower case mismatch. Check that the attributes you mapping in the schemamapper have the same case as the you geodb field names.

 

Community Stats

32,207
Posts
122,305
Replies
39,891
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.