|
BLOG
|
@SanneMikkelsen The link data dictionary works. Perhaps it is getting blocked on your side.
... View more
Friday
|
0
|
0
|
105
|
|
IDEA
|
@NicoleHanson1 Thanks for the idea. Dynamic segmentation is a key capability and can be very useful. A few follow-up questions: Is this idea for Overlay Events GP tool? Is this idea for Dynamic Segmentation tool? Or both? The Overlay Events GP tool honors definition query on Input Route Features and Event Layers. So potentially, you can filter LRS data for current time and get the desired output. Have you tested this? If so, are there additional gaps with the output generated.
... View more
Thursday
|
0
|
1
|
65
|
|
POST
|
Updating this old thread for tracking and community documentation. Related post: https://community.esri.com/t5/arcgis-pro-questions/arcgis-pro-calculate-geometry/m-p/1667532 I added links to the Calculate Geometry Attributes as well as requirements of the field/data type for the geometry attributes. Check if you are using 'double' type for XY coordinates.
... View more
3 weeks ago
|
0
|
0
|
154
|
|
POST
|
@ShailendraKomal I added links to the Calculate Geometry Attributes as well as requirements of the field/data type for the geometry attributes. Check if you are using 'double' type for XY coordinates.
... View more
3 weeks ago
|
0
|
0
|
80
|
|
POST
|
Updating this old thread for tracking and community documentation. Use Calculate Geometry Attributes to add information to a feature's attribute fields representing the spatial or geometric characteristics and location of each feature, such as length or area and x-, y-, z-coordinates, and m-values. Access the Calculate Geometry tool by opening the attribute table and right-clicking the field to bring up the context menu. There is an option to 'Calculate Geometry'. This tool can also be accessed directly from the geoprocessing pane from within the Data Management toolbox > Calculate Geometry Attributes. You can select an existing field or provide a new field name. If a new field name is provided, the field type is determined by the type of values that are written to the field. Count attributes are written to long integer fields; area, length, and x-, y-, z-coordinate, and m-value attributes are written to double fields; and coordinate notations such as Degrees Minutes Seconds or MGRS are written to text fields. Reference KB article: Calculate geometry in ArcGIS Pro
... View more
3 weeks ago
|
0
|
0
|
187
|
|
BLOG
|
Congrats to the Geography Team at UMass Amherst with special mention to @AWildHealy and Andrew-James Finn. You took a common campus problem that impacts students and designed a neat solution. Thanks for sharing your process of employing ArcGIS to address the gap; it is techie and entrepreneurial!
... View more
3 weeks ago
|
0
|
0
|
129
|
|
POST
|
@VenkataKondepati You can find the schema at Introduction to Communications Utility Network Foundation
... View more
a month ago
|
1
|
0
|
118
|
|
POST
|
@TrinityShuler02 The stack exchange provides a basic way of getting the distances. However, you have to repeat the entire process for new sets of points - black polygon and pink diamond. The same link also mentions linear referencing. The workflow is better handled through Linear Referencing ; it does need learning some new concepts and tools. You can get started with the following references: Linear referencing datasets NHD flowlines may be modelled as Routes with the Start/End locations as Calibration Points or simply update measures on the vertices based on geometry length. You can then Locate Features Along Routes using NHD flowline as input route and the points as input features. You can provide search radius of 300 feet for the points that do not intersect the NHD routes. The tool will generate a event table with the located measure of each point along the NHD route. You can then do a simple calculation to find the distance between specified points. This method can be used to persist the measures on the NHD flowline routes. You can generate the event table by running Locate Features Along Routes for newer sets of points.
... View more
a month ago
|
1
|
0
|
272
|
|
POST
|
@CoronaGis Thanks for posting your use case with details and drawing. I encourage organizations to conceive the best way to model the network, rather than duplicate what a legacy system used to do. Utility Network has much broader modelling capabilities with greater possibilities. Here are my comments: Start at identifying the subnetworks for your gas distribution system. A great resource for this is: Managing Gas and Pipeline Networks: Creating Subnetworks Is District similar to a pressure zone? If so, Compressor or Regulator are the prime candidates to act as the subnetwork controller for Pressure tier. Controllable valves are the prime candidates to act as the subnetwork controller for isolation tier. Measurement points do not impact network behavior and therefore not good choice for 'device' and hence 'subnetwork controller' (only devices can act as controllers). Assuming use of the Gas and Pipeline Referencing Utility Network Foundation , PipelineDevice has a yes/no flag field, that can be used to indicate Measurement or SCADA indicator. Note this is simply an attribute, and doesn't impact network behavior. Utility companies often have unique business requirements that drive the modelling decisions. Hoping others in the community will share their implementation advice.
... View more
11-07-2025
09:11 AM
|
0
|
0
|
273
|
|
POST
|
@EdwardBlair The Utility and Pipeline Data Model (UPDM) supports multiple implementation patterns. Utility Network (Gas Asset Package) ArcGIS Pipeline Referencing (information model) Utility Network and ArcGIS Pipeline Referencing The model is flexible to allow for all these implementation variations. In some cases, this introduces redundancy as for Squeeze-off. The choice is up to the organization based on their business requirements. Squeeze-offs maybe better modeled through Utility Network topology and rules - use as Pipeline Junction. However, some pipeline operators using APR-only, model Squeeze-off as LRS event using the P_SqueezeOff class.
... View more
11-05-2025
08:25 AM
|
1
|
1
|
260
|
|
POST
|
@gisuser12 Thanks, I could reproduce the issue using the sample provided. I made a change to use the same data type of TEXT(50) for routes but that didn't change the behavior. I suggest logging a Tech Support Case.
... View more
11-03-2025
09:26 AM
|
0
|
0
|
232
|
|
POST
|
@gisuser12 The linear referencing tools from ArcMap were redeveloped in Pro with little to now change in the logic. Are you able to share a data sample including the routes and event tables?
... View more
10-31-2025
11:18 AM
|
0
|
3
|
283
|
|
POST
|
@COSPNWGuy Yes the solution includes Splice Diagrams that you can Explore Diagrams Good examples with sample splice diagrams at: https://community.esri.com/t5/arcgis-utility-network-questions/splice-diagrams-on-naperville-data/m-p/1613149
... View more
10-28-2025
11:48 AM
|
0
|
0
|
190
|
|
POST
|
@Jishnu_Kaithakkal At the latest ArcGIS Field Maps 25.2.0 release, there's capability to define a branch version that field teams will access when they have connectivity. Field user can then select the version of each feature service from the associated feature service drop-down menu App settings page > Versions section. Ref: https://doc.arcgis.com/en/field-maps/latest/prepare-maps/configure-the-map.htm
... View more
10-23-2025
12:15 PM
|
3
|
0
|
222
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | a month ago | |
| 1 | 06-16-2025 07:58 AM | |
| 1 | a month ago | |
| 1 | 11-05-2025 08:25 AM | |
| 3 | 10-23-2025 12:15 PM |