|
IDEA
|
All of our needs are almost always single starting point. I can't think of a time we needed more than one. Sometimes simple barriers are useful, like selecting certain nodes and edges as barriers. Correct. No editing or validating topology.
... View more
2 weeks ago
|
0
|
0
|
121
|
|
IDEA
|
I have been looking for simple web based upstream and downstream tracing for hydro networks for years now. It is is a huge need in the industry.
... View more
2 weeks ago
|
0
|
0
|
128
|
|
IDEA
|
I also just added this idea to the Experience Builder Idea site to tie these concepts together. The goal should be the enablement of tracing Trace Networks in ESRI web products.
... View more
3 weeks ago
|
0
|
0
|
186
|
|
POST
|
I also added this idea to the Experience Builder ideas page if you want to upvote.
... View more
3 weeks ago
|
0
|
0
|
45
|
|
POST
|
I also just added this idea to the Experience Builder page as well if you wanted to upvote.
... View more
3 weeks ago
|
0
|
0
|
37
|
|
IDEA
|
Please build an EB widget that allows for tracing of Trace Networks (distinct from the concept of tracing Utility Networks). Please work with JS SDK team with the enablement of the JS SDK to "understand" network topology which is a prerequisite item for any kind of widget to be be built. I know ESRI has made the past decision to not support Trace Networks on the web. I want to encourage ESRI to rethink this position for several reasons. First, utility networks make zero sense for simple topologically defined hydro networks that still need tracing functionality. A UN is a lot of bloat for these. Second, you already have the Trace Network capability exposed at the server level. It seems odd to leave the job "half finished" and not offer any ESRI tools utilizing it. Third, ESRI needs to have some kind of "plan B" insurance to offer customers with the coming of NSRS 2022 which has significant impacts to future and current utility networks in the USA as there is no way to reproject a currently built UN.
... View more
3 weeks ago
|
7
|
0
|
131
|
|
POST
|
I know this question is old, but I learned some things at the 2026 ESRI UC that might be useful. Bottom line, having data in a utility network is the only way to perform traces as of today. This is essentially because the Jasvascript SDK doesn't do anything or "understand" network topology. Trace Network capability IS actually supported at the server level (ie. they are exposed to the web), but ESRI hasn't taken the next step for their Javascript SDK to use it - therefore you don't have any kind of widgets in EB for trace network tracing. If you wouldn't mind upvoting the idea in the link above, maybe we can get ESRI to change their minds.
... View more
3 weeks ago
|
0
|
0
|
39
|
|
POST
|
I do hope ESRI reevaluates this position. Trace Network capability is exposed at the server level - we just need the JS SDK to take advantage of it. Please upvote this idea if interested. There are many use cases where using a UN simply to gain tracing functionality on the web doesn't make any sense. Surface water hydro networks are a good example. They are simple topological networks that need to be traced. They are not a man made utility and don't behave like one. A UN is a lot of bloat for such a simple network.
... View more
3 weeks ago
|
0
|
0
|
47
|
|
IDEA
|
Pretty simple idea. Allow the JS SDK be able to take advantage of network topology. It was to my utter surprise that I learned that Trace Networks have been a exposed capability at the server level for a while, and that it isn't just a "Pro" thing. See below screen shot (apologies for the quality - I took this picture at this year's 2026 ESRI UC at the geodatabase kiosk). Notice that Utility and Trace Networks are distinct server side capabilities. They are not the same. It seems incomplete to have this server side capability with no JS SDK ability to use it. I started to put things together with the help of Jose at the JS SDK booth that even though the Trace Network capability is exposed, there is no current ability for the JS SDK to use network topology - hence no JS components, hence no widgets in any ESRI web product that can trace Trace Networks on the web (only in Pro). Jose seemed to indicate that there might be a JS project already in place to look into enabling topology in the SDK. I want this idea to lend credence to it if such a project is on the books. Additionally, it would be good for ESRI to do this as there is a lot of headwinds coming for utility networks due to the upcoming NSRS 2022. Also, there is a lot of hydro networks that do not lend themselves to utility network implementations. It would be good for organizations to have other alternatives (albeit more simplistic) to trace networks on the web than the UN which is the only option currently.
... View more
3 weeks ago
|
8
|
6
|
231
|
|
IDEA
|
Currently, it is not possible to reproject a built utility network. The only way to do this is to go back to the asset package "level", reproject, and build the UN back up. I understand the initial logic on the design decisions on why the coordinate system is "locked down". However, there is a "tsunami" approaching that many in the industry are going to have to deal with that now must be considered. There have been rumblings about the NSRS 2022 (National Spatial Reference System of 2022) for several years. ESRI is aware of it and has blogged about it. It was obvious in this year's presentation by the National Geodetic Survey at the 2026 UC, that it is coming - most likely sometime in 2027. The NGS has transitioned from the "science phase" to full on outreach mode. They are trying to get the word out that the new system is coming. With this news, there are many many utility networks that will and must be migrated to the new coordinate system. This is essentially any utility in the United States or territories. There needs to be a better way for a UN to move to a new coordinate system than the answer essentially be "start over". Orgs have spent countless hours and money building these networks and only to have to start over to change coordinate systems will be a pill hard to swallow. So, the idea is simple - allow reprojection of a built UN.
... View more
3 weeks ago
|
21
|
1
|
234
|
|
DOC
|
I noticed that there are no sessions related to the Utility Network in this custom agenda. Do you have any recommendations on learning about UN telecom applications?
... View more
05-29-2026
09:28 AM
|
0
|
0
|
799
|
|
IDEA
|
@BernSzukalski, or anyone from the Live Feeds team, any updates on this? It has been over five years, and this seems like such incredibly low hanging fruit, not to mention important! I mean this is THE official emergency broadcast feed of the US government that goes to all TV, radio, and cell phones within an area, and it isn't in the Living Atlas!!!!!?????? Can ESRI please work with FEMA to make this happen! What needs to happen to get this unstuck?
... View more
05-29-2026
08:54 AM
|
0
|
0
|
596
|
|
POST
|
Could anyone speak to the capabilities of the current telecom UN foundation model verses what is coming in the future (currently being worked on in beta)? I'm trying to determine if I should be migrating our fiber data to what is available now or wait for the beta to release and become supported. I'd really like to get going, but if I am going to be really shooting myself in the foot, I'd rather wait. My understanding is that the new telecom UN domain schema will be more performant particularly for large systems with the invention of "record grouping" in the database to shrink database size. Is that pretty much it as far as features go? We only have about 60 miles of cable (about 33,000 individual strands) and we only model down to strands (no wavelengths, etc). The service area is a mid size city. Needs are pretty straight forward with splicing and OTDR traces etc.
... View more
02-06-2026
05:01 PM
|
0
|
2
|
1140
|
|
POST
|
Hi all, Long-time GIS user, but first-time water resources/H&H workflow question. I’m working on a project where consultants are developing separate HEC-RAS models for different drainage basins in our city, each producing flood surface results for various design storm events. Once all the modeling is completed, there’s a desire to generate a single multidimensional .crf layer of water surface elevations that represents the combined results of all models. The end goal is to create a smooth, time-enabled flood animation/analysis layer for our ArcGIS ecosystem. I understand that consultants can export individual water surface .tif rasters for each model timestep, but this results in a very large number of files to manage, and I’d like to avoid unnecessary raster wrangling if possible. My main questions: Is it possible for ArcGIS Pro to import native HEC-RAS output results (e.g., the RAS Mapper results folder or the simulation *.hdf file) directly, without requiring hundreds of exported TIFFs? If so, what is the best workflow to convert those native HEC-RAS outputs into a single multidimensional .crf suitable for time-enabled visualization and analysis? Are there best practices or considerations when combining outputs from multiple, separate HEC-RAS models into one coherent time-enabled raster layer? Any guidance would be greatly appreciated. Thanks!
... View more
12-04-2025
03:59 PM
|
1
|
2
|
1621
|
| Title | Kudos | Posted |
|---|---|---|
| 7 | 3 weeks ago | |
| 8 | 3 weeks ago | |
| 21 | 3 weeks ago | |
| 1 | 12-04-2025 03:59 PM | |
| 1 | 07-18-2024 11:35 AM |
| Online Status |
Offline
|
| Date Last Visited |
2 weeks ago
|