|
POST
|
Thanks, this has helped me work out what the issue was - I wasn't aware that the 'Merge Rule' needs to be set for each Output Field separately, so when I chose 'Mean' all I did was to apply a 'Mean' merge rule to the very first Output Field. I ran the tool again, setting the rule for the 'gridcode' field which holds my raster values, and it worked.
... View more
12-22-2017
03:23 AM
|
0
|
1
|
1360
|
|
POST
|
I have a shapefile with 414508 polygons representing different habitat types. I want to match the values from a 25m x 25m raster file for the same study area to these polygons, using the mean value of all 25m cells that fall within each polygon. I converted my raster file to points and ran the 'Spatial Join' tool with the polygon file as my Target Features and the new point file as Join Features. At first, I only changed the Merge Rule from 'First' to 'Mean' and left the default Match Option (Intersect). This did not give me the output I was after though as the matched values seemed too high, i.e. they didn't seem to reflect the 'mean' of all the values in within the polygon. I then experimented with the Match Option, choosing 'Contains' as well as 'Completely contains' but got the same results each time. During each try, the same point value was used for matching, and it doesn't seem like any merge rule was applied at all from looking at the attribute table (see below). The point whose value was matched to the polygon in the image below in no way represents the mean as the majority of points that fall within it have values <0.2, and only a very small portion of it is covered with points >0.2 What did I do wrong? How come the attribute table shows the value of a single point ('pointid' and 'gridcode') rather than the result of the 'mean' merge rule? Is there perhaps another way of achieving what I want without using the Spatial Join tool? I am using Pro 2.0 but also have Desktop 10.5 installed.
... View more
12-21-2017
07:17 AM
|
0
|
3
|
1506
|
|
POST
|
Thanks - this is the example I tried to follow but wasn't sure how to handle 'Null' values (in a string or numeric field). I think I'm beginning to get a better sense of it. What I would really like to see is a feature class version of the 'Reclassify' tool so users that aren't familiar with Python can easily define 'Start' and 'End' values without using code. Anyway, thanks for the help!
... View more
12-06-2017
02:17 AM
|
0
|
0
|
3224
|
|
POST
|
Thank you, I will try this now! Just out of interest, how would this code change if dealing with numerical values rather than string?
... View more
12-05-2017
08:31 AM
|
0
|
1
|
3224
|
|
POST
|
I have a text field called 'Description' that contains some <Null> values that I wish to update to 'Hedgerows' while keeping all other values the same. Using Calculate Field in Pro, I tried the following: Expression: Reclass (!Description!) Code block def Reclass(Description): if (IsNull) return Hedgerows The expression was successfully verified but I then got the following error message when running the tool: Error 00539: Error running expression: Reclass (u"Buildings") Traceback (most recent call last): File "<expression>", line 1, in <module> File "<string>, line 2, in Reclass Name Error: name 'IsNull' is not defined Failed to execute (CalculateField). Any suggestions? I'm a complete novice when it comes to Python.
... View more
12-05-2017
04:26 AM
|
0
|
5
|
5354
|
|
POST
|
I'm assessing the difference by looking at the raster statistics under 'Properties', which show me that the minimum, maximum, standard deviation etc. are the same. I think the difference in visual display is a bug in Pro 2.0 as this problem does not occur in Desktop 10.5.
... View more
09-14-2017
02:02 AM
|
0
|
1
|
2844
|
|
POST
|
Update: The underlying files are actually identical and displaying accordingly when opened in Desktop 10.5. This problem only occurs in Pro, which is incredibly frustrating as I'm deliberately trying to move away from Desktop but Esri are making it hard to do so.
... View more
09-13-2017
06:42 AM
|
0
|
3
|
2844
|
|
POST
|
Thanks for the reply. Unfortunately, this has made no difference. The input raster is in fact a resampled file itself as I have converted what was originally WGS1984 to OSGB1936 and have resampled the cell size using the 'Resample' tool (Cubic). Could this be a problem?
... View more
09-13-2017
04:07 AM
|
0
|
0
|
2844
|
|
POST
|
I am trying to convert a number of raster datasets saved in a File Geodatabase to ASCII using the Raster to ASCII tool. I have tried this in both ArcGIS Pro 2.0 and ArcCatalog 10.5. For some reason, the resulting ASCII file has a different range of values from the input raster each time. In the example below, the input raster (seen on the left) has values between 6.70958 to 10.7875 while the resulting ASCII file (seen on the right) ranges from 6.70958 to 9.28548. As you can see, the ASCII also looks quite different visually. I have applied the same symbology to both (Stretch, Percent clip) so this shouldn't be what's causing it. What happened to those values? Is there another way of creating an ASCII file that I could try?
... View more
09-11-2017
09:04 AM
|
0
|
6
|
4194
|
|
POST
|
Hello I just ran a model in Pro 2.0 trying to convert 97 Ascii files to raster and then mosaicking them all into one. Something seems to have gone wrong as the resulting file only covers a small part of the total area covered by the 97 individual files. The iterator in my model clearly points to a folder containing 97 files and I'm fairly confident the model was built correctly. To investigate what happened, I want to look at the ModelBuilder documentation window (the one that pops up when you start running the model and documents the process). I stupidly closed this after it finished and am not sure how to recover it. Any advice greatly appreciated.
... View more
08-22-2017
03:11 AM
|
1
|
2
|
1169
|
|
POST
|
Hi everyone, I am trying to georeference a JPEG image in ArcGIS Pro 2.0 by manually entering known X and Y coordinates shown on the image (Eastings and Northings in the British National Grid coordinate system). I have now added 8 control points by choosing 'Add Control Points', clicking on the source layer (i.e. the image I want to georeference), right-clicking on the control point and entering the X and Y values. For some reason, these changes are not having any effect as the image isn't being updated with each point. Rather, I can see lines drawn from each control point on the source image to the location on the target layer (screenshot below). AutoApply is enabled, and I have tried manually updating the image by hitting 'Save' but the image isn't moving. Confusingly, some of the control points are not connected through lines on the map (see blue-coloured points at the bottom left of the image), although they are showing up in the Control Point Table. I have georeferenced images before in ArcMap and have never had any issues so I'm not sure what I'm doing wrong. Have they made any changes in Pro that I'm not aware of? Have I made any glaringly obvious errors? Thanks!
... View more
07-28-2017
03:52 AM
|
0
|
0
|
786
|
|
POST
|
I've managed to do it now using the 'Join Field' tool. I thought I could perhaps do this more elegantly using Python script in 'Calculate Field' but as a complete novice to Python it seems needlessly complicated. Thanks for your help anyway!
... View more
06-20-2017
06:21 AM
|
0
|
0
|
1474
|
|
POST
|
Thanks Dan. I tried to edit the table directly but it won't let me many any changes to the cells. See below - I can highlight the cells but cannot enter any values/text. I might try ArcMap instead of Pro to see whether that makes a difference.
... View more
06-20-2017
05:22 AM
|
0
|
2
|
1474
|
|
POST
|
Hi, I have a raster dataset with cell values from 1 to 21, corresponding to different land cover types. I have added a new text field called 'Habitat' to the attribute table and would like to fill this based on call values, i.e. Value = 1 means Broadleaved woodland, Value = 2 means Coniferous woodland etc. I am using ArcGIS Pro 1.4. At first I simply tried to double-click the cells in the new field and type in the new text manually, as I would with a vector dataset. This didn't work and I am presuming this functionality isn't available for rasters. Next, I turned to the Calculate Field and, after looking at previous threads about this topic, attempted the following (I only used the first two values out of 21 to test the code): def Habitat(Value) if (Value = "1"): Habitat = "Broadleaved woodland" elif (Value = "2") Habitat = "Coniferous woodland" For the expression I used Habitat = (!Value!). Upon verifying this I got the following error message: Where did I go wrong? Is there an easier way of editing a field in a raster attribute table? Thanks!
... View more
06-20-2017
04:24 AM
|
0
|
4
|
1996
|
|
POST
|
Hi everyone I'm working on an ArcGIS Pro project for which I need to create a large number of subsets of the same feature layer. Previously, all newly created layers opened their attribute table 'docked' underneath the map I'm currently working on, which is how I want them to be displayed. The most recent one, however, suddenly brings up the attribute table in a new window next to my maps and layouts at the top. Any idea why this might be, and where I can find the setting to change this? Thank you!
... View more
06-09-2017
03:38 AM
|
0
|
0
|
645
|
| Title | Kudos | Posted |
|---|---|---|
| 3 | 10-20-2025 01:36 AM | |
| 1 | 02-24-2021 10:05 AM | |
| 2 | 07-29-2025 05:41 AM | |
| 1 | 07-28-2025 03:00 AM | |
| 1 | 06-26-2025 04:52 AM |
| Online Status |
Offline
|
| Date Last Visited |
a week ago
|