Latest Contributions by AyanPalit

‎06-05-2024

The two United States federal agencies, National Institute of Standards and Technology (NIST) and National Oceanic and Atmospheric Administration (NOAA) retired use of the “U.S. survey foot” on December 31, 2022. 1 International foot = 0.3048 meters 1 US survey foot = 0.3048006096 meters To most people, the difference is barely discernible and equates to approximately one-eighth of an inch per mile. However, surveyors who measure over long distances, the impact can be significant. The difference starts showing up on 2nd decimal place for lengths over 10,000. If US foot was used to survey distances, apply a multiplication factor of 1.000002 to convert to International foot. Length(meters) USS-FT Int-FT USS-FT Int-FT 1 3.280833333 3.280839895 1.00 1.00 100 328.0833333 328.0839895 100.00 100.00 1,000 3280.833333 3280.839895 1,000.00 1,000.00 10,000 32808.33333 32808.39895 10,000.00 10,000.02 100,000 328083.3333 328083.9895 100,000.00 100,000.20 ArcGIS Pro, starting at version 3.0 has both distinct foot definitions and will continue to support US survey foot in the foreseeable future. It is up to users to review their data, organizational standards and make decisions that best serve their business/compliance requirements. Further reads at: Thinking on our feet: December 31 marks the end of the U.S. survey foot Change Is Afoot with the US Survey Foot

‎06-03-2024

Overview ArcGIS Roads and Highways (R&H) provides a GIS-enabled, linear referencing data management solution for transportation organizations. It offers the following: LRS information model & web services Configuration, loading & transformation tools LRS web widgets and templates LRS Network and Event editing LRS data products Recent News This resources blog is updated for the latest ArcGIS Pro 3.7 and ArcGIS Enterprise 12.1 releases of ArcGIS Roads & Highways (May 2026). What’s new in ArcGIS Pro > Production > Roads and Highways What’s new in R&H Server Location Referencing Issues Addressed What’s new blog Event Editor deprecation Roadway Reporter deprecation Roads and Highways Desktop R&H extension to ArcGIS Pro: Getting Started LRS Data Model > Information Model Package Create LRS Components Event Behavior Route Editing Event Editing Reporting tools > LRS data products Conflict Prevention Location Referencing Toolbox R&H tools branch versioning support R&H tools filter and selection support R&H tools licensing Roads and Highways Enterprise R&H Server extension to ArcGIS Enterprise: Getting Started Experience Builder LRS widgets Event Editor (legacy app and is replaced by Experience Builder LRS widgets) R&H REST API R&H REST API Sample Complementary tools ArcGIS Workflow Manager ArcGIS Data Reviewer System & Installs System Requirements > ArcGIS Pro | ArcGIS Enterprise Install ArcGIS Pro Install ArcGIS Enterprise Build Experience Builder App > Configure Location Referencing widgets Configure Event Editor Web Application (legacy app) Enterprise Pro Release Date Pro Support 12.1* 3.7 May-2026 May-2029 12.0 3.6 Nov-2025 Nov-2028 11.5* 3.5 May-2025 May-2028 11.4 3.4 Nov-2024 Nov-2027 11.3* 3.3* May-2024 May-2027 11.2 3.2 Nov-2023 Nov-2026 *Long-Term Release ArcGIS Pro Life Cycle Other Resources Roads and Highways Training web course Manage address and roadway characteristic data together Linear referencing in ArcGIS Field Maps Branch Versioning ArcGIS Pro Terminology Guide R&H Enhancement Requests

‎05-31-2024

Sample LRS data model based on ArcGIS R&H can downloaded from Roads and Highways Information Model Updated this older thread: FYI @PradeepNegi

‎05-30-2024

‎05-30-2024

LRS Event data collection using ArcGIS Field Maps in disconnected environment and sync back to the enterprise geodatabase.

‎05-29-2024

The ArcGIS Roads and Highways Information Model is the core structure for linear referencing data. The package available for download in this blog, can be used to explain the LRS data model as applicable to R&H. This is intended to explain and understand the basic building blocks of the solution as detailed below. The package contains the following items: File geodatabase containing LRS model and configuration LRS report containing schema details and LRS configuration metadata The model evolves as new capabilities get added. Hence, the following packages are being provided corresponding to major, long-term releases: R&H Information Model for ArcGIS Pro 3.3: LRS33RH_Package.zip R&H Information Model for ArcGIS Pro 3.1: LRS31_Package.zip LRS Model The LRS Schema is comprised of the following feature classes and tables: Centerline: Centerline Calibration Point: Calibration_Point Redline: Redline Centerline Sequence: Centerline_Sequence (table) The following LRS entities can be added on as needed for the modelling exercise: Networks Line Network: Line_Net Derived Network: Derived_Net (optional) Events Point Event: Point_Ev Range Event: Range_Ev Station Equation Event: Station_Ev (optional) Intersection Hydrology Intersection: Hydro_Int uses ‘GeoLayers/Rivers’ as the intersecting layer (optional) Address Address Range Event : AddressRange_Ev uses ‘SiteAddressPoint’ as the Site Address Feature (optional) LRS Report The LRS Report is comprised of the following: LRS33RH: schema report (HTML, json, PDF, Excel formats) lrs33RH_Metadata: LRS configuration metadata (XML format) Conclusion You can use R&H tools to create or load data to the geodatabase included, to further your understanding and proof of concept efforts. R&H’s flexible information model allows you to model your own network, event and intersection feature classes. The package is not intended to be organization specific or implementation ready. However, it does provide the core structure to get you started. More comprehensive data models and their implementation practices can be found at Esri Community and related resources.

‎05-29-2024

The ArcGIS Pipeline Referencing Information Model is the core structure for linear referencing data. The package available for download in this blog, can be used to explain the LRS data model as applicable to APR. This is intended to explain and understand the basic building blocks of the solution as detailed below. The package contains the following items: File geodatabase containing LRS model and configuration LRS report containing schema details and LRS configuration metadata The model evolves as new capabilities get added. Hence, the following packages are being provided corresponding to major, long-term releases: APR Information Model for ArcGIS Pro 3.3: LRS33PR_Package.zip APR Information Model for ArcGIS Pro 3.1: LRS31_Package.zip LRS Model The LRS Schema is comprised of the following feature classes and tables: Centerline: Centerline Calibration Point: Calibration_Point Redline: Redline Centerline Sequence: Centerline_Sequence (table) The following LRS entities can be added on, as needed for the modelling exercise: Networks Line Network: Line_Net Derived Network: Derived_Net (optional) Events Point Event: Point_Ev Range Event: Range_Ev Station Equation Event: Station_Ev (optional) Intersections Hydrology Intersection: Hydro_Int uses ‘GeoLayers/Rivers’ as the intersecting layer (optional) LRS Report The LRS Report is comprised of the following: LRS33PR: schema report (HTML, json, PDF, Excel formats) lrs33PR_Metadata: LRS configuration metadata (XML format) Conclusion You can use APR tools to create or load data to the geodatabase included, to further your understanding and proof of concept efforts. APR’s flexible information model allows you to model your own network, event and intersection feature classes. The package is not intended to be organization specific or implementation ready. However, it does provide the core structure to get you started. More comprehensive data models and their implementation practices can be found at UPDM, PODS and related resources.

‎05-28-2024

@AbdulAzeezLawal Great question and you are in the right forum! You will find posts from YPN Community members on this topic. Some share their experiences through blogs and I find them a good read with relatable tips. 30 Networking Tips for Introverts when Attending Conferences The Power of Networking at Conferences: For Students and Emerging GIS Professionals Building Your GIS Network: 5 Tips for International Students Watch the community space as conference specific information is posted ahead of key events!

‎05-20-2024

@SehmiloSheriff Good question on whether to use first name or last name when greeting. Both are common practices and acceptable. I think this depends on cultural norms and familiarity with the person. In some parts of the world, last name is always preferred in formal communications. For example greet as: "Good morning Mr Sheriff, Hope you are well.' I have seen keeping this convention, even if you have known the person for a long time. I always address my teacher or doctor as Mr. LastName or Dr. LastName. However, if you really have a personal relationship in addition to the professional terms, you may use first name. It is a matter of mutual respect and as long other person is OK with it. In some parts of the world, first name is preferred and is considered more direct and easy to form working relationships. For example greet as: "Good morning Sehmilo , Hope you are well.'

‎05-01-2024

@MirekGroen Looks like you are following the documentation but seems like the zipped GDB may not be formatted in a way where the source route feature class is not found. Can you post a screenshot of the GDB with its contents or upload a sample?

‎04-26-2024

@BrianVann This is a common linear referencing challenge that can be solved reasonably well with some guided processes. Let's start with key references to the Locate Features Along Routes help documentation: Crash data may often have just coordinates to locate them on a map. It is desirable to have a Route attribute collected with the crash data. Or perhaps a post-process to enrich the crash data with a unique route attribute. The above process primes the data to then allow for a selective and more accurate process. You can have a recursive script to group the crash points by the route, and then use Locate Features Along Routes tool for each set.

‎04-02-2024

@AlisonWieckowicz I think you are on the right track in unravelling this. Here are three concepts to track: LRS Versioning Conflict Prevention All of these existed in ArcMap and they are in ArcGIS Pro but the nuts-n-bolts have changed under the hood. Hope this helps. Please post your updates.

‎04-02-2024

@AlisonWieckowicz you raise a good question. LRS conflict prevention in ArcGIS Pro is dependent on the geodatabase being branch-versioned. Not sure, if this was a first-time migration from ArcMap LRS to ArcGIS Pro LRS. During the process, it is recommended to also unversion (traditional) and version (branch). Followed by enable conflict prevention. Once the LRS service is published and added back to ArcGIS Pro, the Locks tool becomes active. Click on Locks tool to display locks table - confirming conflict prevention in enabled.

‎03-19-2024

@rohanrajan_hms The Assembly feature class in an Utility Network domain, is a conceptual representation that would contain other physical features. Assembly—Represents point features that contain other features. As with device features, assembly features are compact features, but they differ in that assemblies contain other significant devices. Assemblies are useful to show a single symbol on the map yet model the internal features and their connections. You can view the internal features of an assembly on the map or in the diagram view. Examples of assembly features are switchgear, transformer banks, and pump assemblies. Physical Assets in a domain network are typically stored in device, line and junction feature classes. There are instances where an organization may not have the assembly details or the desire to model all the components. In that case the entire 'enclosure' (which is physical) is modelled as the assembly (leaving out the internal physical details). Other supporting physical assets are modelled as part of the structure network. Structural attachments are typically stored in boundary, line and junction feature classes.

‎03-18-2024

@Acharya Great question and there are several blogs and help documentation that will provide detailed explanation. 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. Utility and Pipeline Data Model = UPDM is a template data model for gas and hazardous liquid pipelines. UPDM is included with the Gas and Pipeline Referencing Utility Network Foundation solution. The model has multiple implementation patterns based on business requirements: Utility Network (Gas Asset Package) ArcGIS Pipeline Referencing (information model) Utility Network and ArcGIS Pipeline Referencing

My Ideas

Latest Contributions by AyanPalit

Using Foot as Linear Measure Units

ArcGIS Roads and Highways – Useful Resources

Re: Sample LRS data model

What's New in ArcGIS Roads and Highways and ArcGIS Pipeline Referencing (May 2024)

LRS Sync Service

Roads and Highways Information Model

Pipeline Referencing Information Model

Re: Mastering the Art of Professional Email Communication: A Guide to Writing with Purpose and Professionalism

Re: Mastering the Art of Professional Email Communication: A Guide to Writing with Purpose and Professionalism

Re: Append Routes issue with Rest API

Re: Event LRS and Spatial Join Discrepancies

Re: How to verify status of conflict prevention in ArcGIS Pro 3.2

Re: How to verify status of conflict prevention in ArcGIS Pro 3.2

Re: Utility Network Assembly

Re: Difference between Utility Network and UPDM

Re: Z factor in Geometries

Re: Seeking GPS Units Recommendations

Re: GIS Career Pathways: Product Management

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

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

Roads and Highways User Group (RHUG)

GIS Leadership User Group