Latest Contributions by MikeCusi

What did you use as the base height for the transparent layer? Are they all in the same xyz coordinate system? ... View more

Reprojection tends to introduce a bit of data massaging as the pixels which do not have any data will have to be given some value somehow during the resampling/rotation/ reprojection. If you need to maintain the actual values of the pixels you would need to convert the raster to points, reproject the points, then convert it back to raster of the exact same pixel size. ... View more

If you only need protection from inadvertent editing, changing the file attribute of the shapefile by right clicking on the file in explorer selecting properties and ticking the box for read-only should do the trick. It is however just as easy to tick it off. ... View more

Hi Heather, NN is the default resampling as it is the least processing intensive. If it was cubic or bilinear it should look better than NN. So I would expect that NN will be used if no resampling method is specified. As there seems to be no solution yet from ESRI, we are left only with workarounds which is always painful .  If the only other alternative is to use the degraded image, I am sure we or maybe someone else can work out a better way of accomplishing what I suggested earlier. You can resample each (of the 600) tiffs to the pixel sizes you would like to use for your "pyramids" and then mosaic them all together (or into predetermined tiles if it is just too big). This can all be batched so it will just take some time but you would at least get a decent looking map. What do you use for serving/accessing the images in the field? Is it an online/mobile one or is it all on a local (laptop/portable) drives? Cheers, Mike ... View more

Perhaps joining the tables first to create a new table should first be done. Then field calculator is possible again. ... View more

running the tool Add CAD Fields before Export To CAD also helps. ... View more

My work-around involves a lot of work but it works. If your rasters are in tiles, you will first create a full resolution mosaic. Then using this mosaic you will create your own set of "pyramids" by resampling your mosaic to the various scales you expect to use in the field. You would then set them up so that they display only at the scales you created them for. Every time you zoom in or out it will just be displaying the optimal rasters. Note that the full resolution mosaic should be displayed only when you are zoomed in at the larger scales. ... View more

Resampling looks like the best option to me. You can then make sure that all your other datasets use the resampled image as your "snap" raster for all your analysis. Use the "Search| Tools" function within ArcMap to look for the tools you need. ... View more

I was just thinking that maybe it does not matter too much as you are for all intents actually working with a ~900m pixel to begin with regardless of whether you have resampled it to 90m. A grid this coarse is always never close to representing the real population. e.g 10 pixels to the left =50, 10 pixels to the right = 100, middle pixel where they meet will be 75? ... View more

The simplest way to do this is to use the resample tool (on your "raw" raster, with pixel size 30 arc-second ~900m) using nearest neighbor so it will not create any new values to a pixel size of 90m. If you want a bit of smoothing, bilinear will be a good technique. Any particular reason why you want to average where two 30 arc-second pixels intersect with a 90 m pixel specially considering that it is population data? ... View more

Correct me if I am wrong but from my understanding what you were wanting was to "resample" your 30 arc-second raster image into a 90-meter raster image? ... View more

Mixing raster and vector inputs in any analysis is one sure way of creating this problem you are in right now. You should choose to do your analysis with either one or the other. Personally I would do all my analysis with rasters as the use of snap rasters avoids this kinds of problems. Is Spatial Analyst available for your use? ... View more

or you can run Raster to point, add a column/attribute to the point feature class, calculate the elevation, then convert it back using Point to raster with the appropriate value field and using the original DEM as a snap raster/source for the pixel size. ... View more

You could separate segment distances with "/" for branching roads/junctions. "25mi/135ft/149ft" could mean turn at junction 25 miles from 0 along HW, Then turn at junction 135ft from there, then house that is 149ft from last junction. Perhaps you can also add an extra column or two in your database to accommodate the lat-long for each house. If you have a road network defined, the points defined by the lat-long can also be used in conjunction with it so that emergency services could use that for such cases. As you are working with a blank canvas..... ... View more

House numbers based on distance is the way to go. One thing to keep in mind though is that most address geocoding algorithms usually adapts a convention of odd and even numbers as being either on the left or on the right side of a road. So find out what the norms are for Alaska before you start assigning the numbers. ... View more