|
POST
|
Your process that creates the fittings will also need to create the corresponding vertices on the mains you are trying to connect them to. There are transformers in FME that can you this, but you can also test this using the Integrate geoprocessing tool. You should do this during the conversion or in the asset package, as running this tool against a live utility network will create a lot of dirty areas.
... View more
03-18-2024
09:02 AM
|
0
|
0
|
1242
|
|
POST
|
This seems like a bug, please log a case with support so they can investigate.
... View more
03-18-2024
08:34 AM
|
1
|
0
|
2350
|
|
POST
|
Subnetworks are allowed to have multiple controllers. When you trace the system analyzes all the controllers for the subnetwork to determine the path upstream, downstream, or to isolate an area.
... View more
03-18-2024
06:02 AM
|
0
|
5
|
4864
|
|
POST
|
If your tracing doesn't include the taps, laterals, or meters from your services than it's likely that you don't have any vertices on your mains to support connectivity. This is done automatically when you edit in pro, but if you programmatically created those features you will need to integrate the vertices from your services into their corresponding mains. This is discussed in further detail in this community question.
... View more
03-13-2024
08:50 AM
|
0
|
2
|
1329
|
|
POST
|
From the online help page discussing geodetic length versus planar length: "Geodesic distance always produces a more accurate result and is the recommended method, unless speed is more important than accuracy." That page includes a good breakdown of why it is considered to be more accurate and given that you're using this calculation in a popup for a single feature, the performance consideration isn't a concern.
... View more
03-13-2024
06:47 AM
|
1
|
0
|
1168
|
|
POST
|
@JohnAlsup @BryanMay531 One important thing that is easy to overlook in John's response is that the electric device unit has been replaced by the Electric Junction Object non-spatial object table. You did this because the Electric Junction Object table doesn't suffer from the limitations outlined in his response. If you want to know more about how to use this new table in the electric model, you can watch this presentation from IMGIS: IMGIS - Esri Videos: GIS, Events, ArcGIS Products & Industries
... View more
03-13-2024
06:44 AM
|
2
|
0
|
1112
|
|
POST
|
The UN system tables do reference an internal identifier that isn't preserved when you create a new database or copy/paste items between databases. If you open the map that you used to publish your original service and fix any broken layers, you can use that to overwrite your original service. If you don't have your original map (uh oh!) you can either recreate it (taking care to preserve your layer ids) or you can browse the file system of your ArcGIS Server machine to download a copy of the map that was used to publish the service.
... View more
03-08-2024
11:21 AM
|
0
|
1
|
954
|
|
POST
|
The meaning behind subnetworks depends on which model you're using, and based on your description it sounds like you're modeling a water system. With that in mind I'm going to answer these questions using the configuration found in the base water utility network foundation. It sounds like this area contains a single "water system" subnetwork that has three "water pressure" subnetworks. The supply/storage that provide water to all three areas during normal operation will be subnetwork controllers for the water system tier. While the equipment that regulate each zone (pressure valves, pumps, etc) are exclusive to each area will be subnetwork controllers for the water pressure tier for each area. Here is a rough diagram I just put together: You can find some lessons specific to water in the following learning series (Learn ArcGIS Utility Network for Water Utilities). There are three tutorials and one article (Utility Network Error Management: Creating Subnetworks for Water Utilities (esri.com)) specific to how to create subnetworks for water networks.
... View more
03-08-2024
07:03 AM
|
0
|
0
|
1794
|
|
POST
|
@AaronCrisanto ah, that's your problem. To connect there needs to be a vertex on the main that is co-located with the device/junction. This is something that we do automatically when you edit the utility network, but if you are creating your taps/laterals during conversion on simple features than you won't see that vertex. I recommend you add a pre-processing step in your asset package that will create these vertices. Depending on how you're migrating your data you may be able to either use a transformer in FME/Data Interop, or use the Integrate/Pairwise Integrate gp tool in ArcGIS Pro.
... View more
03-06-2024
08:33 AM
|
0
|
0
|
2590
|
|
POST
|
@AaronCrisanto for the tees that aren't connected to main, is there a vertex on the main at the same location as the tee? or is the tee just snapped to the edge without a vertex?
... View more
03-05-2024
10:36 AM
|
0
|
1
|
2612
|
|
POST
|
Good question. Changing an asset type's association role from being a container to a structure (or vice-versa) will invalidate any containment/attachment rules for that asset type, along with all the associations associated with any features that belonged to that asset type. Because of this, I recommend you do several prototypes/pilots of your data to work through this, and any other, configuration or data modeling issues before you stand up your production utility network. If you do make a mistake or change your mind several months later (on this or any other items we don't let you change after deploying), you do have a last resort to making changes. You can always export your data to an asset package (losing all your history and versions), make the configuration changes, then standing up a brand-new database and utility network.
... View more
03-04-2024
12:11 PM
|
1
|
1
|
1086
|
|
POST
|
@NadiaAlami Make sure that your device class has the correct domain assigned to it at the object class level (for this UI), and that each subtype/asset group that corresponds to an operable device has this domain assigned at the subtype level (for the attribute editor).
... View more
03-04-2024
06:31 AM
|
0
|
1
|
1471
|
|
POST
|
Can you be more specific with what you mean by clearing the dirty areas. Are you concerned about your data mappings being wrong? Overall data quality? Something else? In general: Create your data mappings Work with your SME to get them as close as you can (rename and add asset type if you need to) Review your dirty areas (topology errors) with your SME to determine the best way to resolve the errors. Resolve the errors through data cleanup, configuration, and automation Define subnetwork controls to accurately reflect your network sources/sinks so you can perform tracing and analysis Steps 1&2 are covered in the data migration learning series I linked above, and steps 3&4 are covered in the connectivity and topology learning series, and step 5 is covered in the subnetworks learning series.
... View more
03-04-2024
06:29 AM
|
0
|
7
|
4964
|
|
POST
|
@BryanMay531 I just noticed that you're running the 3.1 version of the data loading tools using a 3.2 version of ArcGIS Pro. The data loading tools were incorporated into the core geoprocessing framework of ArcGIS Pro in 3.2, so I'd recommend you try this again using the Data Management > Data Loading toolbox. Even if it doesn't succeed, you should see some more informative error messages.
... View more
02-29-2024
01:50 PM
|
0
|
0
|
3557
|
|
POST
|
Can you explain what you mean by lost connectivity? Were these features previously connected/traceable in another system or did you generate them programmatically? Looking at the screenshot you've attached it appears that either the tees/taps of your laterals aren't snapped to the mains, or there isn't a common vertex on the main for the tees/taps to connect to.
... View more
02-29-2024
01:43 PM
|
0
|
1
|
2723
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | yesterday | |
| 1 | Friday | |
| 1 | Friday | |
| 1 | Thursday | |
| 1 | 2 weeks ago |
| Online Status |
Online
|
| Date Last Visited |
6 hours ago
|