|
POST
|
It's disappointing the tool doesn't transfer attributes, but these can be restored with a table join afterwards if 'identify and store polygon neighbour information' is unchecked. yes, 2 overlapping lines should be created if the checkbox is unticked. You can approach it wither way by retaining the neighbour information, but I think this is a more understandable workflow. Spatial Join - Join the lines to themselves and each will get the height attributes of the intersecting line. Afterwards field calculate a new field showing the values of both heights e.g !HOEHE! + ", " + "!HOEHE_1" then run a new field calculation to return the highest value from the lowest range. export as new features without the join field and delete identical.
... View more
06-12-2020
01:23 PM
|
0
|
1
|
4004
|
|
POST
|
Hi all, Say I have multiple features from the same workspace in my TOC (lets say the features are from the same .sde or FGDB and not separated by feature datasets etc, just sat in the same root). I say .sde or FGDB as I would like to be elucidated on both if possible! I right click -> edit features -> start editing , although this is the same as using the edit toolbar and editing a workspace. Say I have a large number of features within my TOC belonging to that workspace, which have now become editable - I'm guessing that's not good for performance? Even if I deselect their visibility I could still open their attribute tables and edit them etc. Am I missing something big, or must I completely remove the other workspace features from the TOC to improve performance when editing a feature from that workspace?
... View more
06-12-2020
12:38 PM
|
0
|
5
|
1475
|
|
POST
|
I would go with George Thompson but take it a small step further and spatially join those lines and then use a field calculation to take the minimum value of the two fields and then the value after the dash. Also ensure the code doesn't hiccup on a line with no matching join, such as the outer line of the enclosing polygon. It just takes a bit of python index slicing and .split() method etc. Feature 1 - Join Field - 0-10m, 10-20m -->10m
... View more
06-12-2020
12:24 PM
|
1
|
0
|
4004
|
|
POST
|
encase it all in double quotes as your single quotes will have confused 'lowparcelid' in the string
... View more
06-12-2020
08:20 AM
|
0
|
0
|
5597
|
|
POST
|
can you screenshot the input and error on field calculator? are you using the python interpreter when using ! !
... View more
06-12-2020
07:24 AM
|
0
|
2
|
5597
|
|
POST
|
06-12-2020
07:12 AM
|
0
|
0
|
1405
|
|
POST
|
What is it saying? something like GeoprocessingObject? print(desc.XMin, desc.XMax...
... View more
06-12-2020
04:01 AM
|
0
|
2
|
1405
|
|
POST
|
Unfortunately there's no best answer. Jugging by the original question if would suggest Natural Neighbour as it will give you a fairly linear change in elevation between the points, although it can produce quite unnatural surfaces because of the thiessen polygon methodology. How Natural Neighbor works—Help | ArcGIS for Desktop However it's up to your judgement of the original data points and the terrain to best decide upon the interpolation model.
... View more
06-10-2020
04:19 AM
|
2
|
1
|
3110
|
|
POST
|
You might be best creating an interpolated elevation surface then extracting the cell values coincident with the points
... View more
06-09-2020
04:58 AM
|
2
|
3
|
3110
|
|
POST
|
Are you writing to a feature dataset? I guess that would ignore any environments to preserve topology etc?
... View more
06-08-2020
01:59 PM
|
0
|
1
|
3067
|
|
POST
|
I would say that "0.003280839895013 Foot" etc. is being passed as an incorrect variable which is ignored by the environment. "0.003280839895013 Feet" should be passed?
... View more
06-08-2020
01:49 PM
|
0
|
0
|
3067
|
|
POST
|
You've passed the field in as a list, possibly either remove the []'s or use row[0] = But I don't think that's actually causing an issue from what you say, what's your field length on building number? seems like values over 2 are too long?
... View more
06-08-2020
01:09 PM
|
1
|
1
|
5287
|
|
POST
|
can you humour me and show the print/add message results please
... View more
06-08-2020
12:50 PM
|
0
|
3
|
3067
|
|
POST
|
What part do you have a problem with (I can't help with any GDAL stuff unfortunately). I would however: 1.Create a python list or dictionary of your Cities as a Key, and the WGS84 Lat Long as a value. 2. Run these through GDAL translate to get the projected coordinates 3. Do some simple maths to get your UL/BR coordinates for each city 30km square. MyDictionary = {"Lublin" : [290004 370001, 320004 34001], "Frampol" : [ ... workspace = r"C:\\.." Input = "Lublin" #create output path outpath = Input+".tif" outpath = os.path.join(workspace, outpath) GDAL_function(MyDictionary[Input], outpath)
... View more
06-07-2020
12:05 PM
|
0
|
0
|
2412
|
|
POST
|
I know it makes little sense but it may be an arcpy quirk, have you tried something like: MTolerance = sr_object.MTolerance arcpy.env.MTolerance = MTolerance … arcpy.FeatureClassToFeatureClass_conversion()
... View more
06-07-2020
11:48 AM
|
0
|
5
|
3067
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 06-13-2025 01:08 PM | |
| 1 | 09-25-2025 03:19 PM | |
| 1 | 09-24-2025 02:35 PM | |
| 1 | 09-17-2025 02:42 PM | |
| 1 | 09-10-2025 02:35 PM |
| Online Status |
Offline
|
| Date Last Visited |
2 weeks ago
|