POST
|
Basically I'd like to keep all the attributes from the record with the lowest OID. I am dealing with a large scale watercourse dataset that has hundreds of small gaps in the original capture. Most of them are within 4 metres, and so by performing a Near Analysis on the from and to nodes of the dangles, I can create a line feature class from the From-XY and To-XY attributes to connect them. But the merging part has me perplexed...
... View more
06-24-2019
10:28 AM
|
0
|
0
|
957
|
POST
|
Hi Joshua, I am very much interested in how you would apply the merge functionality using arcpy. To answer your question, I would like to merge to the lowest OID feature. Thanks.
... View more
06-24-2019
08:51 AM
|
0
|
2
|
957
|
POST
|
Hi Christine, I have installed the latest version of Arc Hydro for ArcGIS Pro. The commands seem to work fine from the toolbox, but is it possible to call the commands from a python script? In the ArcGIS desktop version, we would just use "Import ArcHydroTools" to setup the environment. However, this does not work in Pro. Is there a different module, or is this functionality not yet available? Many thanks!
... View more
03-13-2018
07:01 AM
|
0
|
0
|
3173
|
POST
|
I tried manually typing in the import command in the Python window, which works with the standard modules. But when I try "import ArcHydroTools", I get the same "No module named.." error. Either the name of the module for calling Arc Hydro has changed or is nonexistent / not available for this version of the tools. We have automated much of our data processing with rather complicated scripts which would not be easily translatable to the Model Builder environment. Nor would I want to do that when I can just stick with ArcGIS Desktop..
... View more
03-13-2018
06:53 AM
|
0
|
4
|
2213
|
POST
|
Hi Stuart, It took me a while trying to find where Arc Hydro installs itself. The MSI installer does not tell you where it will install, and explorer does not search the "Program Files" folder for some weird 'security' reason (I tried typing "ArcHydro" as my search parameter from the C drive and only files I created referencing Arc Hydro or files I opened recently came up). So through manual sleuthing, I found Arc Hydro 'Pro' installs here: C:\Program Files\ArcGIS\Pro\Resources\ArcToolBox\Scripts\ArcHydro (or likely it will install wherever you chose to install ArcGIS Pro) I then proceeded to follow your suggestion, and it seems the AH install was smart enough to do that part for me. There was already a archydropython.pth file located in said "site-packages" folder with the path above already in it. Let me clarify, the individual tools within the Arc_Hydro_Toolbox_Pro.tbx do run okay on their own. It's when I try calling the functions through ArcPy it bails with the following message (my script is called "2. Create EFD**" just in case you're wondering what that means): Start Time: March 12, 2018 4:18:23 PM
Running script CreateEFD...
Failed script 2. Create EFD** ...
Traceback (most recent call last):
File "Z:\GI\ProvincialMapping\Tools\Python\MNRF_TerrainProcessing-JG-2017-08-09\TerrainScripts\Step C.2. Create EFD - master.py", line 38, in <module>
import ArcHydroTools
ModuleNotFoundError: No module named 'ArcHydroTools'
Failed to execute (CreateEFD).
Failed at March 12, 2018 4:18:24 PM (Elapsed Time: 0.59 seconds)
... View more
03-12-2018
01:36 PM
|
0
|
6
|
2213
|
POST
|
Thanks for this tip! I'll give it a try hopefully this afternoon and will report back if successful.
... View more
03-12-2018
11:37 AM
|
0
|
0
|
2294
|
POST
|
Unfortunately no readme file currently comes with the MSI file that I can see. Would be most helpful
... View more
03-12-2018
11:36 AM
|
0
|
0
|
2294
|
POST
|
Thanks for the tip for adding the toolbox, but I am still getting the same error. Either the python functionality isn't there yet or they changed how to access it.. which would be unfortunate, since many of the standard tools are accessed exactly the same way under both platforms (with a few notable exceptions - but they're usually well explained). The same should hold true for Arc Hydro.
... View more
03-07-2018
11:51 AM
|
0
|
2
|
2294
|
POST
|
Yes I tried installing the latest version listed there and no luck. I couldn't find any documentation either on this site.. it's all old help files for ArcGIS.
... View more
03-05-2018
04:11 AM
|
0
|
5
|
2294
|
POST
|
Hello, I am testing some python scripts created originally in ArcGIS 10.3.1/10.5.1 which utilize the ArcHydroTools module. I have installed the latest Arc Hydro package in ArcGIS Pro, but it still doesn't recognize this module. I get the following error when trying to import the module: " ModuleNotFoundError: No module named 'ArcHydroTools' " Is this functionality not yet available? Or should I be doing something else? I tried scouring the documentation but it all relates to ArcGIS desktop not Pro. Not that I could find anyway! Thanks in advance, John
... View more
03-02-2018
02:51 PM
|
0
|
20
|
6559
|
POST
|
Thanks Dan for the quick response. I thought I'd try my hand here first, but that is a good suggestion. Cheers.
... View more
02-01-2018
01:29 PM
|
0
|
0
|
259
|
POST
|
My ministry is currently performing some platform testing before we officially migrate from ArcGIS 10.3.1 to 10.5.1. Our group has been asked to participate and I noticed an issue when working with ESRI Grids in one of our native projections: NAD 1983 Ontario MNR Lambert. On 10.5.1, it can read the projection in ArcCatalog and even set the data frame in ArcMap to this projection, but when I add the grid into ArcMap, the projection reverts to the older projection name: NAD_1983_Lambert_Conformal_Conic. When I take it back to 10.3.1, the projection name has indeed changed to the old name. NAD_1983_Lambert_Conformal_Conic no longer appears as an option in ArcMap, so it might be a legacy "ArcInfo" translation nuance that has changed. The parameters for these projections are identical but since it applies specifically to Ontario, I understand this was the rationale for adopting the new name. But for some commands in ArcGIS, this becomes an issue because they will think they are different projections even though they aren't, and because of this, will not work properly. I tried redefining the projection in ArcMap to Ontario MNR Lambert but nothing happens. I have to go back to 10.3.1 to successfully redefine it. This phenomenon only happens with ESRI Grids. I tested rasters in file geodatabases and ERDAS Imagine file formats with no apparent issue. I wish I could just abandon the ESRI Grid format for many reasons, but we have several tools which still write to this format and it would not be an easy fix to convert formats. It would take days if not weeks to reprogram, retest, etc... And since ESRI Grids are still supported (I have yet to hear otherwise), is there a known fix for this type of issue? Thanks in advance.
... View more
02-01-2018
01:07 PM
|
0
|
2
|
352
|
IDEA
|
This is not very useful if you don't have access to SDK, which requires Visual Studio to be installed. Useful tools that were available in ArcGIS should be made available in Pro without having to install resource hogging SDK's and third party tools that may or may not be actively supported.
... View more
01-19-2018
01:58 PM
|
0
|
0
|
1169
|
POST
|
Thanks Curtis. I will consider doing this. In some of the tools we have designed, there is a certain structure to our data products which we don't want altered by the user. But it was very handy to show these read-only outputs so they know what to look for when the tool is done (as these outputs serve as inputs to subsequent tools after they are QA/QC'd). This feature goes back to my programming days in VB and C+ in creating 'intelligent' user entry forms for various applications.
... View more
11-09-2017
12:19 PM
|
2
|
0
|
1340
|
POST
|
Hello, I am testing some rather robust tools created in ArcGIS Desktop 10.3.1 in ArcGIS Pro 1.4. One nuisance I have come across is a change in behaviour when working with disabled parameters. In the help, it states the following: When a parameter is disabled, it will disappear from view on the tool dialog box, and when reenabled, it will reappear. This effect is seen on several system geoprocessing tools such as the Add Field tool where the need for several parameters is dependant on the field type. You can still manipulate them in the background using the validation tab, however, they are no longer displayed on the form. I want the user to be able to see data outputs from the tool and where they are going to be created before running the tool. I can no longer do this when the parameters are hidden from view. I have attached an image showing the form in Desktop and the equivalent in Pro. As you can see, the read-only parameters outlined in green in Deskstop no longer show up in Pro. Is there a way to get around this? Can this functionality be restored in a future version of Pro? This is a rather advanced way of controlling user entry and data outputs which I would still like the user to still have the ability to see.
... View more
10-27-2017
04:03 PM
|
0
|
4
|
1493
|
Title | Kudos | Posted |
---|---|---|
1 | 06-25-2020 06:21 PM | |
1 | 11-16-2020 06:42 AM | |
2 | 11-09-2017 12:19 PM | |
1 | 07-17-2019 01:06 PM | |
1 | 07-18-2019 08:49 AM |
Online Status |
Offline
|
Date Last Visited |
03-23-2024
04:39 AM
|