Latest Contributions by NeilCurri

Hello, I have 2 adjoining DEM rasters that I have combined into a single, continuous raster using Mosaic To New Raster. The two source rasters overlap, and both have some 0 pixel values around their edges. Here's the overlap of one atop the other: [ATTACH=CONFIG]34792[/ATTACH] Here are the options I am using in the Mosaic to New Raster tool: [ATTACH=CONFIG]34794[/ATTACH] In order to deal with the overlap and the fact that some of the pixels at the edge = 0, I set the Mosaic Operator to Maximum. Raster values are in Meters and range from 0 to 1,683, so I use 32 bit unsigned as the Pixel Type. The mosaicked raster looks fine at the boundary. However, at the southeast edge, there is some odd banding that is happening in the display. This is how it looks at 1:125,000 scale, with 2 odd bands of pixels at seemingly odd ranges from the neighboring pixels: [ATTACH=CONFIG]34795[/ATTACH] One of the odd band of pixels goes away when zoomed in at higher scales, but one remains. Here it is at 1:60,000: [ATTACH=CONFIG]34796[/ATTACH] At scales higher than 1:1:57,311, both odd bands of pixels disappear and the raster looks "normal". Here it is at 1:50,000: [ATTACH=CONFIG]34797[/ATTACH] Why the odd display, and why only at smaller scales? Looking at these again, it appears as if the odd bands of pixels are "ghosts" of other parts of the raster. ... View more

Hello, I am creating a composite mosaic dataset from three other mosaic datasets, each of which holds four orthophoto tiles from different years: 2004, 2009, and 2013. The goal was to create a time-aware layer and use the time slider to demonstrate this functionality for my students. The extent of the tiles are the same across years and the coordinate system is all state plane (feet), the only difference between the datasets is that the 2009 photos are higher resolution (0.5 ft) than the 2004 and 2013 (1 ft). After I combine the mosaic datasets into the master mosaic dataset and enable time on the layer, ArcMap does not display the 2009 set when the time slider comes to that year. It's footprint appears, but nothing else, and the other two years display just fine. At first, I tried using "build overviews" to see if that would fix it. It didn't. Then, I looked at the master mosaic dataset's footprint layer. I noticed that identical values are produced for MinPS, MaxPS, LowPS, and HighPS for the 2004 and 2013 sets in the master dataset's footprint attribute table. The LowPS for the 2009 orthos is (expectedly) 0.5, reflecting the higher resolution of this series. However, the MaxPS value is set to 1 for the 2009 set, while for the 2004 and 2013 sets the MaxPS value is 270.(Please see attached screenshot of the attribute table showing.) [ATTACH=CONFIG]34089[/ATTACH] I still wasn't quite sure what the MaxPS field does even after reading the help article on cell size ranges, but I changed it to 270 for the 2009 set, as it was set for the 2004 and 2013 sets, and then it displayed. In order to understand this better, I kept changing the value until I discovered that the image would appear if I set the value to 6 or greater. When set to 5 or less, the image would not appear when moving the time slider to 2009. I would LOVE it if someone can explain to me why so that I can explain it to my students! Thanks! -Neil ... View more

I've created a mosaic dataset for orthophotos for two adjacent towns. There are several overlapping tiles along the town boundary, and the tiles in each town are different sizes. This shouldn't be a problem for a mosaic dataset from what I've read - however, after following the work flow http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#/The_workflow_and_tools_to_create_mosaic_datasets/009t00000039000000, there are gaps along the town boundary where the tiles overlap... But only over some: [ATTACH=CONFIG]19501[/ATTACH] If I load the individual tiles where the gaps appear, it seems that some of the larger tiles along the boundary include white space in the actual image. The screenshot below shows one of the tiles with white space obscuring the mosaic dataset "Footprint" boundaries for the smaller tiles. [ATTACH=CONFIG]19502[/ATTACH] So, from what I understand about how the ZOrder field in the "Footprint" boundary is supposed to work, if I set the value lower in the small tiles and a higher for the larger tiles, the smaller tiles (with photographic information throughout the space) should display on top and the larger tiles should be the background. So, I set ZOrder = -1 for all the smaller tiles and 1 for the larger tiles. That seemed to work, but then I when I built overviews and zoomed back out I see the same gaps, though they have shrunk a bit (compare to the first screenshot). [ATTACH=CONFIG]19503[/ATTACH] I found a post in the forums describing a problem that seemed to be similar to what was happening for me (http://forums.arcgis.com/threads/48759-Mosaic-dataset-overviews-appear-black-have-gaps-in-some-parts?highlight=mosaic+raster+gaps). So, I followed the advice written in by gsumerling and recreated the mosaic again, this time running the Build Footprints tool after loading rasters into tthe mosaic, though that seems redundant since I had "Update Cell Size Ranges" and "Update Boundary" boxes checked in the Load Rasters window (I also had calculate pyramids and statistics checked, and was careful to leave "Update Overviews" unchecked). Then, I ran Build Overviews and did NOT edit the ZOrder field in the table. Got the same result as in the first screenshot. Can anyone see where I'm going wrong in the process, here? ... View more

Is this a bug? When running the Near tool on a feature class (file geodatabase) whose table is joined to another, the Near tool fails (error 999999). Remove the join or export the feature joined feature class to a new feature class or shapefile and the tool works. ... View more

Anyone have this problem when checking in ArcPad data? First off, when I start off using the Get Data For ArcPad tool, no Picture Field is available to set in the Select Picture Options window of the wizard for the feature class in which I want to store the file name. Now, I've created a text attribute column 20 characters long to hold the file name, which is the minimum length needed in order to make the column available to the tool for holding picture file names, according to the instructions I read in the ArcPad help. But even more confusing is that I ran the tool anyway, got the data on my GPS unit, went out and collected data and took pictures, and ArcPad successfully put the file name for each picture in the attribute column for each collected point. I'm just writing this in case it illuminates what follows. The actual problem came when I used the Get Data From ArcPad tool. The first time it worked like a charm. I originally had 4 features in my feature class, but after check in the 2 new features I collected with the GPS were added. Every time I've tried it after that, with different saved versions of the same project, the new data I collected did not get added to the feature class in ArcMap. The Check In Results window Report stated: "The selected layers in C:\blah\GIS-Data_gdb.axf were successfully checked in, but one or more edits were skipped because the geodatabase reported an error. The first error reported is: The row contains a bad value. [Photo]" Now, I know the reason that this error comes up is because there is not sufficient space in the column to hold the length of the data that is being attempted to update it - in this case the [Photo] column. But the column is 20 characters long and the length of the name that ArcPad enters into it is only 14 characters long (Photo_0001.jpg). I've tried recreating the project several times over, changing the name of the column, etc., but the error persists. I'd love to hear any ideas. ... View more