Solved! Go to Solution.
There is one instance in which a schema.ini file will be created by ArcGIS when opening a delimited text file: when the format for a certain field cannot be reliably determined. In this case, a schema.ini file will be created containing the presumed format of the field.
Hi Chris Fox and Curtis Price ,
I have a similar issue, but when I use Table to Table (Conversion) my custom Schema.ini file is overwritten by the tool. So if I try to force a field to be a specific type the tool deletes my changes and makes it's own file reverting back to the incorrect field types.
I would prefer to hard code each field in the Schema.ini file as long as ArcGIS doesn't overwrite it. Is there a way to lock the file down?
Thanks,
John S.
System:
Windows 7
ArcGIS 10.1
Example Schema.ini:
[AOIs.csv]
Col1=Facility_Name Text Width 20
Col2=Date Date
Col3=Leader Text Width 50
Col4=Occurrence Text Width 35
Col5=Nature_of_AOI Text Width 35
Col6=Mapsite Text Width 150
Col7=Distance Text Width 25
Col8=Start_Point Text Width 20
Col9=End_Point Text Width 20
Col10=Total_Length Text Width 20
Col11=Starts_in Text Width 5
Col12=Comment Text Width 255
Example input CSV/Text:
Facility_Name,Date,Leader,Occurrence,Nature_of_AOI,Mapsite,Distance,Start_Point,End_Point,Total_Length,Starts_in,Comment
Place #1,2/1/2015 00:00,"Appleseed, Johnny",Daily,AOI A,"Site-1",376 Upstream,"012345, 0123456",,,No,At the Termination Point.
Place #2,2/2/2015 00:00,"Wayne, Bruce",Daily,AOI B,"Site-2",376 Upstream,"012345, 0123456","012345, 0123456",,No,At the Termination Point.
Place #3,2/3/2015 00:00,"Kent, Clark",Daily,AOI C,"Site-3",376 Upstream,"012345, 0123456",,,No,At the Termination Point.