|
POST
|
I would recommend of the zonal statistics or zonal statistics as a table. They should create the desired output. With the Zonal Statistics as a Table, you will have to join the table back to the original shapefile.
... View more
07-26-2012
10:31 AM
|
0
|
0
|
637
|
|
POST
|
You might consider the Reclassify tool in order to determine the areas. Since you have the quantile classification already, you could create a new raster into the 5 classes and then the area would be easy to calculate.
... View more
07-24-2012
07:16 AM
|
0
|
0
|
693
|
|
POST
|
Always be sure that the point file being used is above the DEM being input. I have seen many situations where the point is below the input DEM and an error will prompt. Also I cannot see your full path, but it appears that you are exporting to the Q drive. Does the same behavior happen when you output locally?
... View more
07-20-2012
03:37 AM
|
0
|
0
|
1971
|
|
POST
|
What were the resampling methods used to display each raster? If the cell sizes are the same, then there must be something else creating that look. I would consider the resampling method being used to display the raster under the layer properties. Also if the issue is only in the pyramids, consider altering the resampling method used to create the pyramids. Perhaps switching from Nearest Neighbor to Bilinear will make the displays match.
... View more
07-17-2012
03:16 AM
|
0
|
0
|
8087
|
|
POST
|
Without seeing your lidar data, it is difficult to know, but perhaps you might need to consider whether the lidar data was obtained or generated for the buildings. Perhaps the values created reflect the height above the ground rather than the true elevation. In that case, if you added the building values to ground elevation you would have a building with a height of 427 or in your case, 214 meters above the ground. I have not seen much lidar like this, but perhaps you should consider it.
... View more
07-17-2012
03:10 AM
|
0
|
0
|
966
|
|
POST
|
You can export the attribute table to a .dbf, while opening the attribute table of the original raster. If that is your desire, then that should not be too bad. The NetCDF format is designed to provide a n dimensional look at the data. So if you had landcover pixels for multiple years then the NetCDF may be the format. That way the lat/lon and multiple values could be listed by date and you could spin through the raster by selecting different values. I am not sure if the NetCDF will allow you to access the original attribute table of the landcover data in the manner you are looking for. For instance, normal NetCDF data is water temperatures that are collected over a time period and usually a depth. So then you can select a particular depth and then scroll through each time period. If you only have a Landcover dataset for one year, I am not sure if that will get what you want, but if you simply want to see the information in the landcover raster in a text format there are other ways. From my limited understanding of Matlab, a text file should work and it does not have to be a NetCDF.
... View more
07-12-2012
05:19 AM
|
0
|
0
|
4779
|
|
POST
|
For specific help then if those suggestions do not work, then I recommend creating a Support Incident to look over your workflow. Something is still not correct, because while the skewing should happen without the transformation, you should see some effect from either projecting the raster or using the proper transformation.
... View more
07-12-2012
05:08 AM
|
0
|
0
|
2475
|
|
POST
|
What transformation are you using in the map document? Have you considered projecting the data into Illinois Harn? I would recommend either of those options, depending on your workflow. Setting the correct transformation in the map document or using the correct transformation to project the data should fix the "skew." In this blog, it discusses how to choose the desired transformation.
... View more
07-11-2012
10:51 AM
|
0
|
0
|
2475
|
|
POST
|
The NETCdf is going to be like an ascii file with the data in a matrix of sorts, so the normal size convention will not apply. I am not as concerned about the size, but if the variables being selected during the create process are making it read as invalid, then that is the problem. You say the raster has an attribute table, do the values in the field names correspond to normal NETCdf variables or are they unique. I would keep the lat/lon as the same, unless that is actually corrupted. The NetCDF layer has certain variables it is usually expecting. I am not sure what the variable names are you are specifying or if you are trying to push the New NetCDF into another coordinate system. I would consider what coordinate system you are using if you are defining it or the field names as whether they can be used as valid fields. What value are you specifying for the value of the NetCdf?
... View more
07-11-2012
03:14 AM
|
1
|
0
|
4779
|
|
POST
|
If it imported correctly and is a simple color, then you can apply a standard deviation stretch. You will have to generate statistics on the ascii file in order for the stretch to be applied. That is if the data made it in successfully after following the steps that Eric suggested.
... View more
07-11-2012
03:07 AM
|
0
|
0
|
2177
|
|
POST
|
If you mxd has a coordinate system prior to your export and then you manually modify it in ArcCatalog, you are probably creating an improperly defined raster. It may be causing the problem that your original map is in WGS 1984, which has the extents in degrees and when you 'define' it in ArcCatalog as NAD 83 you are creating the problem, since the name of the projection changed, but the data was not projected. I would recommend altering the mxd's coordinate system to the one you want and then retry, skipping the step in ArcCatalog. That should allow the exported map to appear in your mobile device.
... View more
07-10-2012
03:58 AM
|
0
|
0
|
762
|
|
POST
|
Converting a raster to a NetCDF, would require a raster attribute table to create the different dimensions. NetCDFs are N dimensional and other than the lat, lon, and value for each raster. Also consider your original raster, the converted NetCDF will only be visible with the Make NetCDF Raster layer and the tool should recognize the variables set. The output from the NetCDF should be a .nc file, which will be rather small in size compared to a raster.
... View more
07-10-2012
03:51 AM
|
0
|
0
|
4779
|
|
POST
|
You can harvest the Building footprints with the Multipatch Footprint tool. This tool also records the Z Min/Max so you should have an idea about the rooftop, provided the top is not too irregular. Otherwise you could try burning the buildings into a Raster DEM with this from the resource center.
... View more
06-29-2012
03:12 AM
|
0
|
0
|
865
|
|
POST
|
Per the help, you should be using a class break table. On this page, there is an example of how the table should look.
... View more
06-28-2012
03:26 AM
|
0
|
0
|
838
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 04-20-2026 09:09 AM | |
| 1 | 10-26-2023 10:44 AM | |
| 2 | 02-14-2024 08:29 AM | |
| 1 | 11-15-2022 06:57 AM | |
| 1 | 12-08-2023 09:13 AM |
| Online Status |
Offline
|
| Date Last Visited |
3 weeks ago
|