2.9 Display XY data, and Coordinate Table to Point Error Invalid SQL statement used

714
4
Jump to solution
01-08-2022 11:37 AM
Labels (3)
MichelleWilliamsERM
Occasional Contributor II

I've tried all the normal tools to get this to work, but I think the underlining code is broken.

Please help.

Esri9.0 error coord tried DDM csv.png

Esri9.0 error coord tried DDM.png

Esri9.0 error coord tried float and double.png

   

Esri9.0 error coord tried Show XY from csv.png

Tags (3)
0 Kudos
1 Solution

Accepted Solutions
DanPatterson
MVP Esteemed Contributor

why don't you show some of your table since I have used those tools many times.

Things that can go wrong... too many to list, but blank entries, wrong text encoding, punctuation within text,  ... symbols in text (like a degree symbol) etc etc etc.

Excel to table is pretty good, but will fail if a lot of rules aren't followed.  Excel to csv ... same thing.

I suspect your issue is within the table


... sort of retired...

View solution in original post

0 Kudos
4 Replies
DanPatterson
MVP Esteemed Contributor

DD2, aka decimal degrees, 2 fields is the default, 

your field type latfloat, should work

I would suggest

XY Table To Point (Data Management)—ArcGIS Pro | Documentation

to ensure nothing is wrong fundamentally with the data ot

Make XY Event Layer (Data Management)—ArcGIS Pro | Documentation


... sort of retired...
0 Kudos
MichelleWilliamsERM
Occasional Contributor II

@DanPatterson, can you tell me that this tool works for you in Pro 2.9?

I've tried both suggestions, and I get the error when I try to open the attribute table.

Here's my workflow;

csv file to table to points (but I haven't gotten to the points yet).

I also tried importing the Excel table to points.

 

0 Kudos
DanPatterson
MVP Esteemed Contributor

why don't you show some of your table since I have used those tools many times.

Things that can go wrong... too many to list, but blank entries, wrong text encoding, punctuation within text,  ... symbols in text (like a degree symbol) etc etc etc.

Excel to table is pretty good, but will fail if a lot of rules aren't followed.  Excel to csv ... same thing.

I suspect your issue is within the table


... sort of retired...
0 Kudos
MichelleWilliamsERM
Occasional Contributor II

Thank you everyone for you comments, I had a teammate try it on his 2.8 software and it broke, so with more digging we found a " in the header from another field.

0 Kudos