1

I currently have shapefile of US PUMAS and another feature shapefile (call it feature X). I am using ArcPy to project both of these files to the following projection coordinate system (using Project_management):

http://spatialreference.org/ref/sr-org/nad_1983_contiguous_usa_albers/html/

After projecting, I use intersect_analysis and then CalculateAreas_stat to compute the intersection areas. Finally I output a .csv file, which I then use to compute area weighted means.

The issue is that every time I run my simple script, the intersection areas vary by a small amount (somewhere to the 8th decimal point). These small changes are impacting my analysis.

If this is a GIS precision issue or if I making a mistake, how can I go about fixing it?

closed as off-topic by PolyGeo Oct 7 '18 at 3:25

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "When seeking help to debug/write/improve code always provide the desired behavior, a specific problem/error and the shortest code (as formatted text, not pictures) needed to reproduce it in the question body. Providing a clear problem statement and a code attempt helps others to help you." – PolyGeo
If this question can be reworded to fit the rules in the help center, please edit the question.

  • I suggest loading the shapefiles into a file geodatabase, don't work with the shapefiles which have lower precision. Another thing - why do you use the CalculateAreas_stat, any specific reason for that? I suggest using the Calculate Field with the !shape.area! resources.arcgis.com/en/help/main/10.2/index.html#//…. – Alex Tereshenkov Mar 10 '15 at 11:39
  • 1
    Shapefiles have lower precision? That's not correct. Shapefiles and (high precision) geodatabases are both using the equivalent of double precision. – mkennedy Mar 10 '15 at 15:48