| CATEGORY | TERM Reference Number | DEFINITION |
| LRS & R&H | ALRS1 | Acronym for the Advanced Linear Referencing System, a linear referencing system implemented by Roads and Highways on the ArcGIS platform that supports multiple linear referencing methods and event measure behaviors. |
| Asset1 | A type of linear referenced event that represents a physical object, such as a sign, guardrail, or bridge. |
| Calibration Point1 | A point feature that defines the measure for a specific locaiton on an LRS route. Roads and Highways uses calibration points to define the measures on the routes. |
| Centerline1 | A polyline feature that defines part (or all) of the geometry of an LRS route. |
| Concurrency1 | Concurrency occurs when two route segments share the same pavement/centerline features. Route segments in a concurrency are called concurrent routes or overlapping routes. |
| Divided Highway2 | A multi-lane facility with a curbed or positive barrier median, or a median that is at least 4 feet in width. |
| Dominant Route1 | In a route concurrent there are at least two routes travelling the same pavement. The one that events are assigned is called the dominant route. In a route concurrency there is only one dominant route. Most DOTs follow the rule that events are associated with dominant routes only. |
| Event1 | Data that is located by its association to an LRS route and measure location. |
| Event Behavior1 | Configuration that defines how event measures and route assoications respond to changes or edits in the LRS network in Roads and Highways. |
| Export Network Service/Tool1 | A web service or geoprocessing tool that enables external systems to synchronize with the Roads and Highways LRS Network to update routes, gaps, concurrencies, and measure translations. Used for system integration. |
| External Event1 | An event that resides outside the geodatabase where the ALRS is configured. |
| External System1 | Databases and other data storage systems of event data that are outside the management of Roads and Highways. |
| Internal Event1 | An event that resides inside the geodatabase where the ALRS is configured. |
| Linear Event1 | An event that represents a segment of a route from a starting measure (or from measure) to an ending measure (or to measure) |
| LRS1 | Acronym for linear referencing system, the method of storing geographic locations by using relative positions along a measured linear feature. |
| LRM1 | Acronym for linear referencing method, a method for defining measurements along linear features for the purpose of linear referencing. |
| LRS Network1 | A collection of routes, measured to a specific LRM in Roads and Highways. |
| Measure1 | Or mile point or milepost. A location along a route based on a distance from a known point of origin. |
| Point Event1 | An event that represents a single point location on a route at a specific measure. |
| RCE1 | Acronym for Roadway Characteristics Editor. This application was renamed to Event Editor at the 10.5 release. It's a web based event editing application included with Roads and Highways. |
| Relocate Event Service/Tool1 | A web service or geoprocessing tool that allows external events to be synced to route edits in Roads and Highways. Used for system integration. |
| Roadway3 | The portion of a highway intended for vehicular use. |
| R&H | Acronym for ESRI ArcGIS Application Roads & Highways |
| Roadway Characteristics3 | Or roadway attributes. A set of attributes characterizing roadways in a highway system. Examples include surface type, number of lanes, and lane width. |
| Route1 | A linear LRS feature defined based on a LRM. |
| Route ID3 | A value to uniquely identify a route. Some DOTs implement an intelligent/descriptive route ID definition by incorporating information about the route type, county, municipality, route number, and directionality while some use sequential numbers or GUIDs (Globally Unique Identifiers) generated in databases to differentiate routes. |
| Route Dominance Rules1 | A set of rules that decide which of the concurrent routes in a route concurrency is the dominant route for events and the rest subordinate route(s). Route dominance rules can be preset in Roads and Highways by using attribute fields in an LRS network or the internal event layers that are registered to the network. |
| Station1 | Reference points that are placed along the horizontal measurement of a route, centerline, or baseline at a regular interval. Station numbers increase from West to East or South to North based on the cardinal direction of the overall highway. |
| Stationing1 | The fundamental system of measurement used by surveyors. For highway projects, a starting reference station is first established and then all distances along the route centerline are measured from that point location. |
| Subordinant Route1 | In a route concurrent there are at least two routes travelling the same pavement. The route that doesn't have events assigned is called a subordinant route. In a route concurrency there is at least one suborinate route. Most DOTs follow the rule that events are assigned to dominant routes only. |
| | | |
| INTEGRATION | System Integration4 | Or integration, a process of linking together Roads and Highways with different computing systems and software applications physically or functionally to act as a coordinated whole. |
| One Way Integration4 | An integration that supports data in Roads and Highways consumed by an external system. |
| Two Way Integration4 | An integration that supports data exchange between Roads and Highways and an external system. |
| Automatic Integration4 | An integration that is carried out by code or computer programs so human interruption is minimal. |
| Manual Integration4 | An integration that is mainly carried out by manual work performed by human beings. |
| Semi-Automatic Integration4 | An integration that is carried out by both code/computer programs and manual work. |
| | | |
| GENERAL TERMS | Bug4 | Or software bug. A software bug is an error, flaw, failure or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways. Sometimes it is an alternate saying of "software defect". |
| Defect4 | Or software defect. A software defect is a condition in a software product which does not meet a software requirement (as stated in the requirement specifications) or end-user expectations (which may not be specified but are reasonable). In other words, a defect is an error in coding or logic that causes a program to malfunction or to produce incorrect/unexpected results. Sometimes it is an alternate saying of "software bug". |
| Development Environment4 | The development environment (dev) is the environment in which changes to software are developed, most simply an individual developer's workstation. A common 4-tier deployment architecture is development, testing, staging, production (DEV, TEST, STAGING, PROD), with software being deployed to each in order. |
| Enhancement4 | Or software enhancement. In software development, software maintenance refers to modifying software products after delivery in order to correct faults, improve performance or other attributes, or to adapt the product to a modified environment. |
| Process4 | It is a series of actions or steps taken in order to achieve a particular end. |
| Production Environment4 | The production environment (PROD) is also known as live, particularly for servers, as it is the environment that users directly interact with. A common 4-tier deployment architecture is development, testing, staging, production (DEV, TEST, STAGING, PROD), with software being deployed to each in order. |
| Staging Environment4 | The staging environment (STAGING) is an environment for final testing immediately prior to deploying to production. It seeks to mirror the actual production environment as closely as possible and may connect to other production services and data, such as databases. A common 4-tier deployment architecture is development, testing, staging, production (DEV, TEST, STAGING, PROD), with software being deployed to each in order. |
| Testing Environment4 | The test environment (TEST) is an environment for human testers to exercise new and changed code via either automated checks or non-automated techniques. A common 4-tier deployment architecture is development, testing, staging, production (DEV, TEST, STAGING, PROD), with software being deployed to each in order. |
| Validation4 | Or data validation. It is an iterative process that uses formal methods of evaluating a dataset's adherence to a defined quality standard. |
| Workflow4 | It is the sequence of industrial, administrative, or other processes through which a piece of work passes from initiation to completion. A workflow consists of an orchestrated and repeatable pattern of business activity enabled by the systematic organization of resources into processes that transform materials, provide services, or process information. |
| | |
| REFERENCES | |
| 1. | Essential Roads and Highways Vocabulary | |
| 2. | HPMS Field Manual | |
| 3. | ARNOLD Reference Manual | |
| 4. | Wikipedia or Internet | |
| | |
| Last updated by Yueming Wu of WVDOT on 04/23/2018 |
