Hi Bern, Thanks for weighing in on this. I've done exactly as you described, and have been repeating the same pattern, over and over again. I have tried copying and pasting the attribute data into an Excel .csv on my local drive, which uploads to the AGOL map correctly. When the exact same data are either uploaded as a file to Google Drive and then imported as a .csv from the web, or pasted into a new empty Google Sheet as a new file and brought in, the shift happens. I have tried this keeping the latitude and longitude as a number, and also as a text field, and get the same issue.
When I took the correct coordinates from the original point (to 5 or more decimal places) and put them into the search function in the AGOL map, the location was similarly shifted.
Here's the feature class uploaded, with freshly-recalculated x,y, and when I put these coordinates into the search function, I get the off-set in the same place the Google Sheet .csv lands.
Interestingly, I have also had the same issue when bringing in the same .csv stored on Google Drive into a Google Maps project.
I hope there might be some "smoking guns" here that can aid in getting to the bottom of this. Is the difference between taking the decimal degree out from 6 to 8 places a culprit?