|
POST
|
Sure thing - Dirty areas were being calculated for points by expanding the minimum bounding rectangle (MBR) of the feature by 1 x 1 unit (which was a degree of measurement for GCS) prior to this fix. This is now being calculated as approximately 1 x 1 foot.
... View more
11-18-2019
11:40 AM
|
3
|
0
|
1116
|
|
POST
|
I wanted to contact you because I was looking into your inquiry on the following enhancement: ENH-000123974 "Provide the ability to configure the dirty area buffer distance default calculation for a Utility Network" This was incorrectly linked to the internal dev issue that was resolved for 2.5 regarding dirty area size for GCS. However the feature/enhancement for the ability to configure the dirty area size generated is still under consideration for a future release. I'll get this corrected in the system and sorry for this confusion.
... View more
11-13-2019
08:56 AM
|
1
|
2
|
3535
|
|
POST
|
Darren - Branch versioning follows a services based implementation pattern and there are not currently any plans for direct SQL access. As you may have noticed, versioned views are not created for branch versioned datasets. REST calls can be used for these workflows to query and edit within specific branch versions. Have you attempted to query within REST using the Query (Feature Service/Layer) operation?
... View more
11-08-2019
07:10 AM
|
4
|
1
|
9112
|
|
POST
|
Kevin - To add onto what Manoj provided, I wanted to give you some of the places in the documentation you can piece this together for the core functionality that is used outside of an asset package. 1. You need a database sequence. You can create this in the database yourself or using the ArcGIS tool - Create Database Sequence 2. You need a calculation attribute rule created on the ASSETID field that will fire to populate the ASSETID based on a specific edit operation. This rule will use the database sequence you created along with an Arcade function to get the next value in that database sequence. Here it the Arcade function reference for NextSequenceValue that you would use in your attribute rule: NextSequenceValue The Attribute rule script expression examples does not have this exact example workflow, but does have a calculation attribute rule that uses the NextSequenceValue to populate based on a prefix + the next value in the sequence. In the example, it fires on insert operations (triggering event).
... View more
09-20-2019
05:02 AM
|
1
|
0
|
2673
|
|
POST
|
Stephen - Can you confirm if you made changes to the asset package?
... View more
09-19-2019
10:47 AM
|
0
|
2
|
2807
|
|
POST
|
Thanks for the suggestion Hector - perhaps in the future there will be blogs about workflows with using branch versioning with some of our apps. While not in a blog format, there was a thread that discussed this on geonet: https://community.esri.com/thread/209498-taking-branch-versioned-data-offline-with-collector
... View more
09-12-2019
07:20 AM
|
0
|
1
|
5270
|
|
POST
|
The asset packages have versions. I believe the version that this documentation is referring to the Utility Network Release. The version of ArcGIS Pro that is used to create a utility network determines the release for the UN. Utility network dataset administration—ArcGIS Pro | ArcGIS Desktop - reference the ArcGIS platform compatibility section Hope this helps! I'll confirm with the Solutions team and see if we can clear up the terminology on this topic if so.
... View more
09-04-2019
07:48 PM
|
0
|
0
|
1175
|
|
POST
|
Strangely enough when we tried to return the owner back to the original user the system errors that the input dataset must be branch versioned. Weird as this was in branch versioning. What was the exact error? There may also be a requirement for the database connection to have the versioning type set to branch. Yes, support services would be a great place to start investigating this. Keep me posted.
... View more
08-28-2019
07:40 AM
|
0
|
0
|
4128
|
|
POST
|
I've never seen that error message before - So you are attempting to disable the network topology using a database connection after the portal utility network owner was updated? I was able to run the Update Portal Dataset Owner tool and then able to run the Disable Network Topology tool directly following this (after signing into the portal as the updated portal dataset user of course).
... View more
08-27-2019
04:52 PM
|
0
|
3
|
4128
|
|
POST
|
Killian Paenen The above symptoms sound like they are related to the following bug. Please review and see if the workarounds noted help you move past these compatibility issues. Bug: Unable to perform editing/administration workflows when accessing a utility network from an ArcGIS Enterprise 10.6.…
... View more
08-27-2019
05:12 AM
|
0
|
0
|
4195
|
|
POST
|
Hi Ivo - Since this is not directly related to the original post, I would suggest you start a fresh thread on this. We recommend you use the specific industry page for the asset package you are working with. For example: Electric and Gas https://community.esri.com/community/water-utilities
... View more
08-21-2019
07:24 AM
|
0
|
1
|
1596
|
|
POST
|
A series of blogs are released that discuss branch versioning in ArcGIS Pro / ArcGIS Enterprise. This discussion is for questions that are directly related to content/concepts included in these blogs. Branch versioning blogs: To branch or Not to Branch - An Introduction Branch Versioning: Setting the Stage - Configuration and publishing Editing and Administration with Branch Versioning - It's Showtime! - Basic editing and administration Enterprise GIS ArcGIS Enterprise
... View more
08-20-2019
10:58 AM
|
4
|
19
|
10407
|
|
POST
|
You are correct that the new tool to transfer ownership of the portal utility network owner is new for ArcGIS Pro 2.4 - it is called: Update Portal Dataset Owner—Data Management toolbox | ArcGIS Desktop Please let me know if you have any questions about this process. In addition to the tool help, there is a section in the following topic: Utility network dataset administration—ArcGIS Pro | ArcGIS Desktop
... View more
08-14-2019
12:44 PM
|
3
|
5
|
4128
|
|
POST
|
I am not able to reproduce this using the following steps: - Add the utility network to an active map view - Specify custom symbology for some of my asset groups (just a few) - Publish to a feature service - Add the utility network and all related layers to a new map view I have a few additional questions: - What version of ArcGIS Pro and ArcGIS Enterprise are you using? - What does assigned symbology mean specifically? Did you just set symbology on the data before publishing? Can you provide specific steps and examples? Did you set custom symbology for all layers? I need the smallest amount of steps to reproduce this.
... View more
07-30-2019
05:25 AM
|
0
|
0
|
975
|
|
POST
|
Are you using feature barriers or dynamic barriers? https://pro.arcgis.com/en/pro-app/help/data/utility-network/barriers.htm There is no way to bypass traversability for physical barriers currently. The team has had discussions on how to resolve this type of situation. Is there is an open device upstream that should be closed that you are trying to find it? If so, then using a condition barrier would not help since that would prevent traversability back to the source. You may want to try and use a filter barrier in addition to an output condition with device status = open. This should tell you what the open device is that needs to close.
... View more
07-29-2019
09:44 AM
|
1
|
0
|
1947
|
| Title | Kudos | Posted |
|---|---|---|
| 5 | 11-17-2025 08:22 AM | |
| 2 | 11-06-2025 03:32 PM | |
| 8 | 05-23-2022 01:34 PM | |
| 1 | 03-24-2022 06:56 AM | |
| 1 | 07-03-2024 06:55 AM |
| Online Status |
Offline
|
| Date Last Visited |
a week ago
|