arcgis-10.3arcgis-desktopattribute-tablegps
I had import shapefiles data which is a point features from GPS receiver. The points are well on pointed on the ArcGIS display, but when I open each attributes table, there is no field show the latitude and longitude of the points while the points were shown at display in a correct location abse on my georeferenced map. Why? The attributes only show the ObjectID, Shape, and Comments.
I am using ArcGIS 10.3 for Desktop.
When someone says that data points are tiny compared to other data layers, the usual problem is that the new points have been assigned a projected coordinate system--probably the one that the other layers are using--but the new points are latitude-longitude and should be assigned a geographic coordinate system.
The Add XY tool will default to the data frame's coordinate system. You need to change that to match what these points are in.
Even though you're seeing latitude-longitude in the data frame, the display units (data frame properties, general tab) may have been set to show degrees or degrees-minutes-seconds even though the data frame's coordinate system is projected.
Did you edit the data in that table at all? It's strange how there is one row with its lat/longs in DDMMSS when all the others (the ones that aren't blank) are in decimal degrees. Also, do the points which are missing positional data actually show up in ArcMap? Are they where they're supposed to be?
As far as the missing data, it looks like everything went fine during data collection on 2/4/2014, all those points have lat/longs, etc. But on 3/4, they don't. I suspect the Trimble is working fine but some other problem cropped up during data collection: too few satellites to get a location fix, for example, or maybe the field team didn't record enough points at each location to get a fix. You could export the file again, but modify the Export Setup to include the data's DOP values, Correction Status, and number of positions recorded to diagnose the problem.
ETA: In light of your comment that differential correction isn't working, I think that's probably the problem. If your export is set up to not export any uncorrected positions (which is the default setting, I think), and you weren't getting real-time corrections in the field on 3/4, then your features would export with no positions, and therefore no lat/long, precision, or height.
So I'd try to get differential correction working first. If it's not able to transfer base station files, you can try:
If you want to confirm that the lack of differential correction is the problem, you can change your Export Setup to include all positions when exporting. It's under the Position Filter tab in the Export Setup Properties:
I believe that with all those boxes checked, you should see lat/longs for all your points in the exported file. Of course, without differential correction, they will probably be a little further away from their actual location than the corrected points.
Best Answer
Because that is the classical layout of the Shapefile, or geodata in general. The coordinates are not shown here since it would be not a good idea when you have for example a polygon with hundreds of points. Thats why the underlying geometry is stored differently.
For the shapefile it is stored in the .shp file. Think of it as a small database with relations of tables with polygons/lines/points to tables of coordinates.
To have columns that are showing you latitude and longtitude you have to add columns for them and fill them with the values:
You go to the attribute table and there to options "Add field" and give it float or double as data-type. The right-click the new columns and go to "calculate geometry" and choose X-Coordinate/Y-Coordinate. Then the field is populated with the latitude and longtitude values.