POST
|
My organisation has a lot of published arcgis online services. That makes it very hard to look for the exact one I want to overwrite, and it is not possible to sort the elements in this window. It would be nice to be able to sort, or search, or apply a filter.
... View more
03-16-2016
01:43 AM
|
0
|
2
|
1928
|
POST
|
I can't get my ArcPy script to delete a terrain. If it exists, it should be deleted. However it throws an ERROR 000317: {path} cannot be deleted My script is a lot longer than this, but this is what it boils down to. fds is a feature dataset in a file geodatabase. The feature dataset contains a terrain with 2 associated feature classes: - a points feature class used as masspoints - a polygon feature class used as boundary/softclip import os import arcpy fds = r'D:\Dumfries & Borders.gdb\DEM' arcpy.env.workspace = fds l = arcpy.ListDatasets() for d in l: if arcpy.Exists(os.path.join(fds, d)): arcpy.Delete_management(os.path.join(fds, d)) Earlier on I tried to have the script delete the whole feature dataset at once. Didn't work either. I then decided to delete the dadasets in it one by one. The ListDatasets() lists only one: the terrain, which sparks the error mentioned above. It is possible to delete the terrain or the feature dataset by hand in ArcCatalog, or using the Python window in ArcCatalog. However, even after closing all other programs (to preclude any locks from obstructing) except my Python interpreter (PyCharm) it still doesn't work. So, any ideas? edit follow-up: removing the spaces and & from the gdb's name does not help, as ListDatasets() won't list anything now anymore. Also scriptwise trying to delete the feature dataset now throws an ERROR 000732: Input Data Element: Dataset {path} does not exist or is not supported. (sorry no idea if this is the right place to post, couldn't find any esri/arcgis forum at all for half an hour)
... View more
08-29-2014
07:16 AM
|
0
|
0
|
720
|
POST
|
A feature class is a dataset with geometry stored for each record. The data you want to copy/export is a table which has no geometry so it can't be stored as a feature class. Why do you want to export the table to a feature class and not just to a table?
... View more
10-01-2013
03:26 AM
|
1
|
0
|
515
|
POST
|
...huge non-existing polygon around... I don't exactly understand what you mean, though it might be related to, or be the same as, the problem described above. Could you please post a screenshot or 2 to illustrate what exactly you want to do and what happens? EDIT: I just found it's now officially a bug, reference number NIM091033, which can be found here: http://support.esri.com/en/bugs/nimbus/TklNMDkxMDMz There's not much info there though.
... View more
09-17-2013
06:49 AM
|
0
|
0
|
531
|
POST
|
I've had the same before. I've been looking for ways of automating this, but Python isn't (yet?) able to access the symbology of arcmap layers, and can't be used to save a layer's symbology to a .style file as far as I know.
... View more
07-15-2013
06:08 AM
|
0
|
0
|
635
|
POST
|
I hadn't even thought of accessing the geometry object, focussed as I was with accessing the array. This will work nicely, thanks both!
... View more
07-02-2013
01:02 AM
|
0
|
0
|
311
|
POST
|
To my surprise, it is impossible to get the last element of an array from a polyline (which is a arcpy.arcobjects.arcobjects.Array, so not a normal Python array for which it would definitely work!). my_array[-1] throws this error: Runtime error <type 'exceptions.RuntimeError'>: Array: Error in getting object from array EDIT: OK a rather stupid workaround I thought of myself: my_array.getObject(len(my_array)-1) gives: <Point (280349.568, 311663.817, #, 162.393)> I still wonder: why is it not possible to just use my_array[-1]
... View more
07-01-2013
08:40 AM
|
0
|
3
|
687
|
POST
|
I have had the same problem, both in the office and at a ESRI python course on ESRI PCs. It seems to be an issue with compatibility between pywin and arcpy. I have since switched to pyscripter and haven't switched back.
... View more
05-03-2013
03:23 AM
|
0
|
0
|
1532
|
POST
|
I had the same problem. Finally I could identify the/one reason. I had one big polygon around the area to be digitized (here: the watershed boundary). Inside I wanted to digitize a hydro-geological map and use the watershed boundary as outer boundary applying the "auto complete polygon" tool. This did not work, neither completing polygons to the outer boundary nor to any other polygon. After I deleted the outer boundary from the attribute table, the auto complete polygon tool worked fine for completing adjacent polygons. I guess from your story that the "outer boundary" is a polygon covering you whole watershed. This will not work with auto-complete as you can't use it to build polygons on top of each other.
... View more
05-03-2013
03:10 AM
|
0
|
0
|
2099
|
POST
|
Just to let you guys know: I've submitted the bug through ESRI UK and they're taking it to ESRI Inc.
... View more
04-19-2013
12:19 AM
|
0
|
0
|
2099
|
POST
|
@rborchert Both F2 and double click yield the same result, also classic snapping does not help. @tiffanypuett No the features are not in a topology. The nodes suggestion might be a correct one, as smaller polygons (which have less nodes), do get constructed. Tracing the whole polygon does indeed construct it. I did not have problems with some polygons with a lot of vertices however. I'd rather not edit the registry, as my admin won't like it, and because I think it should work normal. Some fiddling around and what I found out is that the extent of the dataframe does matter after all as well. In situation 1 I am unable to construct polygons using autocomplete at lines 2, 3 and 4. When I move the dataframe view to situation 2, all construction lines prove no problem at all. Even when I start drawing along line 3, move the data frame to situation 2, then finish, it works. Both, thanks for your reply 🙂 I think this should be reported as a bug, which I will do, and now I have quite some info to back it up.
... View more
04-09-2013
01:11 AM
|
0
|
0
|
2099
|
POST
|
I am digitising a map in ArcMap 10.0 SP 2 with a few hundred polygons. I use auto complete polygons to avoid drawing all the lines twice. I use it using both straight segment and trace (along another layer) to draw the lines. Most polygons end up right, but some aren't created when I finish drawing. Also when trying again and making sure to go from existing polygons' vertices or crossing polygons' boundaries the polygon won't draw. A workaround I found is drawing the polygon in parts. But still, one part may draw and the other may not. I then draw even smaller parts and smaller parts until it works. Eventually I fill the polygon with smaller parts (sometimes 2, sometimes 20) and merge them, but it is costing me a lot of time circumventing around unwanted and strange ArcMap behaviour. I looked up various other posts and errors about auto-complete. The main one if found was about the polygon drawn not being complete visible, but I tried zooming out until I saw the polygon drawn and all the adjacent polygons in full and it still wouldn't draw. Also some polygons will draw regardless of zoomlevel. Anyone encounter this before and found a (better) way to deal with it?
... View more
04-05-2013
06:46 AM
|
0
|
13
|
10653
|
POST
|
Sorry to dig up an old post, but I'm experiencing a similar problem and could not solve it following the solution posted. I'm in Arcmap 10 editing a featureclass in a 9.3 pgdb. Because the fc contains many points that I don't want to see while editing, I applied a definition query on the date, excluding all points older than July 24th 2012: [datum] > #07-23-2012 00:00:00# No points do yet exist with date value 24-07-2012. I then made a template with some attributes filled by default, some not and a default date (field "datum") of 24-7-2012. This results in my template not showing in the template list. Changing the definition query to another field, in which another default value is included does show the template, but not the query on the date field. Is it possible that this has something to do with date syntax? The query writes the date as #mm-dd-yyyy hh:mm:ss#. Entering exactly the same date (07-24-2012 00:00:00 except the hashes, as these aren't accepted) into the feature template date field value doesn't work, neither does 07-24-2012, 24-07-2012 or any other syntax, with or without time. More shockingly, also when setting the query to show only a date that is already present in the attribute table, and applying the same date to the feature template default date value, no feature template shows. I have no other def query on this fc, no page definition, symbology is single symbol and I can see points when I change the def query to show values that are already present. So I guess it does not have anything to do with visibility, just the date syntax. Please help me out before I have to resort to classic editing 🙂
... View more
07-25-2012
02:07 AM
|
0
|
0
|
696
|
POST
|
Actually, that isn't necessary with the TableToDBASE tool, as the output table becomes the same name as the input table. However, I now realize that the input table names may have a name which is too long for a dbf table, which might be the cause of the error. When looking for abilities to specify the output table's name, I found another tool (TableToTable) with which I am able to copy a GDB table to dbf format as well, without errors, and while specifying the table name for each export. So, still a little strange but I found a workaround. Thanks for your help! 🙂
... View more
02-14-2012
04:36 AM
|
0
|
0
|
278
|
POST
|
Thanks for the reply, but no that doesn't work, as both produce exactly the same list of values for rd.
... View more
02-14-2012
03:56 AM
|
0
|
0
|
278
|
Title | Kudos | Posted |
---|---|---|
1 | 10-01-2013 03:26 AM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:24 AM
|