Creating a new LRS

The linear referencing system (LRS) extends the geodatabase to provide additional capabilities for linear referencing, including support for multiple linear referencing methods (LRMs), event location management, and a time-aware linear referencing system (LRS).

1. Right-click the target geodatabase and click New > Advanced Linear Referencing System.
   • In ArcCatalog, the geodatabase is in the Catalog tree.
   • In ArcMapp, the geodatabase is in the Catalog window.

   The Advanced Linear Referencing System setup wizard appears.

   

   Nota:

   • The number of steps in the wizard are different depending on whether the Create required tables and feature classes check box is checked or not checked. If the check box is not checked, there are six steps in the wizard. If the check box is checked, there are seven steps.
   • If any of the required tables or feature classes are not in your target geodatabase, the Create required tables and feature classes check box should be checked.

2. Haga clic en Siguiente.
3. Name the new LRS and provide a brief description.

   

If none of the LRS minimum schema items are present in the target geodatabase, the Create required tables and feature classes check box is checked and those minimum schema items are created with the LRS. If any of the minimum schema items are present, the check box is not checked.
4. Click Next.

   The Step 2 of 7, Minimal schema dialog box appears.

   

5. Name the minimum schema items and select the tolerance and spatial reference.
   1. Choose the name for each minimum schema item.
   2. Select the x,y- and z-tolerance for the centerline, calibration point, and redline feature classes.

      Enter the values by typing in the text boxes for X-Y Tolerance and Z Tolerance, or by selecting the tolerance values from an existing feature class, such as your source routes, by clicking the ellipsis (...) button to the right of the text boxes.

      Nota:

      Make sure the tolerance settings of your LRS match those of your source route feature class. This ensures the shape and length of your routes are the same in your LRS Networks as in your source route feature class. For more information about tolerance and resolution in Esri Roads and Highways, see LRS data model.

   3. Select the spatial reference of your required tables and feature classes by clicking the ellipsis (...) button next to the Spatial Reference field.

      If you selected an existing feature class for your x-y and z tolerance in the previous step, the spatial reference of that feature class is automatically selected for you. The spatial reference of your LRS should match the spatial reference of your source polyline route feature class.

6. Click Next.

   The Step 3 of 7, Schema dialog box appears.

   

   Nota:

   If you checked the Create required tables and feature classes check box, you can use the default values for steps 3 and 4 in the LRS setup wizard.

7. Map the LRS schema to the proper data elements.

   See LRS data model to learn about the data elements used in the LRS.

8. Click Next.

   The Step 4 of 7, Field Mapping dialog box appears.

   

9. Map fields to LRS data elements.
   1. Choose LRS data elements using the Table/Layer drop-down arrow.
   2. Map the LRS fields to the data element field names using the Mapped To drop-down arrow.

      See LRS data model to learn more about the LRS data elements.

10. Click Next.

    The Step 5 of 7, Locks and Notifications dialog box appears.

    

11. If the LRS needs conflict prevention, check the Enable Conflict Prevention check box and choose the lock root version from the list of versions in the Lock Root Version drop-down list. If lock transfers between users will be allowed, check the Allow Lock Transfer check box. For more information on conflict prevention, see Conflict prevention.

    This step is only available if the LRS is created in a multiuser geodatabase environment.

    The Step 6 of 7, Elevation Dataset Configuration appears.

    

12. If a digital terrain model, digital elevation model, or similar raster dataset is going to be used to calculate the z-values of centerlines when creating and editing them in Esri Roads and Highways, configure the Elevation Dataset Configuration. For more information about using z-values on centerlines, see Elevation data on routes.

    This step is not required if an elevation model is not going to be used with your LRS.

    1. Check the Use an elevation dataset to populate Z values when editing centerlines check box if an elevation model is going to be used.
    2. Click the ellipsis (...) button to the right of the Raster Dataset field to select your elevation model.
    3. Type the Z factor for the elevation model in the text box.
    4. The Centerline Z unit of measure field is populated automatically based on the spatial reference of the centerlines in the LRS.

    Nota:

    When an elevation model is configured with the LRS, the z-values on centerlines are only populated using the elevation model when creating and editing centerlines within an edit session. If any of the settings, such as Z factor, are changed, the new settings will only be applied to edits made moving forward. If you want to use the elevation model to populate the z-values on the routes being loaded into your LRS, consider using the 3D Analyst extension to populate the z-values on the routes before loading them into Esri Roads and Highways.

    To use the configured DEM to apply z-values to created and edited centerlines in the LRS, the 3D Analyst extension must be installed and enabled on your machine.

13. Click Next.

    

14. Click Finish to finish creating the LRS and close the wizard.

    Nota:

    If your LRS is in a multiuser geodatabase, the following tables should remain unversioned: Event Behavior, Locks, Lookup, and Metadata.

    The Question message appears asking if you want to create a new network.

    

15. Choose one of the options and close the LRS setup wizard.
    • Click Yes to create a new network.
    • Click No to close the LRS setup wizard and return to ArcMap or ArcCatalog.