Latest Contributions by AyanPalit

‎08-21-2025

There was a similar BUG-000160398 that was resolved at Pro 3.2. Possible this is remnant of that or new issue.

‎08-20-2025

@Kevin_Andras What is your coordinate reference system and default linear units? In map views, ArcGIS Pro sets the elevation units to the linear units defined by the map's vertical coordinate system, if it exists. If a vertical coordinate system is not assigned, it is set to the linear units defined by the map's x,y coordinate system. REF: https://pro.arcgis.com/en/pro-app/latest/help/editing/edit-vertex-z-values.htm

‎08-20-2025

@VenkataKondepati Enterprise geodatabases are supported in the following relational database management systems: IBM Db2 Microsoft SQL Server Oracle PostgreSQL SAP HANA While there is no documentation of supporting Apache Sedona, innovators are always welcome to tinker and test. It will be interesting to hear other responses on your inquiry!

‎08-20-2025

@JurajKrumpolec Thanks for the idea - I see a lot of value in your idea and personally use the steps outlined. Have you explored Data Engineering ? It's newish but very nifty in providing these data insights and more.

‎08-18-2025

@NickKoopman Each organization's environment is unique. I can only provide generic guidance based on the limited information available. Direct access to the database is not available/allowed through ArcGIS Web Adaptor in typical branch versioned environment. Someone must explicitly open the database access through the firewall. There are additional checks that may be implemented: Implement reverse proxy in a DMZ Protect Default Version in the enterprise geodatabase Apply fine grained capabilities for external users to only edit in named version. It is possible to restrict users from creating version, deleting version, reconcile and post to Default version. Good references at ArcGIS Trust Center: ArcGIS Enterprise implementation guidance ArcGIS Architecture Center: Working in secure environments

‎08-15-2025

@NikkiCronyn You will benefit from the following resources at the ArcGIS Architecture Center. Selecting a deployment pattern for imagery data management Selecting a deployment pattern for self-service mapping Each topic covers SaaS and on-premise deployment patterns.

‎08-14-2025

Quoting Dr. Malcolm (Jurassic Park): "Your scientists were so preoccupied with whether they could, they didn't stop to think if they should." @CalvinHarmin Technically it is possible to have mixed Traditional and Branch versioned objects in an EGDB. In my implementation best practice, I would not recommend a mixed transaction model. It adds to user confusion and system overhead with data maintenance as well as system integrations.

‎08-14-2025

@NickKoopman Switching to branch versioning should have clear drivers and be a well-thought out process (plan, design, test, implement). During planning, revisit the architecture and stated database setup. Some key considerations: Organization size and GIS data volume Purpose: What workflows will your data support User types: Office GIS analysts, mobile workers, public users, decision-makers — each has different performance and access needs. Data update frequency: Is it real-time, daily batch, or occasional? Performance: acceptable performance criteria System Integration Security and Access Control As stated by @DavidSolari branch versioned geodatabase is more efficient. Due to this many organizations have collapsed the data architecture layers. Small organizations use a single branch versioned geodatabase to support Editing, Viewing and Field Work. Since branch versioned editing is done through feature services, the same database can be use for viewing through other map services. Field work can be supported using Feature Sync through Feature Services. You may not need the traditional geodatabase replication in a future state with slimmer data architecture. Consider these options, along with your organizations unique requirements to come up with a design that works well.

‎08-11-2025

@ElsitMandal1 Thanks for posting the screenshot; this helps. Suggest reviewing the LRS Locks table and correlate with the documentation. If there's an edit on the shared centerline, the LRS Locks table will show locks on both Routes. This is expected behavior. If only event on North south route is edited and has an event lock, with no locks on the route itself. Then the East west route (with shared centerline) should not have a lock. Try releasing the event lock and check if that resolves the issue. Reference: Conflict prevention > Conflict prevention during centerline editing

‎08-11-2025

@ElsitMandal1 I can just guess based on the description; it would help if you post a screenshot. Note that locks are at the route level - not the centerline. That's the only way to maintain the integrity of calibration on routes. So a shared/concurrent centerline, even small segments, would lock the corresponding route(s).

‎08-11-2025

@ElsitMandal1 Where concurrent routes exist, routes are locked based on common centerlines. Reference: Conflict prevention > Conflict prevention during centerline editing

‎08-01-2025

@LRoberts_RDM Quick follow-up, please post a screenshot of the Prune Branch History tool parameters. Specifically, the Only Prune System Tables parameter. Do you see any difference checking/unchecking this option.

‎07-28-2025

@DEAF_PROBERT_68 You may try Define Projection or Project or a combination of both Projections and Transformations tools. The following articles can be useful: Identify the spatial reference, projection, or coordinate system of data Data does not line up when the correct datum transformation is applied

‎07-28-2025

@LyonMNGIS Ok, I now better understand that you want to selectively enable Editor Tracking and the GP is not letting you do so. All my use cases involve tracking all the fields for full editor tracking. As a workaround, could you try Enabling and then use Disable Editor Tracking, to remove the fields you don't want tracked.

‎07-28-2025

@LyonMNGIS The basic concept of editor tracking requires storing user and time of creation or update of features. When Enable Editor Tracking Geoprocessing tool, you can choose ArcGIS defaults as below or point the tool to specific fields in your schema. created_user (Text) created_date (Date - low precision) last_edited_user (Text) last_edited_date (Date - low precision) So Editor Tracking must be mapped to 4 fields; either ArcGIS defaults or user chosen. There is really no way to have editor tracking, leaving the fields empty.

My Ideas

Latest Contributions by AyanPalit

Re: Edit Vertices - default z value units stuck in feet

Re: Edit Vertices - default z value units stuck in feet

Re: Apache Sedona Database Support from ArcGIS Pro

Re: Show sum of area and length for selected features

Re: Branch Versioning on Production Databases

Re: Cloud Storage Solutions for Imagery & Geodatabases with Version History

Re: Branch Versioning on Production Databases

Re: Branch Versioning on Production Databases

Re: Roads and Highways Locks

Re: Roads and Highways Locks

Re: Roads and Highways Locks

Re: Prune Branch History Not Working

Re: From State Plane projection to UTM Zone 13N Question

Re: Enable editor tracking geoprocessing tool no longer allows <None> for creator or editor

Re: Enable editor tracking geoprocessing tool no longer allows <None> for creator or editor

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)