Latest Contributions by AyanPalit

Refer to Editor Tracking detailed documentation. ... View more

Welcome Mog - great to have you as part of the  Community! ... View more

@Cristian_Galindo A good place to start is the LRS Network definition and requirements. The  Gas and Pipeline Data Management for ArcGIS Enterprise includes two LRS networks: Engineering Station Network Continuous Station Network The implementation patterns may be: Use only the Continuous Station Network for simple linear referencing use case where there is no break in measures. In this case, the LineID, LineName and LineOrder fields are not needed. Use Engineering Station Network as the primary line network and Continuous Station Network as its derived counterpart. Engineering stationing may have a gap in measure at the junction of two routes that are part of the came line. This point is often referred as Station Equation. In this pattern,  the fields of LineID, LineName and LineOrder are required and are used to generate/ derive the roll-up of routes to lines.  Another major consideration is, whether you are configuring APR only or APR with a Utility Network. The referenced post and workaround only applies to the APR with Utility Network. For APR only implementation, the Centerline layer in the data model should be used for LRS configuration. The Pipeline Line, Device and Junctions may be configured as LRS events and managed as such.  The implementation pattern of  managing Pipeline Referencing and a Utility Network together has different data requirements and configuration process as in the reference link.   #ArcGIS Pipeline Referencing #electric and gas utilities‌ #gas and pipeline enterprise data management‌ #oil and gas ... View more

Maintaining the version compatibility is an important step and will help streamline the configuration process. ArcGIS Pro, ArcGIS Enterprise and the corresponding Event Edit Web App versions must be in sync. A compatibility matrix can be found at  ArcGIS Pipeline Referencing - Useful Resources ... View more

This is a common issue users run into if the source calibration point data is not in sync with routes data. I believe, you are on the right track with troubleshooting. Review the attributes of the calibration points per Nathan. Also, check the geometry of the route, where you attempted to add calibration points manually. Feel free to post step-by-step screenshots for a closer review.   ... View more

Cristian_AndresGalindo_Londoño The recommended APR upgrade pattern includes migration to Branch Versioning. As noted previously, there are several/significant changes to the geodatabases: Schema Change Version Transaction Model Archiving Model LRS Registration You can retain a backup of the legacy database. As part of the upgrade you are setting up a new/different versioning model that includes archiving. A careful review of branch versioning documentation, planning and execution is needed as part of the upgrade.       ... View more

Cristian_AndresGalindo_Londoño Is this a production environment with archiving and versioning enabled? Are you using traditional versioning? There are many considerations for upgrades to a production environment. which need careful planning and execution. I feel this goes beyond the Community forum and recommend additional review through other channels like Esri Tech Support.      ... View more

Cristian_AndresGalindo_Londoño if you mean versioning history, best to reconcile and post all pending edits as suggested in prior response. If you have editor tracking enabled, the metadata captured as attributes will be preserved through the move.   ... View more

Cristian_AndresGalindo_Londoño Moving Feature Classes (FC) from one Feature Datasets (FD) to another FD is a major schema change. Also, you may have to re-register or validate the FC's registered with the LRS. Due to this, I would recommend to reconcile, post and delete all versions prior to making these schema changes. Either Drag-n-Drop or Python script may be used but best to collapse the versions. Many clients also need to switch from traditional to branch versioning as part of the upgrade. In that case, the geodatabase will need to be unversioned, make changes as required for branch versioning and then register as branch version.    ... View more