Tag Info

New answers tagged

0

I found out that my issue was simply that statistics did not get recalculated when I reclassified my rasters


1

Try putting the output shapefile in a different folder - such as C:\temp\test_083c15_contour.shp. I think you might be having problems because 1 of your folders is named with a leading number or your output shapefile is named with a leading number.


0

I would first make a join of the two tables crime and population. Then I would add another column where I calculate the crime case per population, simply divide the crime case column by the population coloumn. Works if the numbers refer to the exact same areas. Then you can visualize this column in a choropleth map and immediately see where the crime is ...


1

I tested the ZonalStatistics function with overlapped polygons shapefile as zone data. Shapefile is converted into a raster, so overlapped areas are lost. As workaround I tried to extract every polygon feature from the shapefile and process the ZonalStatistics. The script does not contain def. Summing up what it does: Define the input variables Create ...


4

You can't give your existing cells a distance to the line feature as in the Point Distance tool for vector points. You can, however, calculate a new raster of distances to the line feature using the Euclidean Distance tool. You will have to ensure that you sent your cell size and snap raster to the original raster, so you get essentially a new raster with ...


0

have you tried "Euclidian distance" ? you can set up the environment so that the pixel size is the same as your other raster.


2

The first error message comes from the fact that your raster is in float, so you have more that 65535 (aka 16bit) possible unique values, but this does not mean that the values is larger than 65535. You should convert your a raster to integer (e.g. with copy raster or with Int(raster) in map algebra tools) if you want to be able to build unique values, but ...


3

A solution to this is discussed on the ESRI forum here: Every planar surface has a simple formula, Jesse, in the form (something)*x + (something else)*y + (constant). In the Raster Calculator, x is $$XMap and y is $$YMap. The trick is figuring out the coefficients. Often you want to specify a plane in terms of its slope (s), aspect (a), ...


2

To do this you would need a 3d Analyst and Spatial Analyst license. First, elevate your waterbody using Interpolate Shape, this will give the baseline for your elevations by attributing the polygon with the Z values from the DEM to each vertex. Build a terrain with your waterbodies as the elevation data source (perhaps buffer by a small amount and include ...


1

what happens when you load the county layer and the coordinates in a fresh new mxd, do they overlay (just these two layers in a new arcmap session)? Ok so this worked. Likely a different projection in the TOC / Map or a selection issue..


1

It appears as though you have background geoprocessing for your script enabled. Disable background geoprocessing for this tool and try running it again. Additionally, you are introducing an infinite loop in your script. Change your while loop to include the df.time.currentTime += df.time.timeStepInterval snippet: while df.time.currentTime <= ...



Top 50 recent answers are included