Census Field Alias Replacement : how best to potentially employ the schemaMapper or/and AttributeExposer to create an alias look up table from a CSV file .

To be honest, I am not 100% sure on what you are trying to achieve. But if it to rename the fields held in the "CSV_FIELD" to the name held in "DESCRIPTION" (e.g. BLOCK20 to Census Block Geocode), then just use schemamapper and choose this file. Set up attribute mapping and CSV_FIELD is your source and DESCRIPTION is your destination.

Hi Todd, I accessed your tool and created an action.

However, I believe part of the issue I'm having is getting the originating Fields names to be changed to a value in the source field which is NOT in the same table as the destination. It's in a separate CSV table.

Alias Source table field is CSV .

Field in Destination table has 165 fields to rename :It's a one to one field NAME replacement ...

I think I might need to add another element for each field?

I'm trying to rename the FIELD NAME, not rename the attribute value.

So based on the Source ( Alias table) P0020001 would be changed to Population P2 (Destination Field Name Alias)

P0020002 would be changed to Hispanic Origin etc.

Hi,

I believe this is what you need but I will go into more depth, as there some things that are not obvious.

So the schemamapper with attribute mapping is what you want and you would select the dbf as source and the csv as destination. Here is my example

But what the schema mapper doesn't do is "expose" those "new" attributes to the workspace. (They are now there but not visible as an attribute in the canvas environment).Easiest way is to use the AttributeExposer and "Import". Choose the CSV and import "Attribute values" from the relevant field.

Attached is my example workspace.

Cheers,

Todd

Thank you.