|
IDEA
|
This was added in ArcGIS Pro 2.9. Here is the text from the What's new in ArcGIS Pro 2.9: You can migrate utility network datasets between geodatabases for staging and testing using Copy and Paste tools and the Export XML Workspace Document and Import XML Workspace Document geoprocessing tools.
... View more
05-12-2022
11:59 AM
|
0
|
0
|
3060
|
|
POST
|
I was able to do this via a file geodatabase using the spatial join tool, add join tool, and calculate field tool against a regular layer. I'd recommend log a case with support with your particular workflow (subtype group layers, services, add spatial join tool) if you're not able to work around it. If you can't work around the issue and you're comfortable writing python, an alternative (although slower method) would be to use a combination of a arcpy data access search / update cursors to scan the spatial join table and push the edits to the corresponding rows.
... View more
05-12-2022
11:40 AM
|
0
|
0
|
1869
|
|
POST
|
You appear to be running a field calculate on a layer that has a join against it. Can you confirm that the field calculate works without the join?
... View more
05-12-2022
08:51 AM
|
0
|
2
|
1876
|
|
POST
|
That search will return any partner who has the words utility or network in their name. What I recommend is a search for anyone who explicitly has a Utility Network Specialty certification from Esri: https://www.esri.com/en-us/about/partners/find-partner/search?specialty=Utility+Network+Management
... View more
07-28-2021
06:40 PM
|
0
|
0
|
2959
|
|
POST
|
The Esri partner network will let you search for Utility Network certified vendors and solutions, but to my knowledge there are only a handful on the marketplace and I believe one of the prerequisites to becoming certified is one or more reference sites in production. I am aware of a few staking vendors who aren't certified (yet?) who have implemented on the UN or who are in the process of implementing on the UN.
... View more
07-23-2021
03:19 PM
|
1
|
0
|
2978
|
|
POST
|
Workaround Using the python command prompt for your conda environment force the 2.8.0 version of the untools to install using the following command conda install untools=2.8.0 Description I have found that the 2.8.0 untools work fine with both the ArcGIS Pro 2.8 and ArcGIS Pro 2.8.1 release. The trick is that if you've upgraded to ArcGIS Pro 2.8.1 the application will automatically install the 2.8.1 version of the tools.
... View more
07-21-2021
10:01 AM
|
1
|
0
|
6868
|
|
POST
|
Configurable Facility ID Creation Using the Utility Network | POWER Engineers
... View more
06-24-2021
06:09 AM
|
0
|
1
|
5401
|
|
POST
|
Here's the link: https://uc2020.esri.com/sessions/15345791/subsession/25135466/The-Journey-from-PLS-CADD-to-GIS
... View more
11-17-2020
12:24 PM
|
1
|
1
|
7382
|
|
POST
|
If you review the log files from loading you should be able to determine how much time was spent on each operation. With numbers that high my guess is that you enabled post processing and you have a significant number of error, this can be confirmed by reviewing the logs and seeing if the "Enable topology" task was responsible for 40+ hours of time.
... View more
09-29-2020
06:14 AM
|
0
|
1
|
2897
|
|
POST
|
If it's an engineer asking they're probably trying to get the data referenced in your electrical distribution maps into a file that can be imported into Milsoft's WindMil application. This requires mapping the elements and values in your GIS to the elements and values in the WindMil model and then creating an extractor to doing the translation. There are several Esri business partners that do this type of work regularly (full disclosure, I work for one of these companies, POWER Engineers). If you're planning on moving to the Utility Network soon and you don't already have such an extractor in place you may be better off planning on building that interface off of the Utility Network since it already has most of the data elements and QA rules in place to support WindMil. You'll still need to build (or buy) an extractor, but having implemented both kinds I can say I prefer the ones run off the Utility Network.
... View more
09-16-2020
07:05 PM
|
1
|
0
|
1785
|
|
POST
|
Matt, I'm gonna have to go dark for the rest of the day, but I'm wondering if there is something up with your asset package (potentially an older version of the model?). Check out my screenshots from earlier in the morning and you'll see that the "globalid" field in the target asset packaqge should be a guid data type and not a globalid data type, this is what allows the data loading workspace to bring your source globalid into the asset package. in your asset package your globalid field is a globalid data type, which means the data loading workspace cannot populate it. I would recommend you download and use the latest Esri Asset Package ( Water Distribution Utility Network Foundation | ArcGIS Solutions for Water ), as the asset package included in the sample data loading workspace appears to be using an older model that doesn't allow for carrying over globalids. Note: there may be some adjustments you need to make to your data loading workspace if there are some model changes between releases. I did have to make a few changes, but I believe all of mine were related to source data issues. Once you have global ids coming across, then getting your related records over should be (relatively) simple. As simple as anything that involves GIS and python can be expected to be.
... View more
05-14-2020
08:22 AM
|
2
|
1
|
4927
|
|
POST
|
Matt, For kicks try making the field mapping all uppercase ( !GLOBALID_1! ), then try running it through and show us what comes across in the "GLOBALID" field of the converted feature.
... View more
05-14-2020
07:54 AM
|
0
|
3
|
4927
|
|
POST
|
Matt, Can you show us the field data types for your source table as well as sample values for a single row for the globalid and globalid_1 columns?
... View more
05-14-2020
07:39 AM
|
0
|
5
|
4927
|
|
POST
|
Matt, You shouldn't need to play any shell games with adding extra fields or calculating new global ids. I just ran the process end to end on my data. If your data already has a GlobalID column (a column with the GLOBALID data type, which it looks like it does) you should map your data to the "GLOBALID" field. Then after running your data loading workspace the global id from your source feature will appear in the global id field on your new in feature: If your data doesn't already have a GlobalID field you should be able to add one using Esris "Add Global ID" tool:
... View more
05-14-2020
07:31 AM
|
0
|
0
|
755
|
|
POST
|
Matt, If the relationship is created on a GlobalID or user generated key then the process is very simple because the primary/foreign keys will be maintained through the conversion. If you're looking to convert relationships (or attachments) which use object id relationships, you'll likely want to add globalids to your source data ahead of the conversion (maybe even now?) and use a python script to map your old object ids to their global ids, then when you recreate the relationships just use the global ids instead. You'll likely want to do this anyways since globalid relationships will allow you to take your data offline.
... View more
05-13-2020
03:23 PM
|
0
|
10
|
4927
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | Thursday | |
| 1 | Wednesday | |
| 1 | 3 weeks ago | |
| 1 | Tuesday | |
| 1 | Monday |
| Online Status |
Online
|
| Date Last Visited |
yesterday
|