POST
|
How did you rescale those polygons? There's a hidden Scale editing tool where you can enter specific scale factor. To access this tool click Customize menu -> Customize mode. In commands tab find Scale tool in Editor category. Drag it to some toolbar. Next, in edit session, select polygons, click Scale tool and press F key on a keyboard. This give you an option to enter specific scale factor which in your case is 0.29/0.24 = 1.208333333
... View more
11-19-2012
01:34 AM
|
1
|
0
|
949
|
POST
|
There's no simple property of COUNT for raster values. It can be read from raster attribute table with a search cursor in this way: import arcpy, inRaster = r"C:\test.gdb\myRaster" # Build attribute table if needed #arcpy.BuildRasterAttributeTable_management(inRaster, "OVERWRITE") # Create a search cursor for desired raster VALUE sCur = arcpy.SearchCursor(inRaster, '"VALUE" = 1') for row in sCur: cellCount = row.getValue("COUNT") print cellCount
... View more
11-08-2012
09:32 PM
|
0
|
0
|
687
|
POST
|
I've managed to run this tool sucessfuly (ArcGIS10, Sp4) on small extent with Sampling Distance = CELLSIZE 0.5 (if it doesn't work, try also CELLSIZE 0,5 - it's a matter of regional settings)
... View more
11-08-2012
03:42 AM
|
0
|
0
|
624
|
POST
|
The output of LAS to Multipoint tool is optimized for storing huge volumes of points. LAS files usually consists of hundreds of thousands points. That's why grouping many points in one geometry (multi-points in one row) drasticaly increase display and processing time of such multipoint layer. Lidar multipoint layer is usually used as an input for creating a Terrain dataset. From a terrain dataset you can create DEM rasters or TINs. That was a background - now you question. You can extract each individual point from multipoint layer using Multipart to Singlepart tool from Data Management -> Features toolset and then add XY coordinates. But I'm interested in what for do you need those coordinates? Note: Your multipoint layer if very small so you should not have performance problems but for larger datasets a multipoint feature class in geodatabase is better solution than shapefile.
... View more
11-07-2012
11:01 PM
|
0
|
0
|
220
|
POST
|
Maybe your point layer is not Z-enabled? To represent a point correctly in 3D space in ArcScene its geometry in Shape field should be Point Z. You can declare that point layer store Z values when you create new feature class in GDB (first page on wizard, Geometry Properties - tick 'Coordinates include Z values') Then, when you create a point in ArcScene, it should have elevation automatically stored as Z coordinate value. Note: When creating a line of sight sometimes it's useful to raise a point a bit above building top (to prevent this building from obscuring a view). It can be done specifying Layer offset in Base Heights tab in observer layer properties.
... View more
11-07-2012
09:58 PM
|
0
|
0
|
318
|
POST
|
Is it possible maybe to convert raster to polygon and then with something else calculate intersection of two polygons with decimals, I mean real km2 values? Yes, it's possible, but it won't give you more accurate result. Your result will be more precise but still will be as accurate as your least accurate data set. In other words, your result with decimals won't be closer to reality than result without decimals.
... View more
11-07-2012
02:27 AM
|
0
|
0
|
1451
|
POST
|
You can try using raster analysis mask: - In IDW tool dialog window click Environments - In Raster Analysis section select your polygon layer as Mask
... View more
11-07-2012
12:54 AM
|
0
|
0
|
1622
|
POST
|
Hi! Thematic Raster Summary Tool (Hawth's Analysis Tools for ArcGIS) ... this tool only counts cells of each class inside polygon and fills attribute table with integer numbers. Your raster cell area is 1 km2, so the cell count is already an area in square kilometers. You will not get better precision that 1 km2 as raster cells are not clipped like polygons. Zonal tools take only whole cell and assign it to one of adjoining zones.
... View more
11-07-2012
12:46 AM
|
0
|
0
|
1451
|
POST
|
From context help (click "?" besides "x", then click on parameter): Point features: No duplicate label options are available. One label is always placed per feature part. Line features: When two or more contiguous features have the same value for the label string, only one label will be placed. This prevents unnecessary duplication of the same label. For example, in a layer representing the rivers of South America, the Amazon river may be represented by a number of contiguous line features, with each section of the river between each tributary being a separate feature. When this option is selected, the label "Amazon" will be appear just once along the entire river, even though it is made up of several features. This is the default for line features. Polygon features: When two or more features have the same value for the label string, only one label will be placed. The features need not be contiguous.
... View more
11-06-2012
10:49 PM
|
0
|
0
|
872
|
POST
|
Maybe you can just rotate your index features to align with your data? You can do it in Edit session using Rotate tool (pressing A key allows to enter specific rotation angle).
... View more
11-06-2012
09:41 PM
|
0
|
0
|
1385
|
POST
|
worked fine thx! I just used as type field my "capture date" and in fact, that the format is sometimes dd.mm.yy and sometimes with dd.mm.yy + time I got seperated values. Can i drop the time before in my attribute column? To drop the time: create new column and use this simple expression in Field Calculator with Python parser: !Erfassungsdatum![:10] (which takes only first 10 characters) By the way, if you've found my previous answer helpful, mark my post as answered using voting tools:
... View more
11-05-2012
11:03 PM
|
0
|
0
|
1578
|
POST
|
Firstly, what for do you need 2 cm spaced points when your data resolution in 1 meter. You wont get higher accuracy using such a spacing. General workflow for lidar data is: - convert LAS files to multipoint in geodatabase feature dataset (- if you have 10.1 you can create LAS dataset directly from LAS file) - create Terrain dataset (for example refer to Creating and using terrain dataset tutorial exercise) - convert terrain dataset to raster with desired resolution and do something with raster (you don't need to convert it back to points and interpolate)
... View more
11-05-2012
10:41 PM
|
0
|
0
|
711
|
POST
|
You can only add new field to raster of integer type (not floating point). It can be done in the same way as for feature class - in attribute table menu. To check what type is your raster in Catalog window open raster properties and look for Pixel Type value. You can convert floating point raster to integer using Int tool from spatial analyst toolset. But this operation truncates decimal part of raster values.
... View more
11-05-2012
09:42 PM
|
0
|
0
|
438
|
POST
|
Try this two-steps approach: 1. Select all blue/black polygons B which are in large green polygon A using Select By Location from Selection menu. 2. Use Summary Statistics tool (Analysis->Statistics->Summary Statistics) to calculate summary area for each type of polygon B with settings: - Statistics Field: Shape_Area - Statistics Type: SUM - Case field: type field - the field based on which you differentiate polygons color.
... View more
11-05-2012
09:00 PM
|
0
|
0
|
1578
|
POST
|
I guess you want to create continous surface raster. It can be done using one of Interpolation methods available in Spatial Analyst extension. An interpolation will produce best results in areas where there's many points and/or point are evenly distributed. That's why an interpolation result from your data for south part of Gulf of Mexico may not be accurate.
... View more
11-05-2012
02:35 AM
|
0
|
0
|
273
|
Title | Kudos | Posted |
---|---|---|
1 | 06-03-2012 11:51 PM | |
1 | 10-26-2012 01:13 AM | |
1 | 10-10-2012 02:57 AM | |
2 | 04-20-2012 12:38 AM | |
1 | 11-19-2012 01:34 AM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:23 AM
|