A feature dataset is a collection of related feature classes that share a common coordinate system. Feature datasets are used to facilitate creation of controller datasets (sometimes also referred to as extension datasets), such as topology, utility network or pipeline referencing. Feature classes that are to be included in an extension dataset are first organized into a feature dataset.
To support service-based editing of your data in Pipeline Referencing, certain feature classes in the LRS data model must reside in a feature dataset in your geodatabase. If the feature classes and tables are modeled in advance, the following feature classes must be contained in a feature dataset: Centerline, Calibration Points, Redline, Networks, Events, and Intersections.
Reference: LRS information model
When a feature dataset is created, you must define its spatial reference. This includes the coordinate system, either geographic or a specific projection, as well as coordinate units and tolerances for x-, y-, z-, and m-values. All feature classes in a feature dataset must share a common coordinate system, and the x,y coordinates of their features should fall within a common spatial extent. When you create a feature class in an existing feature dataset, the coordinate system is inherited from the feature dataset.
Since measures and their precision are critical to the accuracy of any linear referencing method (LRM), the spatial reference, tolerance, and resolution settings for all these feature classes must align. This ensures that geometry and measures for routes, events, and intersections are correct in a linear referencing system (LRS) and remain in alignment. If any of the centerline, calibration point, redline, network, event, or intersection feature classes are modeled before they are registered with the LRS, ensure that the tolerance and resolution settings match.
Reference: Tolerance and resolution settings
At ArcGIS Pro 2.6, you can now configure LRS intersection feature classes as well as generate and update intersections. The example below shows intersection of an LRS route with railroad layer.
The required fields for LRS intersection class are listed in the following table.
Field | Data Type | Description |
Intersecting ID | Guid | The name of the intersection ID field. |
Intersection Name | Text (1000) | The name of the intersection. |
Route ID | Text (1000) | The unique ID of the route. |
Feature ID | Text (1000) | The unique ID of the intersecting feature. |
Feature Class Name | Text (150) | The name of the intersection point feature class. |
From Date | Date | The date the network became active. |
To Date | Date | The date the network was retired. |
Measure | Double | The measure on the dominant route where the intersection is located. |
Here is a sample attribute table for the intersection of an LRS route with railroad layer.
At ArcGIS Pro 2.8, the redline feature class that is a APR information model core object, must be z-enabled and cannot be m-enabled.