POST
|
If you create one overlapping point layer you can extract te values from each raster with extract values to points ( http://resources.arcgis.com/en/help/main/10.1/index.html#//009z0000002t000000 ). Then for each raster create a field and calculate the value in it. This gives you a point layer with a value from each raster that can be evaluated. Hope this helps.
... View more
04-21-2014
09:47 PM
|
0
|
0
|
3
|
POST
|
Try a Union ( http://resources.arcgis.com/en/help/main/10.1/index.html#//00080000000s000000 ) I think this does what you want. It "merges" the to shapes into one bringing the shapes and attributes together.
... View more
04-17-2014
12:16 AM
|
0
|
0
|
4
|
POST
|
If you have small rasters or large cell size you could convert the rasters to points and extract all values to the point layer. This way you can analyze it more easily. Hope this helps.
... View more
04-17-2014
12:13 AM
|
0
|
0
|
3
|
POST
|
Try changing it into: "OLEADSPC" NOT in ("PLOT_MASTER_LEADING_SP" OR "OLEADSPC","PLOT_MASTER_LEAD_SPEC_")
... View more
04-17-2014
12:03 AM
|
0
|
0
|
6
|
POST
|
Python has standard functions for these kinds of things. Perhaps you could ask the question on that thread, I know the functions are there but am not yet capable of giving you the solution. good luck
... View more
04-16-2014
11:54 PM
|
0
|
0
|
3
|
POST
|
Merging features "across borders" sometimes creates more problems and also gives false extents. Some databases or feature datasets will not accept the data becouse it is "out of bounds" or exceed the "spatial grid index" (see also: http://resources.arcgis.com/en/help/main/10.1/index.html#//01m600000046000000 ) But putting it from UTM to GCS also is not allways the best option, but it will work without problems and is geographicly correct. Why is it necessary to put it in a Feature dataset, do you want to check the topology?
... View more
04-15-2014
05:31 AM
|
0
|
0
|
5
|
POST
|
Hi The feature classes all need to have thesame coördinate system otherwise it will not work. Feature datasets can only store features with thesame coördinate system. So first you will need to project your data ( http://resources.arcgis.com/en/help/main/10.1/index.html#//00170000007m000000 ). Depending how accurate your data needs to be you could use GCS WGS84 which has no zones but is geographical (GCS) in stead of projected (UTM). Otherwise you will have to choose one of the zones and project all data in that so you can use this for the feature dataset (I advise you not to do this). Greets Paul
... View more
04-15-2014
04:01 AM
|
0
|
0
|
5
|
POST
|
Great! These questions are allways interesting and fun if they can be solved. If you would please check the box that it is the answer and Arrow up on it. Thanks!! Greets Paul
... View more
02-09-2014
08:47 PM
|
0
|
0
|
14
|
POST
|
I see I forgot to mention someting. When calculating X and Y you need to calculate the Centoid of the polygon. You will probably do it correctly but this is a critical step. Please let us know if it worked.
... View more
02-05-2014
01:28 AM
|
0
|
0
|
14
|
POST
|
You could use the Edit Vertices tool on the editor toolbar ( http://resources.arcgis.com/en/help/main/10.1/index.html#//01m80000003p000000 ), this then shows all vertices of the feature. With a right click you can select Move to and set the new coördinate. You can also click on the Sketch Properties button (also on the editor toolbar) this creates a window with all of the coördinates of all of the vertices of the feature you want to edit. There you can also change the specific coördinate of a vertex. Hope this helps. Greets Paul
... View more
02-04-2014
09:16 PM
|
0
|
0
|
6
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:23 AM
|