Has anyone ever had issues importing a .csv as events into ArcMap (or Pro) and having it interpret String fields with a length of 8000? This winds up creating viable feature classes with the same issue that break most geoprocessing tools because of the field lengths. I'd love to know how to avoid this.
Solved! Go to Solution.
I just have it for the first time after several years using .csv with text columns as the most reliable format for joins. What a bummer that such a bug does not get addressed and thanks for the workaround! My first attempt was to export the csv to a dbf and set the text length to 254. It still did not work. The join-values come from the file that I want to link back to. So next attempt in a new project did work with the newly created dbf but not the original csv.