I'm working on a project to add point locations to a map using the arcpy.MakeXYEventLayer_managment tool in Python. This tool is acting unpredictable and causing a fatal EOFError (End Of File) exception every other time I run my script. Half the time it completes normally with no modifications. I've tried different inputs to the MakeXYEventLayer tool consisting of a .csv file, .dbf file, and a table view. None of these seem to make a difference. This is a current short snippet of the latest attempt: import arcpy basePath = 'C:\Users\Jason\Documents\SchoolStuff\GEO 4393C' workspacePath = basePath + '\FinalProject\Project.gdb' arcpy . env . workspace = workspacePath arcpy . env . overwriteOutput = True locationsFilePath = basePath + '\FinalProject\Locations\MiniGolfLocations.xls' locationsTable = 'MiniGolfLocations' arcpy . ExcelToTable_conversion ( locationsFilePath , locationsTable , 'MiniGolfLocations' ) print 'Done converting spreadsheet to table' arcpy . MakeXYEventLayer_management ( locationsTable , 'LONGITUDE' , 'LATITUDE' , 'USpoints' ) print 'Done creating xy event layer' arcpy . CopyFeatures_management ( 'USpoints' , workspacePath + '\USpoints' ) print 'Done creating USpoints' Has anyone else run into this problem before or have any suggestions?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Problem with arcpy.MakeXYEventLayer in Python Script

JasonBartling

I'm working on a project to add point locations to a map using the arcpy.MakeXYEventLayer_managment tool in Python. This tool is acting unpredictable and causing a fatal EOFError (End Of File) exception every other time I run my script. Half the time it completes normally with no modifications. I've tried different inputs to the MakeXYEventLayer tool consisting of a .csv file, .dbf file, and a table view. None of these seem to make a difference. This is a current short snippet of the latest attempt:

<SPAN class="keyword token">import</SPAN> arcpy

basePath <SPAN class="operator token">=</SPAN> <SPAN class="string token">'C:\Users\Jason\Documents\SchoolStuff\GEO 4393C'</SPAN>
workspacePath <SPAN class="operator token">=</SPAN> basePath<SPAN class="operator token">+</SPAN><SPAN class="string token">'\FinalProject\Project.gdb'</SPAN>

arcpy<SPAN class="punctuation token">.</SPAN>env<SPAN class="punctuation token">.</SPAN>workspace <SPAN class="operator token">=</SPAN> workspacePath
arcpy<SPAN class="punctuation token">.</SPAN>env<SPAN class="punctuation token">.</SPAN>overwriteOutput <SPAN class="operator token">=</SPAN> <SPAN class="token boolean">True</SPAN>

locationsFilePath <SPAN class="operator token">=</SPAN> basePath<SPAN class="operator token">+</SPAN><SPAN class="string token">'\FinalProject\Locations\MiniGolfLocations.xls'</SPAN>
locationsTable <SPAN class="operator token">=</SPAN> <SPAN class="string token">'MiniGolfLocations'</SPAN>

arcpy<SPAN class="punctuation token">.</SPAN>ExcelToTable_conversion<SPAN class="punctuation token">(</SPAN>locationsFilePath<SPAN class="punctuation token">,</SPAN>locationsTable<SPAN class="punctuation token">,</SPAN><SPAN class="string token">'MiniGolfLocations'</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="keyword token">print</SPAN> <SPAN class="string token">'Done converting spreadsheet to table'</SPAN>

arcpy<SPAN class="punctuation token">.</SPAN>MakeXYEventLayer_management<SPAN class="punctuation token">(</SPAN>locationsTable<SPAN class="punctuation token">,</SPAN><SPAN class="string token">'LONGITUDE'</SPAN><SPAN class="punctuation token">,</SPAN><SPAN class="string token">'LATITUDE'</SPAN><SPAN class="punctuation token">,</SPAN><SPAN class="string token">'USpoints'</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="keyword token">print</SPAN> <SPAN class="string token">'Done creating xy event layer'</SPAN>

arcpy<SPAN class="punctuation token">.</SPAN>CopyFeatures_management<SPAN class="punctuation token">(</SPAN><SPAN class="string token">'USpoints'</SPAN><SPAN class="punctuation token">,</SPAN>workspacePath<SPAN class="operator token">+</SPAN><SPAN class="string token">'\USpoints'</SPAN><SPAN class="punctuation token">)</SPAN>

<SPAN class="keyword token">print</SPAN> <SPAN class="string token">'Done creating USpoints'</SPAN>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

Has anyone else run into this problem before or have any suggestions?

Finde mehr Beiträge mit dem Tag

Accepted answers

forestknutsen1

You could try using an InsertCursor—Data Access module | ArcGIS Desktop

It is way faster and more stable then using an events layer in my experience.

This is how I like to do paths. As in Dan and Darren links point out.

import os

path1 = r"c:\stuff"
path2 = r"more\and\more"

full_path = os.path.join(path1, path2)

All comments

JasonBartling

Ok. Thanks for the information.

DanPatterson_Retired

In a very short period of time you will have to move to python 3, so be aware of future pitfalls regarding path constructs since there are more pitfalls ahead...

basePath <SPAN class="operator token">=</SPAN> <SPAN class="string token">'C:\Users\Jason\Documents\SchoolStuff\GEO 4393C'</SPAN>
workspacePath <SPAN class="operator token">=</SPAN> basePath<SPAN class="operator token">+</SPAN><SPAN class="string token">'\FinalProject\Project.gdb'</SPAN>

&nbsp; File <SPAN class="string token">"<ipython-input-1-bc7a010eb6d9>"</SPAN><SPAN class="punctuation token">,</SPAN> line <SPAN class="number token">1</SPAN>
&nbsp;&nbsp;&nbsp; basePath <SPAN class="operator token">=</SPAN> <SPAN class="string token">'C:\Users\Jason\Documents\SchoolStuff\GEO 4393C'</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="operator token">^</SPAN>
SyntaxError<SPAN class="punctuation token">:</SPAN> <SPAN class="punctuation token">(</SPAN>unicode error<SPAN class="punctuation token">)</SPAN> <SPAN class="string token">'unicodeescape'</SPAN> codec can't decode bytes <SPAN class="keyword token">in</SPAN> position <SPAN class="number token">2</SPAN><SPAN class="operator token">-</SPAN><SPAN class="number token">3</SPAN><SPAN class="punctuation token">:</SPAN> truncated \UXXXXXXXX escape<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

So you remember the 'pirate' thing and raw encode the first bit then try to use that subsequently

basePath <SPAN class="operator token">=</SPAN> r<SPAN class="string token">'C:\Users\Jason\Documents\SchoolStuff\GEO 4393C'</SPAN>&nbsp; <SPAN class="comment token"># ---- cleverly 'r'r'r'ed</SPAN>
workspacePath <SPAN class="operator token">=</SPAN> basePath<SPAN class="operator token">+</SPAN><SPAN class="string token">'\FinalProject\Project.gdb'</SPAN>

<SPAN class="comment token"># ---- big check ---- looks good ---</SPAN>
workspacePath
Out<SPAN class="punctuation token">[</SPAN><SPAN class="number token">3</SPAN><SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="string token">'C:\\Users\\Jason\\Documents\\SchoolStuff\\GEO 4393C\\FinalProject\\Project.gdb'</SPAN>

<SPAN class="comment token"># ---- on to append in Copy_management ----</SPAN>

workspacePath<SPAN class="operator token">+</SPAN><SPAN class="string token">'\USpoints'</SPAN>
&nbsp; File <SPAN class="string token">"<ipython-input-4-393953a8a67e>"</SPAN><SPAN class="punctuation token">,</SPAN> line <SPAN class="number token">1</SPAN>
&nbsp;&nbsp;&nbsp; workspacePath<SPAN class="operator token">+</SPAN><SPAN class="string token">'\USpoints'</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="operator token">^</SPAN>
SyntaxError<SPAN class="punctuation token">:</SPAN> <SPAN class="punctuation token">(</SPAN>unicode error<SPAN class="punctuation token">)</SPAN> <SPAN class="string token">'unicodeescape'</SPAN> codec can't decode bytes <SPAN class="keyword token">in</SPAN> position <SPAN class="number token">0</SPAN><SPAN class="operator token">-</SPAN><SPAN class="number token">1</SPAN><SPAN class="punctuation token">:</SPAN> truncated \UXXXXXXXX escape

<SPAN class="comment token"># ---- it's back again</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

And unless you are trapping errors you will get nice silent failures or unrelated error messages.

Python 3 opens a whole new world called Unicode when it comes to working with text.

JasonBartling

Using an InsertCursor instead looks to have fixed my problem. It's quite a few more lines of code in setup of the feature class and a SearchCursor, but at least it works consistently. Thank you for this suggestion.

JasonBartling

I tried using double backslashes, raw strings with backslashes, forward slashes, and raw strings with forward slashes. None of those options changed my execution results.

forestknutsen1

You could try using an InsertCursor—Data Access module | ArcGIS Desktop

It is way faster and more stable then using an events layer in my experience.

This is how I like to do paths. As in Dan and Darren links point out.

import os

path1 = r"c:\stuff"
path2 = r"more\and\more"

full_path = os.path.join(path1, path2)

DanPatterson_Retired

and for visual examples of Darren's choices on the survey...

Filenames and file paths in python

is a good place to get the reasons why

DarrenWiens2

Whether or not this is your problem, you're playing with fire using backslashes in file paths (e.g. "\t" = tab). In short, don't use backslashes, unless in a raw string. See here for three options - don't use the fourth option.

Nimm an der Unterhaltung teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.