Latest Contributions by AyanPalit

‎12-19-2023

@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.

‎12-15-2023

@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.'

‎11-27-2023

@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.

‎11-15-2023

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.

‎11-15-2023

@JummaKhan Looking at the coordinate values, you can try switching them as: 43.287, -79.878

‎11-13-2023

@RobertArens Similar question discussed at: https://community.esri.com/t5/arcgis-pro-questions/will-pro-honor-import-mxd-functions-after-arcmap/m-p/1338413#M74037 What happens once ArcMap is in Mature phase - this is explained at ArcGIS Product life cycle support policy Keep an eye on ArcMap Continued Support page.

‎11-02-2023

If you have My Esri access, you can directly download patches: https://support.esri.com/en-us/patches-updates/2023/arcgis-pro-3-1-patch-3-3-1-3-announcement

‎11-02-2023

@RBCopland ArcGIS Pro cannot automatically check for an update when using a checked out license (offline mode). Suggest check: ArcGIS Pro > Project > Licensing > Settings. If Authorized to work offline, return checked out license and run ArcGIS Pro with the appropriate licensing portal. You may need to consult your co-worker or the GIS administrator.

‎11-02-2023

@BrianBulla As a first step, suggest looking at the editor tracking fields, settings and if they are mapped, configured correctly. You may try disabling and re-enabling them as well.

‎11-02-2023

@GerardAshton While sketching the second segment, you can use the right-click context menu and use Distance: Reference: https://pro.arcgis.com/en/pro-app/latest/help/editing/trim-or-extend-an-unfinished-line.htm https://pro.arcgis.com/en/pro-app/latest/help/editing/trim-a-polyline-feature.htm

‎10-31-2023

@GraemeBrowning_Aurizon The main requirement here is to rename Lines and Routes. At ArcGIS Pro 3.1, this is possible through: Rename Route tool Note: When a route or a line is renamed using rename tool, all related records are changed across all time slices. In earlier versions: Rename of Line is not supported Rename of Route supported through Reassign Route Note: When a route is renamed using reassign, all related records are time sliced and the history of the name change is preserved. The error reported during Retire+Create is expected as Retire operation preserves the history and sees the conflict at the Create step. You are already thinking in these terms - my comments are just a confirmation. If the Rename Route tool cannot be used, the only supported workflow is as you stated (with minor changes as below): export the affected routes and related records from Enterprise Geodatabase to file geodatabase fix Linename / Routename values in file geodatabase delete affected routes from the Enterprise Geodatabase reload from the file geodatabase

‎10-24-2023

@GerardAshton Thanks for the comments. A recent blog posting related to the National Spatial Reference System (NSRS) modernization: Prepare your data for the National Spatial Reference System modernization of 2022 in the U.S. Additional notes on Using Foot as Linear Measure Units

‎10-19-2023

@Anonymous User I will add a few notes to the technical explanation by @JFarmer Are we required to have branch versioned databases just to use Workflow Manager? No Traditional versioning is fully supported, although certain newer ArcGIS solutions strictly use branch versioning. Switching to branch versioning should have clear drivers (doesn't look like you have any) and be a well-thought out process (plan, design, test, implement). Are we able to at least deploy basic workflow manager functions while on a traditional versioning? Yes only few step types are not supported, like: Create Version Job Version Cleanup figure out how to maintain both traditional DBs and somehow copy data to/from branch DBs just to use workflow? This will over-complicate the architecture and introduce unnecessary overhead. This is not a best practice; the alternate to handle version management steps through ArcGIS Pro Tasks or manually is much simpler.

‎10-19-2023

@OliviaGill3 Tolerance and Resolution for XY, Z and M are set based on the spatial reference at the asset package schema of Utility Network. These settings are preserved when configuring the Utility Network by Stage Utility Network—Creates the utility network dataset Apply Asset Package—Configures an input utility network using an asset package The XYZM tolerance and resolution may be modified using the Change Asset Package Spatial Reference tool that is part of the Utility Network Package Tools to automate the process of creating and configuring a utility network using asset packages for specific industry domains. Reference: Utility network creation and configuration Utility Data Management Support tools - 2.9.3/3.1.1 Release

‎10-18-2023

@sinekelly1410 Interesting problem and I anticipate many variation edge cases for instance: This is a common problem and may be addressed in different ways depending on the unique requirements. It will help if you post sample screenshots. Simplistically, Identify and select the lines that are incorrect Use the Flip Line geoprocessing tool Use ArcGIS Pro Editing tools to Reverse the direction of a polyline

My Ideas

Latest Contributions by AyanPalit

Re: Migrating non monotonic routes for ArcGIS Pro

Re: LRS Dataset with multiple networks has some "null routes"

Re: LRS Line Network where some Routes not part of Line

Re: I Can't Live Without ArcMap because...!!! - plugins, add-ons, and Jerry Garcia

Re: Long Lat Help

Re: I Can't Live Without ArcMap because...!!! - plugins, add-ons, and Jerry Garcia

Re: ESRI update service is temporarily unavailable

Re: ESRI update service is temporarily unavailable

Re: Editor Tracking not timestamping properly

Re: Extend a line by a distance

Re: Invalid line name attribute. The line name must match the existing line name associated with the route name.

Re: International Feet vs. US Feet measurements

Re: Brach Versioning Requirement

Re: Utility Network tolerance value

Re: Ensure all lines follow the same line direction

Re: Utility and Pipeline Data Model 2026 is Releas...

Re: GeoAI for Roof Damage Delineation: Five Lesson...

Re: It is too easy to accidently make an edit in t...

Re: Utility and Pipeline Data Model 2023 is Releas...

Re: ArcGIS Pro 3.7 Update, Error 126

GIS Leadership User Group

Roads and Highways User Group (RHUG)