|
POST
|
If you are using a layer name, like MG_linhas_transmissao, as input, that layer has to be saved in a project so that the external scheduling system can locate and know the data to use. Is your project with that layer name saved? Can you try to use the full path to the feature service (URL) instead of the layer name and see if that resolves the problem?
... View more
05-19-2020
12:40 AM
|
2
|
0
|
1430
|
|
POST
|
Hello Pace Farbstein Joshua Bixby Can you describe what version you are seeing the error 999999 with this calculate field case? A few releases ago we added code to catch this NoneType error and raise a warning. If you are still seeing the issue in 2.5 I would love to better understand your data and repro case. Thanks Error as of 2.5 that results from the replace() Nonetype exception:
... View more
05-18-2020
04:34 PM
|
0
|
2
|
3122
|
|
POST
|
Instead of trying to figure out how to construct the path with all the \ which are Python escape characters, use the very handy os function, os.path.join(): os.path.join(r"\\DPWTECHENG\Plat", !plat_book! + "_" + !plat_page! + ".tif")
... View more
05-02-2020
12:58 AM
|
1
|
0
|
394
|
|
POST
|
Thank you for this post Scott Drzyzga. This problem was brought to the development team a few weeks ago and has been fixed in ArcGIS Pro 2.6 (it will be in the early adopter snapshot of ArcGIS Pro 2.6, or the public beta available in a few months if you would want to participate). For the 2.5.x release you will need to perform the additional step you explained with the Project (management) tool.
... View more
04-27-2020
10:17 AM
|
1
|
0
|
4497
|
|
POST
|
Hi Paul Cote, We will investigate this issue. Thanks for providing your project. We will let you know any information soon. Drew
... View more
04-24-2020
05:08 PM
|
1
|
0
|
1607
|
|
POST
|
Husham Mohamed please try to use the full url of the feature service when scheduling, instead of a layer name. It may be that the application cannot hand over credentials for the layer to the schedule process, and we may be able to work around this by using the full url rather than the layer name. All you need to do, instead of using the layer in the open tool dialog for your script tool prior to clicking Schedule, replace the layer name with the full feature server layer path.
... View more
04-15-2020
10:35 PM
|
0
|
1
|
2175
|
|
POST
|
You do not need to use arcpy mp or ApplySymbology to symbolize an output dataset of a script tool. There are three approaches: 1. Open the script tool properties, go to the Parameters page, find the output feature class parameter, scroll right to the Symbology column click in the cell and then browse to your layer file. This is the easiest for always symbolizing the output the same way. 2. If you need to symbolize differently depending on the output shape type or some other factors you may want to write code to symbolize the output. You have access to a parameter's same Symbology property set through the UI above available in tool validation. See here: Setting output symbology in scripts—Geoprocessing and Python | Documentation 3. There is a new arcpy function, arcpy.SetParameterSymbology also exactly for this purpose. This allows you to keep the Symbology logic in your source code instead of validation or the tool properties. Arcpy mp is for mapping workflow automation not GP output symbolization. These other methods give you a ton of options for performing the latter.
... View more
04-06-2020
10:32 PM
|
4
|
3
|
11763
|
|
POST
|
These other browsers will have no impact on Pro, which is hardwired through it's WPF architecture to use Internet Explorer only. IE 11 or above is required. Check the other system requirements here https://pro.arcgis.com/en/pro-app/get-started/arcgis-pro-system-requirements.htm And use the Can I Run It? link to analyze your system. Can You Run It?
... View more
03-27-2020
07:57 AM
|
0
|
3
|
2954
|
|
POST
|
I would guess it is internet explorer that is out of date (yeah might be OS too). IE-based browser is embedded in several places in the app, including this initial sign in screen for your home use ArcGIS Online licensed account. The javascript errors Dan Patterson mentions are old ArcMap errors that occurred when opening a geoprocessing tool, as in ArcMap days all tool dialogs were html forms.
... View more
03-27-2020
01:01 AM
|
0
|
9
|
2954
|
|
POST
|
To me, this looks like you probably got an error the first time you started the app while it was creating the geoprocessing cache. The causes for this are often that the Python environment you are using needs to be recloned or just switch back to the default environment and restart the application. When the cache cannot be built, all of the tools that run in Desktop mode (on your local system) will not show up in the GP pane. Only the tools that run remotely in the cloud or in your connected portal will show up, evidenced by all those hammers with cloud icons in your search results.
... View more
03-25-2020
08:32 PM
|
1
|
0
|
1451
|
|
POST
|
Peter MacKenzie did you set the environment in the Python window via arcpy.env.maintainAttachments = False, and then run the tool through the Geoprocessing pane UI? Once the project environments are established, changing the arcpy.env does not impact the environment settings for your project or the tools run in the Geoprocessing pane UI. You can think about it as a one way street - the environments set in the project are automatically derived into arcpy.env, but changes in arcpy.env don't flow up to the project environments. This could be a reason why the tool is stuck at 100% for a long time - the maintain attachments setting never got disabled for tools run in the Geoprocessing pane UI. Transferring attachments is a post process of creating new relationship classes and transferring potentially large amounts of binary information in blob fields into a new table in the geodatabase. The progress bar accounts for the feature transfer, but not for the attachment transfer which is a much less deterministic process, as each attachment can be a different size and require more or less processing time. Dan Patterson had a hunch about that output named g.gdb\_1 -- the geodatabase does allow this name, and I could successfully run CopyFeatures with an output named _1. Russell Brennan's suggestion about Fiddler would help to debug if queries are still being made to the service or if things are stuck on the client side for a long period of time. Working with Esri Tech Support would help to do some of this troubleshooting for you.
... View more
03-25-2020
08:11 PM
|
3
|
2
|
20284
|
|
POST
|
It likely depends on the processing that the tool is doing, your inputs and outputs, number of fields, if you've asked the tool to transfer domains and subtypes, if an expression is being applied, etc. (this tool can do a lot). I ran the most vanilla Table to Table I could find, moving 1million records from a feature class to a file gdb table, and the progress bar is quite smooth. Based on your images, the progress bar is definitely not ideal in your case, it would be great if you could work with Esri Tech Support for them to understand your case and get it to development for improvement.
... View more
03-25-2020
08:00 PM
|
2
|
1
|
4603
|
|
POST
|
Specifically, I imagine, the Processing Extent (or potentially the raster analysis mask for raster tools)? I just tested Calculate Geometry, and it isn't impacted by the extent (and is documented as such), though many tools will be so your comment is definitely valid.
... View more
03-25-2020
12:14 AM
|
0
|
1
|
14678
|
|
POST
|
And double check that your layer doesn't have a selection, definition query, etc that limits which records are processed by the geoprocessing tool. You can switch, instead of using the layer as input, browse and select the feature class on disk so you know you are working against the full dataset. Aside from this, I don't see any reason the tool shouldn't work to calculate the values. Dan's comment about tech support with your data is the best thing.
... View more
03-24-2020
11:45 PM
|
3
|
0
|
14678
|
|
POST
|
Marjorie Jerez This issue has been resolved in Alpha snapshots of ArcGIS Pro 2.6. The issue is due to loading new records into a shapefile and that shapefiles do not automatically recalculate a new spatial index/extent that includes those new features. As a temporary workaround you should be able to run the Add Spatial Index (Data Management) tool against the shapefile to get the shapefile to draw correctly.
... View more
03-23-2020
05:01 PM
|
2
|
1
|
1976
|
| Title | Kudos | Posted |
|---|---|---|
| 3 | 03-22-2024 09:27 AM | |
| 2 | 03-08-2024 01:56 PM | |
| 3 | 02-21-2024 11:58 AM | |
| 1 | 05-09-2023 02:24 PM | |
| 3 | 02-27-2023 05:23 PM |
| Online Status |
Offline
|
| Date Last Visited |
2 weeks ago
|