How to transfer geocoded csv table and a related table to an ESRI feature class and related table (linked via relationship class) with pre-determined schema.

The easiest thing to do is add the table/feature class as a reader and then copy the attributes from the reader to the output by right clicking the output and click "Copy Attributes from Feature Type". Saves a lot of time trying to set things up.

Also, whatever you set the "Type" to is what it will write as. Text will be converted to numbers automatically.

On a side note, whenever you aren't sure of what you are about to be writing. It's best to add a _1 to the feature class name on the writer to create a new feature class. Then you can run the data into a temp space, verify the results, and remove the _1 when you are sure it's what you want.

@allasimon FME can't create a relationship class in a Geodatabase. The relationship class must already exist in your geodtabase, or use a template. The tutorial Introduction to Working with Geodatabase Relationship Classes will take you thru the steps. If you're not familiar with FMe's Geodb writer and templates then How to use an Esri Template Geodatabase

Hi @jlbaker2779,

Thanks for your suggestions above. I have already done that and the writer has the imported schema from the feature class I eventually want to write to. Could it have something to do with the date field?

feature class written above but with no schema definition. Then used as a reader to write to defined schema below.

imported schema definition above

***An error occurred while attempting to convert the '' component of a date. A possible reason for this is that the data in the date field may be corrupt

Some of the other errors that follow in the log are:

An error occurred while attempting to convert the '' component of a date. A possible reason for this is that the data in the date field may be corrupt

Storing feature(s) to FME feature store file `Q:\\log.ffs'

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Feature Type: `Welfare_MainTable_test01'

Attribute(encoded: windows-1252) : `Call Identification Number' has value `00-00-02'

Attribute(encoded: windows-1252) : `CallIdentificationNumber' has value `00-00-02'

Attribute(encoded: UTF-8) : `GeoCoded_y_n' has value `No'

Attribute(encoded: windows-1252) : `OBJECTID' has value `'

Attribute(64 bit real) : `_latitude' has value `5815849.601'

Attribute(encoded: UTF-8) : `_longitude' has value `1940095.127 '

Attribute(encoded: windows-1252) : `accomnumberofadults' has value `'

Attribute(encoded: windows-1252) : `accomnumberofchildren' has value `'

Attribute(encoded: windows-1252) : `accomrequestreason' has value `BACKFILL'

Attribute(encoded: windows-1252) : `accomrequirements' has value `'

Attribute(encoded: windows-1252) : `additionalnotes' has value `'

Attribute(encoded: windows-1252) : `additionalrequirements' has value `'

Attribute(encoded: windows-1252) : `animalagencynotes' has value `'

Attribute(encoded: windows-1252) : `animaldateofreferral' has value `'

Attribute(encoded: windows-1252) : `animalneednotes' has value `'

Thanks again,

Simon

Hi @markatsafe,

I did see that tutorial so maybe I'll give it a go. I thought that I could write both files indidually to the desired feature class and table schema, create the relationship in arc afterward using the call id fields in both tables, then change this to a globalID/parent global id relationship afterward?

But I am having serious issues pushing all the fields defined as text in the output csv or feature class to a feature class with the imported desired feature schema.

Thanks,

Simon

I see. Use a dateformatter and set the output format as %Y%m%d. That will convert it to YYYYMMDD. That should have no problem writing. Make sure you catch the rejected if any fail and adjust accordingly.

But if you're having trouble with the straight load of the tables that's something different altogether. If you can add some sample data and an export of your Geodb schema and your workspace we should be able to sort it out (or to mark @ safe.com if the data is more sensitive)