Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Cancel
- Home
- :
- About JeffreySwain
JeffreySwain
Esri Regular Contributor
since
07-01-2014
05-21-2026
809
Posts created
10
Kudos given
28
Solutions
68
Kudos received
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
My Ideas
(2 Idea Submissions)Latest Contributions by JeffreySwain
|
POST
|
Is the point cloud covering nodata values or do the coordinate systems match? Could there be points where no raster data could possibly be?
... View more
04-12-2013
04:10 AM
|
0
|
0
|
833
|
|
POST
|
Try any of the volumetric solutions that 3d Analyst offers, from Cut/Fill, Surface Volume or even Polygon Volume.
... View more
04-12-2013
03:34 AM
|
0
|
0
|
608
|
|
POST
|
You could try Raster Painting under ArcScan. That can let you change the values of specific cells manually. For more automated processing, perhaps the Reclassify or Con Tool will be better.
... View more
04-05-2013
04:28 AM
|
0
|
0
|
1287
|
|
POST
|
Have you upgraded the geodatabase? Or considered trying to create a new geodatabase and then copy the mosaic dataset to that geodatabase? After copying you should be fine to create the overviews. If you do not want overviews you can always increase the value in the MaxPS to allow them to be seen instead of the overviews.
... View more
04-04-2013
01:06 PM
|
0
|
0
|
645
|
|
POST
|
I wonder after your extract if the statistics were present on the raster or if there was a stretch that could be applied. Depending on your settings in your mxd, you might need to generate the statistics and apply the stretch.
... View more
04-03-2013
03:43 AM
|
0
|
0
|
3407
|
|
POST
|
So Extract by Mask will not change the rows and columns and the Clip tool adds overlap data? Is that a correct explanation? What kind of polygon are you using? What is the cell size of the original raster and the clipped raster? Is this LGN6 data corrupt? Are the cells rectangular by a little bit? It sounds as if the original is rectangular and then in the clipping process each tool tries to account for this. The Extract by Mask seems to make them square. The other question is when you zoom to the extent of the clipping polygon does it zoom in or does it zoom to the full extent? I think the that snap raster and the processing extent should help, but I am more interested in the original data. For the true comparison as well, I would convert the clipping polygon to a raster to see what the clipping area would be. Perhaps that will also yield a clue as to what is happening.
... View more
04-03-2013
03:40 AM
|
0
|
0
|
3752
|
|
POST
|
The fix is in for the next update 10.2 per the published bug information.
... View more
04-03-2013
03:30 AM
|
0
|
0
|
4016
|
|
POST
|
I would consider using the polygon that you used to clip as a soft clip rather than how you are clipping the breaklines. It appears that if your breaklines are losing their elevation is that either you are making them 2d. The soft clip will restrict what will be considered and not use the z of the clipping polygon.
... View more
04-02-2013
04:38 AM
|
0
|
0
|
1868
|
|
POST
|
According to the mosaic dataset function, it should be used on raw data and have the proper metadata. The input for this function is the raster. There are no other parameters for this function because all the information is derived from the input's properties and key metadata (bands, data type, and sensor name). Only imagery from the Landsat MSS, Landsat TM, Landsat ETM+, IKONOS, and QuickBird sensors are supported. If it does not, then you will need to acquire the raw data. You should be able to apply it to a raster with the fx on the Image Analysis Window or when the data is added to a mosaic dataset
... View more
03-29-2013
06:43 AM
|
0
|
0
|
2546
|
|
POST
|
The morphology of the counties is probably causing the issue. Depending on your data, that is what I would look into. Also per the help documentation, If the zone input is a feature dataset, a vector-to-raster conversion will be internally applied to it. To ensure that the results of the conversion will align properly with the value raster, it is recommended that you check that the extent and snap raster are set appropriately in the environment settings and the raster settings. Since the internal raster must have an attribute table, an error will occur if one was not created in the conversion. If this happens, convert your feature dataset directly with Feature To Raster, Polygon To Raster, Point To Raster, or Polyline To Raster. Generate an attribute table for it as described in the previous tip and use the resulting raster as your Zone input. Also depends on how much NoData is covered by your zones.
... View more
03-29-2013
06:30 AM
|
0
|
0
|
4904
|
|
POST
|
ArcMap does support .DAT files in a certain format. After reading the documentation on your data, I am not sure if that is the format that is supported. With questions like this, I always look into this document. Envi .dat , AIRSAR .dat files, and USGS .dat files are supported per the document. I am not sure if the UK information follows those specifications. Once it is added as a raster in ArcMap, you can pursue either way to analyze the data.
... View more
03-29-2013
04:46 AM
|
0
|
0
|
1580
|
|
POST
|
When you converted it, did you use the snap raster environment setting to align the pixels? Or make it match the extent of the raster via the Output Extent? From what it sounds like, pixel registration is causing issues. Since you are choosing to match the cell size, I would complete it and then use the snap raster and processing extent.
... View more
03-27-2013
01:03 PM
|
0
|
0
|
1726
|
|
POST
|
Did you ever convert your data to a raster and look at where it put the pixels? I would process that and then look at the problematic errors. It should explain what the tool is doing when considering the zones.
... View more
03-26-2013
01:26 PM
|
0
|
0
|
1726
|
|
POST
|
Have you considered using the mosaic dataset and then applying the Gray Scale Function? Once you have the grayscale, you can then export it.
... View more
03-26-2013
01:15 PM
|
0
|
0
|
1825
|
|
BLOG
|
 Full Extent of the LAS Dataset with the Tools greyed out. The ArcGIS 10.1 help on interactive toolbar tools for LAS datasets identifies one such step:
What does 'full resolution' mean? According to the ArcGIS help on the topic, the definition is, "the scale threshold used to control when the LAS dataset will render itself without thinning, using 100% of the LAS points." So once you have modified the settings or zoomed in far enough to see 100% of the LAS points, you can use all the tools in the 3D Analyst toolbar, right? Almost.  The final step is to choose the Elevation option from the Display As TIN options on the LAS dataset. Once you make that selection, you should see the LAS dataset appear in the drop-down for the 3D Analyst toolbar and the tools should become active.  Now you can create the profile graph or generate a 3d feature just as you would with a normally recognized surface in ArcMap. References Additional information on Lidar and LAS files: Additional blogs on LAS dataset:Jeff S. – Senior Support Analyst |