|
POST
|
@JayLarsen the following come to mind, hope this helps. https://demographics5.arcgis.com/arcgis/rest/services/USA_Traffic_Counts/MapServer https://traffic.arcgis.com/arcgis/rest/services/World/Traffic/MapServer
... View more
02-08-2024
02:03 PM
|
0
|
1
|
2961
|
|
POST
|
@EricAkiyoshi Very well laid out pilot study - thanks for sharing with the Esri Community!
... View more
02-08-2024
07:23 AM
|
0
|
0
|
1766
|
|
POST
|
@AlexanderShields_AZ The start (green) and end (stop) graphics to show route editing segments are very much there. What is the ArcGIS versions used? Also the screenshots suggests that centerline does not touch the routes. In this case, the start and end of realign is not auto-detected and could be the reason.
... View more
02-06-2024
10:47 AM
|
0
|
1
|
5029
|
|
POST
|
@CristinHolmgren2 The deployment of Utility Network to enterprise geodatabase (SDE) requires the Utility Network user type extension. Please ensure that you are signed into Portal and the connected user has the Utility Network user type extension license. Please post your update.
... View more
01-25-2024
07:22 AM
|
0
|
0
|
1944
|
|
POST
|
@Bud I like to consider control points similar to vertices with a special designation. They are stored as geometry attributes and you can convert a control point to a vertex or a vertex to a control point. Note this is a newer functionality introduced at Pro 3.1. I found the SDK reference here: https://pro.arcgis.com/en/pro-app/3.1/sdk/api-reference/topic1519.html
... View more
01-17-2024
10:06 AM
|
1
|
0
|
793
|
|
BLOG
|
@gargarcia Thanks for your interest! Most Esri data models started out as a stand-alone schema; the most popular and widely implemented ones evolved into ArcGIS Solutions. Once you find the solution of your interest, the package downloaded from the solution gallery will include documentation, model and other map artifacts. I will let @JimBarry comment on the future roadmap for railroads data model.
... View more
01-17-2024
07:56 AM
|
0
|
0
|
5116
|
|
POST
|
@JuhaHaanpera Please consider the Gas and Pipeline Referencing Utility Network Foundation that provides more comprehensive modelling and analytical capabilities using ArcGIS Utility Network with an option of ArcGIS Pipeline Referencing. This solution may be used for natural gas, petroleum liquids and hydrogen as well. A good place to start will be reviewing the business requirements and aligning with the most appropriate solution functionality.
... View more
01-04-2024
05:04 AM
|
0
|
0
|
1912
|
|
POST
|
@-ChrisCraig This Help document steps you through Draw measured hatches along lines Blog: ArcGIS Pro symbology for the Civil 3D objects: working with LYRX files The techniques described can be used to symbolize mile markers for a route.
... View more
12-26-2023
04:45 AM
|
0
|
0
|
2469
|
|
POST
|
@TravisSmith9 The SDR attribute has come up during data mapping/migration at other organizations as well. Some clients see this as a calculated ratio, that can be derived as and when needed. While others have the need to persist this data, and have added a custom field to Pipelineline feature class.
... View more
12-21-2023
02:10 PM
|
0
|
0
|
1574
|
|
POST
|
Very interesting question! Glad that you started this thread @DasheEbra Here's my take on this: Utility Network = ArcGIS Utility Network product Utility Network is the ArcGIS product focused on network solutions for electric, gas, and water utilities, architecture, engineering, construction (AEC), and telecommunications industries. The Helpful Utility Network Links provided by @VanessaSimps applies to ArcGIS Utility Network. Network Management = generic theme, model, solution, technique to manage any network. Network Management is a theme and not an ArcGIS product. There are several ArcGIS products (not a comprehensive list) that offer network management capabilities like: ArcGIS Utility Network ArcGIS Network Analyst ArcGIS Trace Network ArcGIS Pipeline Referencing ArcGIS Roads & Highways ArcMap Geometric Network (legacy) Arc Hydro etc.
... View more
12-21-2023
01:58 PM
|
1
|
0
|
1214
|
|
POST
|
@PeteJordan My guess is the process was developed long time back and seems high overhead to maintain. Recommend creating an m-aware feature class and using the standard LRS route editing tools to update feature geometry and attributes. Sorry I don't have a direct answer to your cache issue but think there is a more efficient way to do the same.
... View more
12-20-2023
03:16 PM
|
0
|
1
|
5217
|
|
POST
|
@PeterStiegler2 This is a data anomaly as an LRS route by definition has measure values that are strictly increasing or decreasing monotonically. Consider the following options to model this correctly: If this is the only instance, have an analyst research the data. If there is no documentation or authoritative record, remove the faulty calibration point with 101.183 measure and re-calibrate the route. Split the route at calibration point with 101.183 measure. This will create 2 monotonic routes. Use LRS modelling concepts like Line Network, Station Event if this issue is more prevalent and needs a system level handling. A solution upgrade as in ArcMap to ArcGIS Pro, is typically a significant effort and investment. I highly encourage organizations to clean up the data along the way, as much as possible. Pushing the data as is with their flaws, is a missed opportunity.
... View more
12-19-2023
04:42 AM
|
1
|
0
|
1589
|
|
POST
|
@GraemeBrowning_Aurizon I believe this is unexpected behavior. Recommend to trace back the configuration of the networks and the route loading process. Conceptually, LRS data model allows you to have multiple LRS networks. After configuration on the LRS networks, you should verify the dLRSNetworks domain. 'The Network ID field is registered with the dLRSNetworks coded value domain when the LRS is created.' After, Append Routes or Create Routes verify the Centerline Sequence table records. 'The combination of the network ID and route ID creates a way of uniquely identifying each route in the LRS. The use of the network ID helps differentiate between LRMs, as route IDs may not be unique across networks.' If you generated Calibration Points, verify the Network ID field as well. If appending Calibration Points, proper Network ID values should be assigned. 'Calibration points are specific to an LRS Network and comprise the measure component of the LRM.'
... View more
12-15-2023
09:00 AM
|
0
|
0
|
1348
|
|
POST
|
@GraemeBrowning_Aurizon Interesting use case! Key requirements: LRS Line Network (primary) LRS Derived Network (secondary) Only a subset of routes group to form a line (consider the % of this subset) Refer to the LRS Network concepts and the corresponding configuration options in the LRS Network toolset. The configuration applies at the feature class level and there is no differentiation at the record level. Options to consider: Model all routes in LRS Line Network (with lots of "single route lines"). Small overhead if low % May consider adding a flag field for single route lines that can be used to search, apply definition query and run geoprocessing on specified selections as applicable. Split records into multiple network feature classes one as LRS Line Network and second as non-line LRS Network. This option has its own overhead but may make sense if high % of such records.
... View more
11-27-2023
06:21 AM
|
1
|
0
|
1745
|
|
BLOG
|
Hello @RobertArens Here are my thoughts: Going strictly by the verbiage referenced, no patching would include security patches. So, you may run into the risk of non-compliance with organizational security polices. The retire policy is similar to other technology companies like Microsoft, Oracle, Google. However, there have been special circumstances where Esri has issued patches due to the extreme nature of the security vulnerability and the wide impact to users (for e.g. log4j). This is more of an exception and not the norm, so suggest not relying on this practice. Having said that, you can certainly raise the matter with your Esri Account Representative and seek specific guidance. Secondly, you should also raise the concern with the vendor/creator of the ArcMap extensions. Any software maintenance plan on the extensions should have a roadmap for porting to ArcGIS Pro. You can certainly consider additional support contracts but my advice is that funds are better used towards a future state with ArcGIS Pro based tools versus maintaining legacy tools.
... View more
11-15-2023
01:46 PM
|
0
|
0
|
6334
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 4 weeks ago | |
| 1 | 3 weeks ago | |
| 1 | 4 weeks ago | |
| 1 | 06-17-2026 06:24 AM | |
| 1 | 05-29-2026 07:53 AM |