I am moving to 10.3 and trying to move from the SDE commands.
Like many people, I find fieldmapping confusing. I am writing an append script and took the "copy as python snippet" from the results table. One thing I am not seeing documented - what order are the various properties stored in the import-export string? Some are self-evident, but the multiple boolean and integer fields are not so easy Does someone have the order of the properties in the string?
Finally found the answer. It was in Field Mapping logic for 9.2
"Here are the field mapping text parameters:
[Field Name] [Alias] [Editable] [IsNullable] [IsRequired] [Size] [Type]
[Precision] [Scale], [Merge Rule], [Delimiter], [Input Field Location, Input
Field Name], [Start Postion, End Postion], [Additional Input Field Location,
Input Field Name], [Start Postion, End Postion]
IsRequired is a hidden property and not assignable.
The booleans are the [Editable] [IsNullable] [IsRequired]
The recommended method by development is to use the field mapping object and not
the string."
A big thank you to the author, Dave Bollinger, and Simon Willis, whose link led me to it. I wish ESRI would document since I wanted to use fieldmappings, but could not find an example with append.
I agree!!! Good find.
For the price we pay for ESRI.... I would expect full documentation.
This we are not getting.
Thanks for posting. It helped me!
The documentation for field mappings, as done through python objects is pretty good, when you can get your head round them
What were you specifically trying to achieve, I can probably bash up a sample for you to show you how it works for your use.