We have a number of reports, python scripts, etc. using ST_GEOMETRY queries against versioned views (*_EVW) in our Geometric Network dataset. Example, against a specific where clause, the query will return SUM(SDE.ST_LENGTH(SHAPE)). I haven't found any promising replacement yet in our Utility Network test environment. * With branch versioning, I don't see a way to do this, since there is no equivalent to the _EVW. * I don't believe a query to the REST endpoint can return a sum of Shape_Length, but I could be wrong on that. * I've seen some arcpy examples to cursor through selected features, aggregating the geometric length of each, but with a large (300K+ line records) dataset this is not ideal. Any ideas on how to accomplish this via some form of automation? Right-clicking and summarizing shape length in ArcGIS Pro against a selected set isn't a fit either - since the results get formatted into various outputs. Thank you, UN people. EDIT: I suppose my jumping-off point is this: https://www.esri.com/arcgis-blog/products/utility-network/electric-gas/utility-network-sql/ And this: https://community.esri.com/t5/arcgis-utility-network-documents/branch-version-sql-views-utility-network/ta-p/1200811

* With branch versioning, I don't see a way to do this, since there is no equivalent to the _EVW. You can query the branch version featureclass base table directly using in the proper where clause parameters just as described in the article. Then, you can use the st_geometry function to calculate the shape length, to make the query easy accessible, then you can create a view, and to make the view results to show faster, then you can create a materialized view. Branch Version Sql Views - Utility Network - Esri Community SQL Views and Branch Versioning - Esri Community Utility Network Journey: Branch Versioning and SQL

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to access Sum of Shape_Length from of selected/where clause features

SillPaul

We have a number of reports, python scripts, etc. using ST_GEOMETRY queries against versioned views (*_EVW) in our Geometric Network dataset. Example, against a specific where clause, the query will return SUM(SDE.ST_LENGTH(SHAPE)).

I haven't found any promising replacement yet in our Utility Network test environment.

With branch versioning, I don't see a way to do this, since there is no equivalent to the _EVW.
I don't believe a query to the REST endpoint can return a sum of Shape_Length, but I could be wrong on that.
I've seen some arcpy examples to cursor through selected features, aggregating the geometric length of each, but with a large (300K+ line records) dataset this is not ideal.

Any ideas on how to accomplish this via some form of automation? Right-clicking and summarizing shape length in ArcGIS Pro against a selected set isn't a fit either - since the results get formatted into various outputs.

Thank you, UN people.

EDIT: I suppose my jumping-off point is this: https://www.esri.com/arcgis-blog/products/utility-network/electric-gas/utility-network-sql/

And this: https://community.esri.com/t5/arcgis-utility-network-documents/branch-version-sql-views-utility-network/ta-p/1200811

Najděte více příspěvků označených jako

Accepted answers

MMBR

With branch versioning, I don't see a way to do this, since there is no equivalent to the _EVW.

You can query the branch version featureclass base table directly using in the proper where clause parameters just as described in the article. Then, you can use the st_geometry function to calculate the shape length, to make the query easy accessible, then you can create a view, and to make the view results to show faster, then you can create a materialized view.

Branch Version Sql Views - Utility Network - Esri Community
SQL Views and Branch Versioning - Esri Community
Utility Network Journey: Branch Versioning and SQL

All comments

MMBR

With branch versioning, I don't see a way to do this, since there is no equivalent to the _EVW.

You can query the branch version featureclass base table directly using in the proper where clause parameters just as described in the article. Then, you can use the st_geometry function to calculate the shape length, to make the query easy accessible, then you can create a view, and to make the view results to show faster, then you can create a materialized view.

Branch Version Sql Views - Utility Network - Esri Community
SQL Views and Branch Versioning - Esri Community
Utility Network Journey: Branch Versioning and SQL

Ayan Palit

@SillPaul A conceptual solution will be to use a Trace configuration and use an Add function which will sum the targeted Network Attribute (Shape_Length) as it traces the line features.

Review the documentation and the following blog:

Exploring the ArcGIS Utility Network Trace Framework

JimClarke

One more option is to use the outStatistics parameter on the REST API. See this blog: generating-reports-from-the-utility-network

SillPaul

Thanks to everyone for suggesting multiple potential solutions. I'll definitely keep the trace configuration suggestions and Statistics parameter via REST API in mind for future consideration, as these align best with the UN service-oriented approach.

Queries against database views are more in my comfort zone. Creating the materialized view using sample syntax (Oracle) from this post from Robert Krisher is working well.

Branch Version Sql Views - Utility Network - Esri Community

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.