AGOL Overgeneralizing Coordinates

[LilyMaddox]

Hello! I have a very simple asset map here that I built from a CSV using Latitude and Longitude columns. Because my points are all in the same county, it's important that the coordinates go 6-8 decimal places out. For some reason, I'm finding that when when I upload the CSV, it automatically shortens my coordinates to two decimal places. So I'm now having this problem where it appears that some of my points are overlapped despite having completely different addresses. I tried to go into "Fields" to change this, but it seems that the changes are only displayed in the popup and not the actual point location. I'm sure I'm missing something so simple here, but am completely stuck. 

[DavidPike]

What you're seeing in the popup is default rounding,  I don't think it's truncated your data values.  The easiest way to see this would be to start editing the data and you'll see the true precision of the values.

in the general U.S latitude, 8 decimal places would be (roughly) 0.1cm on the ground, 6 decimal places would be 10cm.

Are you sure that the coordinates are maybe not a bit funky?  Maybe a check on google maps for 2 values.

[LilyMaddox]

Ah yes, you're right. When I looked at my Edit, it showed me longer values that were slightly incorrect. Going back to my CSV, I saw that my Geocoder's actually the culprit. When I plugged in my addresses and some of the coordinates, it returned about 15/90 of my points with rounded decimal points. Then, when I plugged that sheet into AGOL, it extended those now shortened coordinates back out to a central point. Thank you for the help! Wouldn't have caught that.

[ToddHalvorson]

Have you tried generating a shapefile from your X,Y data in Pro, define the appropriate coordinate system to the file, add your attribute fields and then creating the service from that?   Typically when I need a feature class that would be my approach.