Latest Contributions by IanMurray

almost there. in the arcpy.RasterToOtherFormat_conversion, you are passing along rasters, which is your list of rasters instead of the individual rasters which would just be your variable, raster. Not this: arcpy.RasterToOtherFormat_conversion(rasters ,"OtherFormat","JPEG") But this: arcpy.RasterToOtherFormat_conversion(raster ,"OtherFormat","JPEG") ... View more

If you are needing 1-2 foot contours, then you would be needing a much higher resolution elevation data then what is available from the NED.  Even if you have the 1/3 arc-second data(which it sounds like you do), that means each cell is 10m x 10m and you get the average elevation for that 10m x 10m.  While you can generate contours from this at 1-2 feet, generally speaking the elevation data isn't fine enough for it to be accurate at all or true to the actual surface.  For 1-2 foot contours, you would need likely 1m resolution DEM, which would likely only be available where LiDAR has been flown.  You can check the United States Interagency Elevation Inventory(USIEI) hosted by NOAA to see if your area could have LiDAR derived data. Where is your Area of Interest, and how large of an area are you looking at?  Also could you provide the link you used to download the data(I'm guessing it was a ftp connection through either NRCS or USGS Earth Explorer or something similar)? ... View more

Make sure you know what units the raster are in, generally they are in meters, not feet for elevation.  What is the source of your DEM data and what sort of resolution is it? ... View more

I'm going to agree with Blake, the new cursors are much more managable(not to mention much faster) for doing what you are needing to do.  Never used the old style ones to be honest. What might be the problem is it seems your indentation is off from what you were previously using for that particular if statement.  You indented 8 spaces instead of 4 like the rest of your script(indentation on the else statement below seems correct), so it might be skipping the inside of your if statement?  Or it could be the syntax highlighting in the forum. ... View more

in tools like ListRasters the "*" acts as a wildcard that will take any string name.  So if you have  "DEM*"  it will return any jpegs that begin with "DEM" and have any characters following it.  This does not work with arcpy.RasterToOtherFormat_conversion as an input, since it is checking for a raster at a specific file path, not attempting to find multiple rasters as the ListRasters does.  ListRasters is intended to get a list of all the rasters of the name and type you indicated, which you can then use as the input for other geoprocessing tools. ... View more

This could be as simple as the fact that updateField is a list with one item, and the argument it is expecting is a string, not a list. Try either changing if row.getValue(updateField) == None: to if row.getValue(updateField[0]) == None: or changing your updateField variable to a string, not a list with a single string in it. ... View more

you need to replace arcpy.RasterToOtherFormat_conversion("*.jpg","OtherFormat","TIFF") with arcpy.RasterToOtherFormat_conversion(raster , "OtherFormat","TIFF") List Rasters returns a list of raster string paths, so when you loop through them, raster represents the file path for the raster you want converted. ... View more

From most of the scientific papers I have read, generally it is acceptable to generate cells of the same dimensions as the average point spacing of the Las file.  That is if your average point spacing is 1.3, then it would okay for your cell size to be 1.3m by 1.3m(1.69m^2).  Otherwise I would say you are very much under utilizing your data, since you will be having ~20 points being used per pixel instead of ~1. Donald, have a look at page 5 of this ISPRS paper, it should explain why the smaller cell size is acceptable. ... View more

Unfortunately, I don't believe there is.  I know when I convert shapefiles to be kmls in Google Earth that it will popup the attribute table for that feature on click, but with rasters with or without and attribute table, I'm not getting anything.  Perhaps you will need to make a very fine fishnet polygon behind the raster which stores the elevation values in an attribute table that will show up on a click, could work as a possible solution.  Maybe Raster to Point, then Create Fishnet, and then a spatial join?  If your dataset is very large, it could become impractical, but might be worth a shot. ... View more

First number is your northing, second is your easting, third is elevation value, in whatever unit value your coordinate system is in(you can have HARN State Plane in either meters, international feet, or feet).  Check what your linear unit is for your projection and that will tell you what units it is in. ... View more

Are your points numbered or sorted in any meaningful way in your attribute table? ... View more

Welcome though I am curious if someone could come up with a more elegant way to manage this process.  Maybe generating the near table from the feature to vertices to determine the closest coordinate, using those coordinates then inserting new x,y coordinate of the point into the line segments geometry using an Update Cursor based on the nearest vertex in the near table.  No time for me to experiment today, but maybe some other time.   ... View more

This exact question has been asked on stack exchange, you may to try their idea of using topology. ... View more