![]() ![]() I then converted my USGS/NCRS Soils shape file (containing ~25,000 polygons) to a raster using the cell size of the other raster files (slope, dem, and aspect). Eachof the rasters output shared identical extent, rows/columns and cell size which was desirable. Each raster was cut after selecting the Snap Raster option under Environment | Processing Extent. I then cut each raster using the kentucky boundary shapefile (polygon) that also was in GCS WGS_1984. I also ensured that the cell size (both X and Y) were square and the same for all the raster layers. I started with all my data (DEM, Aspect, Slope, Land Use/Land Cover) in GCS (WGS_1984) at a much larger extent than I will require output at. ![]() I decided to re-cut all my data layers in hopes that some of the issues I was experiencing would vanish. but you must have a need to use a GCS, just a warning for others in general Be careful with this since you are unfortunately working with geographic coordinates and the 8th decimal place in a GCS is sadly not the same precision as the same representation in projected coordinates. check the left bottom alignment and cell size and prune everything to the minimum of the inputs. What I think is happening is that the erroneous files are trying to be squeezed/stretched (whatever) into an extent at the same time as the lower left corner and cell size is being aligned. In this vein, it would be best to get that established first, then trim any extra rows and columns from the top and left after all rasters align to the lower left and all have the same cell size. they are independent of the general analysis extent. The important think to deal with for processing in the first instance is the bottom left hand corner and the cell size must match. Snap Raster (Environment setting)-Help | ArcGIS for Desktop ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |