> For the complete documentation index, see [llms.txt](https://atd-dts.gitbook.io/atd-geospatial/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atd-dts.gitbook.io/atd-geospatial/comprehensive-transportation-network/ctn-data-dictionary.md). # CTN Data Dictionary ## Identification Fields * UNIQUE\_ID * SEGMENT\_ID: Unique segment id from Street Segment feature, NULL if modified. * NETWORK\_ID: Unique id based on segment id or object id if feature was modified. * FULL*STREET* NAME: From Street Segment feature. * PREFIX\_DIRECTION: From Street Segment feature. | Domain | Domain Description | | ------ | ------------------ | | E | East | | N | North | | S | South | | W | West | * PREFIX\_TYPE: From Street Segment feature. * STREET\_NAME: From Street Segment feature. * STREET\_TYPE: From Street Segment feature. * SUFFIX\_DIRECTION: From Street Segment feature. | Domain | Domain Description | | ------ | ------------------ | | EB | Eastbound | | NB | Northbound | | SB | Southbound | | WB | Westbound | * SEGMENT\_LIMITS: Use to field calculate FROM\_STREET, TO\_STREET. * FROM\_STREET: Beginning intersecting street name, from E to W or N to S. * TO\_STREET: Ending intersecting street name, from E to W, or N to S. * ORIENTATION: Orientation of segment, from E to W or N to S. | Domain | Domain Description | | ------ | ------------------ | | NS | North to South | | EW | East to West | * SORT\_ORDER: Order of segments, from E to W or N to SB. | Domain | Domain Description | | ------ | ------------------ | | NS | North to South | | EW | East to West | * FROM\_ADDRESS: Address range minimum from street segment feature, not zero. * TO\_ADDRESS: Address range maximum from street segment feature. * PLACE\_TEXT: Address range and full street name. * MODIFICATION: Type of modification made to feature. | Domain | Domain Description | | --------- | ------------------ | | Added | New feature | | Attribute | Attribute change | | Geography | Re-alignments | | Split | Splitting lines | | None | None | * LINE\_TYPE: Location of the line in the network. | Domain | Domain Description | | -------------------- | -------------------------------------------------------- | | On-Street | Roadways | | Off-Street | Trails, transit | | Off-Street Connector | Connects off-street facilities with on-street facilities | | Street Crossing | Shows off-street facilities' continuity across streets | * BUILT\_STATUS: Current status of Urban Trails. | Domain | Domain Description | | -------- | -------------------- | | Existing | Existing Urban Trail | | Funded | Funded Urban Trail | | Proposed | Proposed Urban Trail | *NOTE: This field needs to be renamed URBAN\_TRAIL\_BUILT\_STATUS, moved to the Urban Trails section, and the domains need to match those of the Urban Trails dataset.* * FACILITY\_TYPE: Type of facility by mode. | Domain | Domain Description | | ----------- | ------------------ | | Roadway | Roadway | | Transit | Transit | | Urban Trail | Urban Trail | *NOTE: This field's domains may need updating. Purpose may need to be revisited. Transit value may be added to LINE\_TYPE and Urban Trail facility type may be tracked through URBAN\_TRAIL\_NETWORK\_ID IS NOT NULL query, etc.* ## Traveled Way * THROUGH\_LANES: Number of total through lanes. * INSIDE\_LANE\_WIDTH: Width of inside lanes, if different from THROUGH\_LANE\_WIDTH. * OUTSIDE\_LANE\_WIDTH: Width of outside lanes, if different from THROUGH\_LANE\_WIDTH. * THROUGH\_LANE\_WIDTH: Through lane width. *NOTE: Re-order to be placed between THROUGH\_LANES and INSIDE\_LANE\_WIDTH fields.* * MEDIAN: Type of median. | Domain | Domain Description | | --------- | ------------------ | | Raised | Raised Median | | CLT | Center Lane Turn | | Undivided | Undivided | * LEFT\_TURN\_LANES: Number of left turn lanes. * MEDIAN\_WIDTH: Width of median *NOTE: Re-order to be placevd between MEDIAN and LEFT\_TURN\_LANES fields.* * BICYCLE\_FACILITY: Type of bicycle facility. | Domain | Domain Description | Visual Description | | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------ | - | | Bike Lane | A portion of the roadway that has been designated by striping, signage, and pavement markings for the preferential or exclusive use by bicyclists. A bike lane has no physical barrier (bollards, medians, raised curbs, etc) that restrict the encroachment of motorized traffic. Bike lanes are traditionally located on the right-hand side of the street, but can be located on the left-hand side of the street in specific situations. Bike lanes typically run in the same direction as traffic. See Bike Lane - Contraflow below for other configurations. | | | | Bike Lane - Buffered | Similar in every way to a bike lane, but are typically wider, and are separated from traffic by two wide stripes, as opposed to the single stripe of conventional bike lanes. | | | | Bike Lane - Climbing | Climbing Bike Lanes are installed on steep roads going up hill in order to allow cyclists to climb the hill at their own pace, and without traffic intereference. In most cases where climbing bike lanes exist, only a sharrow is used in the down-hill direction. In cases where climbing bike lanes and sharrows are present, mark the bicycle facility as a climbing lane (see South Lamar between Barton Springs and Treadwell for an example). | | | | Bike Lane - Painted | Painted Bike Lanes are usually found at intersections, and the paint is meant to highlight the location of cyclists on the road. | | | | Bike Lane - Contraflow | Contraflow bike lanes are installed on low-traffic corridors necessary for the connectivity of a particular bicycle route (see N Lamar Service Rd between 5th and 3rd for an example) | | | | Bike Lane - Protected One-Way | An exclusive facility that combines the user experience of a separated path with the on-street infrastructure of a conventional bike lane. A protected bicycle lane is physically separated from motor vehicle traffic and distinct from the sidewalk. Protected bicycle lanes may be at street level, at sidewalk level, or at an intermediate height. | | | | Bike Lane - Protected Two-Way | An exclusive facility that combines the user experience of a separated path with the on-street infrastructure of a conventional bike lane. A protected bicycle lane is physically separated from motor vehicle traffic and distinct from the sidewalk. Protected bicycle lanes may be at street level, at sidewalk level, or at an intermediate height. | | | | Bike Lane - Removed | Bike lanes that have been removed. *check with Active Transportation for more detailed description.* | | | | Bike Lane - Suggested | Bike lanes that have been suggested by citizens. *check with Active Transportation for more detailed description.* | | | | Bike Lane - wParking | Bike Lanes where parking is allowed (see Lost Creek Boulevard) | | | | Neighborhood Bikeway | The following are the recommended speed and volume targets (2014): Speeds: the 85th percentile speed should be managed to be at 25 mph or less, with 20 mph as the preferred speed. Volumes: motor vehicle volumes should be managed to be under 1500 vehicles per day, with up to 3000 vehicles per day allowed in limited sections of the corridor. Additionally, quiet streets must have signage and sharrows. *Check with Active Transportation to see if definition has been updated recently.* | | | | Sharrows | Street markings placed in the travel lane to indicate where people should preferably cycle. | | | | Wide Shoulder | A shoulder can accommodate bicyclists if it is adequate in width (\~10 ft min) | | | | Wide Curb Lane | A wide curb lane is 14'+ outside lane, typically along TXDOT highway projects. | | | | Trail - Paved | Paths physically separated from motorized vehicular traffic by an open space or barrier and are located either within the road right-of-way, or accomodated in another way, such as parkland. Paved Trails are shared by multiple users, and may also be known as Urban Trails or Shared Use Path, depending on jurisdiction. | | | | Trail - Unpaved | Crushed granite trails that are typically ADA-accessible | | | | Bridge | Bridges connect facilities across natural barriers, such as creeks. Bridges are only attributed as such when they connect off-street facilities, such as paved and unpaved trails. It is not necessary to designate roadway bridges, such as the Ann Richards Bridge. | | | *NOTE: Will include a 3rd column with either a screenshot or a link to examples of each facility type.* * BICYCLE\_FACILITY\_WIDTH: Width of bicycle facility. * OUTSIDE\_TURN\_LANE\_WIDTH: Width of outside turn lane, if present. * PARKING: Type of parking, if present. | Domain | Domain Description | | -------------- | ---------------------- | | Parallel | Parallel parking | | Angled Head-in | Angled head-in parking | | Angled Back-in | Angled back-in parking | | Head-In | Head-in parking | | None | None | * PARKING\_WIDTH: Width of parking, if present. * SHOULDER\_WIDTH: Width of shoulder, if present. * PAVEMENT\_WIDTH: Width from curb to curb, including median. * ONE\_WAY: Direction of Travel. | Domain | Domain Description | | ------ | ---------------------------------------------- | | N | None | | FT | To-from (order in which segment was digitized) | | TF | From-to (order in which segment was digitized) | | B | Bidirectional | * MARKINGS: Denotes whether markings are present in segment. | Domain | Domain Description | | ------ | ------------------ | | Y | Yes | | N | No | ### Cross Sections * CROSS\_SECTION\_DETAIL: Denotes road elements including auto lanes, center turn lanes, bike lanes, medians, shoulders and any other area that may occur between face of curbs or edge of pavements. Any time a transition occurs either by pavement marker or physical barrier, a new item should be noted and separated with a “-“. The following designations should be used as a comprehensive library of “tags” for this attribute field: | Tag | Definition | | -------- | --------------------------------------------------------------------------------- | | BL | Bike Lane | | BBL | Buffered Bike Lane | | PBL | Protected Bike Lane One-way (behind raised curb or another physical separator) | | CTT | Protected Bike Lane Two-way (Two-way Cycletrack) | | CL | Center Line | | CTL | Center Turn Lane | | MED | Median (can be curbed or open ditch) | | OW | One Way road (should be used to denote one-way roads at beginning of description) | | P | Parking | | S | Shoulder | | UNMARKED | No pavement markings | Examples detailed cross sections are shown below: | Detailed Cross Section | Description | | ---------------------- | ----------------------------------------------------------- | | T-T-MED-T-T | 4 travel lanes divided by a median | | BL\_T\_CTL\_T\_BL | 3 travel lanes road with a center turn lane and a bike lane | | T-CL-T | 2 travel undivided | | UNMARKED | Unmarked road | | OW-T-T | 2 travel lanes, one way | * CROSS\_SECTION\_GENERAL: This is a generalized classification of a roadway that describes: number of lanes; if a segment is divided or undivided (center turn lanes will be an odd number if undivided); or if a facility is one-way. In addition, if a road is a 2-lane undivided or 3-lane undivided, special designation should be given for highways (-H), rural county roads (-N) and gravel road types (-G). Highways can be defined as TxDOT or County Facilities (FM, RM, CR, SH, etc. designations) or 50 mph and up. Any of these designations can include “-O” or "-OP" for on-street parking. Possible entries include, but are not limited to: | Detailed Cross Section | General Cross Section | Description | Example (NETWORK\_ID) | | ---------------------- | --------------------- | -------------------------------------------------------------- | --------------------- | | OW-T-T-CTT | 2O | 2 travel lanes one way and protected 2-way bike lane | 2036220 | | T-CL-T | 2U | 2 travel lanes, undivided | 2023469 | | | 2U-G | 2 travel lanes, undivided | 2015126 | | T-CL-T | 2U-H | 2 travel lanes, highway | 5122042 | | BBL-T-CTL-T-BBL | 3U | 2 travel lanes with a center turn lane and buffered bike lanes | 2023209 | | T-CL-CTL-T | 3U-H | 2 hghway travel lanes with a center turn lane | 2028269 | | T-T-CL-T-T | 4U | 4 travel lanes with a Centerline | 2015302 | | T-T-MED-T-T | 4D | 4 travel lanes with a raised median | 59895 | | BL-T-T-MED-T-T-BL | 4D | 4 travel lanes with a raised median and bike lanes | 59327 | | T-T-CTL-T-T | 5U | 4 travel lanes with a center turn lane | 2015570 | ## Streetside * SIDEWALK: Presence of sidewalk. | Domain | Domain Description | | ------ | ----------------------- | | EX | Existing | | AB | Absent | | EXD | Existing with Driveways | | EXG | Existing with Gaps | * SIDEWALK\_WIDTH: Width of sidewalk. * PLANTING\_ZONE: Width of planting/furniture zone. * BAR\_DITCH\_WIDTH: Width of bar ditch, if present. * BUILDING\_SETBACK: Building setback from curb. ## Right of Way * RIGHT\_OF\_WAY\_MINIMUM: Calculated length between property lines. * RIGHT\_OF\_WAY\_MAXIMUM: Calculated length between property lines. * RIGHT\_OF\_WAY\_AVERAGE: Calculated length between property lines. * RIGHT\_OF\_WAY\_MEDIAN: Calculated length between property lines. * RIGHT\_OF\_WAY\_CONSTRAINED: Assessment of existing ROW and future ROW. | Domain | Domain Description | | ------ | ------------------ | | Y | Yes | | N | No | ## Context * JURISDICTION: Type of jurisdiction a segment may fall in. *NOTE: This field needs domains.* * MAINTENANCE\_AGENCY: Maintenance agency per segment. *NOTE: This field needs domains.* * COMMUNITY\_CONTEXT: CodeNEXT transects. | Domain | Domain Description | | ------------------------------- | ------------------------------- | | Centers and Corridors | Centers and Corridors | | Urban | Urban | | Suburban | Suburban | | Special District - Downtown | Special District - Downtown | | Special District - Hill Country | Special District - Hill Country | | Special District - Industrial | Special District - Industrial | *NOTE: This field will need some re-purposing, as CodeNEXT has been scrapped, and council has yet to settle on its successor.* * STREET\_LEVEL: Street level type. | Domain | Domain Description | | ------ | ------------------ | | 0 | Level 0 | | 1 | Level 1 | | 2 | Level 2 | | 3 | Level 3 | | 4 | Level 4 | | 5 | Level 5 | *NOTE: Need actual definition as to what the levels represent.* * FUNCTIONAL\_CLASSIFICATION: Functional classification from PWD. | Domain | Domain Description | | ------------------------------------- | ------------------------------------- | | Interstate, Freeway, Expressway, Toll | Interstate, Freeway, Expressway, Toll | | US and State Highway | US and State Highway | | Arterial | Arterial | | Collector | Collector | | Local | Local | | Alley | Alley | | Ramps and Turnarounds | Ramps and Turnarounds | | Private Roads | Private Roads | * LAND\_USE: Existing Adjacent land use(s). | Domain | Domain Description | | -------------------- | -------------------- | | Residential | Residential | | Commercial | Commercial | | Mixed Use | Mixed Use | | Industrial | Industrial | | Civic | Civic | | Parks and Open Space | Parks and Open Space | | Undeveloped | Undeveloped | * SUBCHAPTER\_E: Subchapter E Trigger. | Domain | Domain Description | | --------------------- | --------------------- | | Core Transit Corridor | Core Transit Corridor | | Urban Roadway | Urban Roadway | | No | No | *NOTE: Define Subchapter E. Believed to be used for Street Impact Fee (SIF) studies.* * TRANSIT: Type of transit route(s). | Domain | Domain Description | | ---------- | ------------------ | | Local | Local | | Limited | Limited | | Feeder | Feeder | | Crosstown | Crosstown | | Special | Special | | Express | Express | | MetroRapid | MetroRapid | | MetroRail | MetroRail | | UT Shuttle | UT Shuttle | | Regional | Regional | | None | None | *NOTE: Some of these values may have changed since CapMetro's CapReMap. Regional data should come from Capital Area Rural Transit System (CARTS).* * TRANSIT\_STOPS: Number of stops. *NOTE: Ensure description fits purpose / actual data in CTN vs. other transit-related fields.* * BIKE\_ROUTE\_NAME: Name of designated bike route. * BIKE\_LEVEL\_OF\_COMFORT: Level of Comfort of bike facility. See Reference section for more on Level of Comfort Mapping. | Domain | Domain Description | Visual Representation | | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | | High (H) | High Comfort ratings are most commonly associated with Protected and Buffered Bike Lanes, given the separation from traffic. However, other factors may result in other bike facilities to receive this rating, such as traffic volume, so it is possible that Bike Lanes, and even Shared Lanes receive this rating. | | | High Paved (HP) | High Paved Comfort ratings are used on paved trails, typically Urban Trails (paved, 10'-12' wide) | | | High Unpaved (HU) | High Unpaved Comfort ratings are used for unpaved trails that are suitable for transportation by users of all ages and abilities. This typically includes crushed granite trails shared with pedestrians (see Lady Bird Lake Trail), but would not include the Barton Creek Greenbelt, as it is more difficult terrain that is only truly accessible on a mountain bike and requires significant skill to traverse. | | | Medium (M) | Medium Comfort Ratings are most commonly associated with bike lanes, although other factors may result in other bicycle facilities to receive this rating. In fact, it is not uncommon for roadways without bicycle facilities to be rated M, as their traffic volume, street connectivity and speed limits may lead to a comfortable bicycle ride without needing further improvements. Routes suggested by citizens, for example are often designated as M. | | | Low (L) | Low Comfort roads are associated with high traffic volumes and speeds, and little or no bicycle facilities. Roads rated as L are marked because they are key route connections. | | | Extremely Low (EL) | Extremely Low Comfort ratings are given to roads not recommended for bicycle travel, and must be used with extreme caution. They are rated because they are often the only connection to other bicycle facilities. | | | Rough Trail (RT) | Rough Trail ratings are given to unpaved trails that are not accessible for transportation to users of all ages and abilities, and often require a mountain bike and considerable skill to traverse. They are rated when they provide key connections to on-street facilities. | | | Helpful Sidewalk (SS) | Helpful Sidewalk ratings are given to sidewalks that provide a safer connection between bicycle facilities than riding on the road. Helpful sidewalks are typically found along highways, and may sometimes connect to to paved and unpaved trails. | | | Minor Trail (TC) | This rating applies to trails, whether paved or unpaved that is accessible to people of all ages and abilities, but that is not wide enough to accommodate two-way traffic easily. These are often connections from trails to on-street facilities. | | * SPEED\_LIMIT: Speed limit. * AVERAGE\_SPEED: Average speed from speed study. * PERCENTILE\_SPEED: 85th percentile (MPH) from speed study. * SPEED\_STUDY\_DATE: Date of speed study. * TRAFFIC\_VOLUME: Total vehicular 24-hour volume from traffic study. * TRAFFIC\_VOLUME\_SOURCE: Source of traffic volume study. | Domain | Domain Description | | ------ | ---------------------------------- | | COA | City of Austin | | TXDOT | Texas Department of Transportation | | TIA | *Need disambiguation.* | ## Street Network Plan Recommendations * IMPROVEMENT: Type of the improvements | Domain | Domain Description | | ----------------- | ---------------------------------------------------------------------------- | | New Roadway | New Roadway | | New Bike Facility | New Bike Facility (all line types) | | New Urban Trail | New Urban Trail (off-street, off-street connector,a nd street crossing only) | | Widen Roadway | Widen Roadway | | Reconstruction | Reconstruction | | Restriping | Restriping | | None | None | * REQUIRED\_RIGHT\_OF\_WAY: Amount of Right of Way required for ultimate cross section. * REC\_THROUGH\_LANES: Recommended through lanes. * REC\_INSIDE\_LANE\_WIDTH: Recommended wide of inside through lanes, if different. * REC\_OUTSIDE\_LANE\_WIDTH: Recommended width of outside lanes, if different. * REC\_THROUGH\_LANE\_WIDTH: Recommended width of through lanes. *NOTE: Need to move this field up to be between REC\_THROUGH\_LANES and REC\_INSIDE\_LANE\_WIDTH.* * REC\_MEDIAN: Type of median recommended in ultimate cross section. | Domain | Domain Description | | --------- | ------------------ | | Raised | Raised Median | | CLT | Center Lane Turn | | Undivided | Undivided | * REC\_LEFT\_TURN\_LANES: Recommended number of left turn lanes. * REC\_MEDIAN\_WIDTH: Recommended median width. *NOTE: Need to move this field up to be between REC\_MEDIAN and REC\_LEFT\_TURN\_LANES.* * REC\_BICYCLE\_FACILITY: recommended bicycle facility in 2014 Bike Plan | Domain | Domain Description | | | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | - | - | | Bike Lane | A portion of the roadway that has been designated by striping, signage, and pavement markings for the preferential or exclusive use by bicyclists. A bike lane has no physical barrier (bollards, medians, raised curbs, etc) that restrict the encroachment of motorized traffic. Bike lanes are traditionally located on the right-hand side of the street, but can be located on the left-hand side of the street in specific situations. Bike lanes typically run in the same direction as traffic. See Bike Lane - Contraflow below for other configurations. | | | | Bike Lane - Buffered | Similar in every way to a bike lane, but are typically wider, and are separated from traffic by two wide stripes, as opposed to the single stripe of conventional bike lanes. | | | | Bike Lane - Climbing | Climbing Bike Lanes are installed on steep roads going up hill in order to allow cyclists to climb the hill at their own pace, and without traffic intereference. In most cases where climbing bike lanes exist, only a sharrow is used in the down-hill direction. In cases where climbing bike lanes and sharrows are present, mark the bicycle facility as a climbing lane (see South Lamar between Barton Springs and Treadwell for an example). | | | | Bike Lane - Painted | Painted Bike Lanes are usually found at intersections, and the paint is meant to highlight the location of cyclists on the road. | | | | Bike Lane - Contraflow | Contraflow bike lanes are installed on low-traffic corridors necessary for the connectivity of a particular bicycle route (see N Lamar Service Rd between 5th and 3rd for an example) | | | | Bike Lane - Protected One-Way | An exclusive facility that combines the user experience of a separated path with the on-street infrastructure of a conventional bike lane. A protected bicycle lane is physically separated from motor vehicle traffic and distinct from the sidewalk. Protected bicycle lanes may be at street level, at sidewalk level, or at an intermediate height. | | | | Bike Lane - Protected Two-Way | An exclusive facility that combines the user experience of a separated path with the on-street infrastructure of a conventional bike lane. A protected bicycle lane is physically separated from motor vehicle traffic and distinct from the sidewalk. Protected bicycle lanes may be at street level, at sidewalk level, or at an intermediate height. | | | | Bike Lane - Removed | Bike lanes that have been removed. *check with Active Transportation for more detailed description.* | | | | Bike Lane - Suggested | Bike lanes that have been suggested by citizens. *check with Active Transportation for more detailed description.* | | | | Bike Lane - wParking | Bike Lanes where parking is allowed (see Lost Creek Boulevard) | | | | Neighborhood Bikeway | The following are the recommended speed and volume targets (2014): Speeds: the 85th percentile speed should be managed to be at 25 mph or less, with 20 mph as the preferred speed. Volumes: motor vehicle volumes should be managed to be under 1500 vehicles per day, with up to 3000 vehicles per day allowed in limited sections of the corridor. Additionally, quiet streets must have signage and sharrows. *Check with Active Transportation to see if definition has been updated recently.* | | | | Sharrows | Street markings placed in the travel lane to indicate where people should preferably cycle. | | | | Wide Shoulder | A shoulder can accommodate bicyclists if it is adequate in width (\~10 ft min) | | | | Wide Curb Lane | A wide curb lane is 14'+ outside lane, typically along TXDOT highway projects. | | | | Trail - Paved | Paths physically separated from motorized vehicular traffic by an open space or barrier and are located either within the road right-of-way, or accomodated in another way, such as parkland. Paved Trails are shared by multiple users, and may also be known as Urban Trails or Shared Use Path, depending on jurisdiction. | | | | Trail - Unpaved | Crushed granite trails that are typically ADA-accessible | | | | Bridge | Bridges connect facilities across natural barriers, such as creeks. Bridges are only attributed as such when they connect off-street facilities, such as paved and unpaved trails. It is not necessary to designate roadway bridges, such as the Ann Richards Bridge. | | | *NOTE: Will include a 3rd column with either a screenshot or a link to examples of each facility type.* * REC\_BICYCLE\_FACILITY\_WIDTH: Recommended bicycle facility width. * REC\_BICYCLE\_AAANETWORK: All Ages and Abilities Network, as adopted by or proposed to Austin City Council. | Domain | Domain Description | | -------------------------- | --------------------------------------------------------------- | | CouncilAdopted | AAA Facility adopted by Austin City Council | | CouncilAdoptedAltAlignment | AAA Facility alternate alignment adopted by Austin City Council | | Proposed | AAA Facility proposed to Austin City Council | * REC\_OUTSIDE\_TURN\_LANE\_WIDTH: Recommended turn lane width, if present. * REC\_PARKING: Recommended Parking Type. | Domain | Domain Description | | -------------- | ---------------------- | | Parallel | Parallel parking | | Angled Head-in | Angled head-in parking | | Angled Back-in | Angled back-in parking | | Head-In | Head-in parking | | None | None | * REC\_PARKING\_WIDTH: Recommended parking width, if present. * REC\_CURB\_TO\_CURB: Recommended width from curb to curb, including median. * REC\_CROSS\_SECTION\_DETAIL: Recommended cross section, in detail. * REC\_CROSS\_SECTION\_GENERAL: Recommended general cross section. * REC\_SPEED: Recommended design speed/target speed. * REC\_SIDEWALK\_WIDTH: Recommended sidewalk width. * REC\_PLANTING\_ZONE\_WIDTH: Recommended planting zone width. * REC\_BUILDING\_SETBACK: recommended building setback from curb. * REC\_TRANSIT\_PRIORITY: Recommended transit priority. | Domain | Domain Description | | ----------------------- | ----------------------- | | Transit Only Lanes | Transit only lanes | | Transit Signal Priority | Transit signal priority | | Transit Priority | Transit priority | | Premium | Premium | | Commuter | Commuter | * REC\_SIDEWALK\_PRIORITY: Recommended sidewalk priority. | Domain | Domain Description | | --------- | ------------------ | | Very High | Very high | | High | High | | Medium | Medium | | Low | Low | | Very Low | Very Low | *NOTE: Move this field up above REC\_SIDEWALK\_WIDTH.* * REC\_BIKE\_PRIORITY: Recommended Bicycle Facility in the All Ages & Abilities Network. | Domain | Domain Description | | ------ | ------------------ | | Y | Yes | | N | No | * REC\_URBAN\_TRAIL\_PRIORITY: Tier recommended in the 2014 Urban Trails Master Plan | Domain | Domain Description | | ------ | ------------------ | | Tier 1 | Tier 1 Trails | | Tier 2 | Tier 2 Trails | ## Audit * CREATED\_BY: Automatically filled audit field * CREATED\_DATE: Automatically filled audit field * MODIFIED\_BY: Automatically filled audit field * MODIFIED\_DATE: Automatically filled audit field ## CapMetro * CAP\_METRO\_2025: Routes included in CapMetro's Connections 2025 plan. * C2025\_RAPID: Connection 2025's Rapit Transit Routes. * C2025\_FREQ: Connection 2025's Frequent Transit Routes. * C2025\_EXPR: Connection 2025's Express Transit Routes. * C2025\_LOCAL: Connection 2025's Local Transit Routes. * C2025\_UT: Connection 2025's University of Texas' Transit Routes. * C2025\_RAIL: Connection 2025's Rail Transit Routes. ## Urban Trails * URBAN\_TRAIL\_NETWORK\_ID: ID field imported from the Urban Trails Dataset. * URBAN\_TRAILS\_DATA\_SOURCE: Source for Urban Trails. | Domain | Domain Description | | ------ | ----------------------------- | | UTMP | 2014 Urban Trail Master Plan | | ASMP | Austin Strateig Mobility Plan | *NOTE: Need to update domain to include all current values in urban.trail.network dataset on MAINT.* * URBAN\_TRAIL\_TYPE: *NOTE: Need definition from Urban Trails Staff.* * LOCATION: Relative location of Urban Trail. | Domain | Domain Description | | ----------------------- | ---------------------------------------------------------------- | | ALONG\_CREEK | Urban Trail found along a creek | | ALONG\_RAILROAD | Urban Trail found along a railroad, (rails to trails, etc.) | | ALONG\_ROADWAY | Urban Trail found along a roadway | | NEIGHBORHOOD\_CONNECTOR | Urban Trail found between neighborhoods, they're typically short | | WITHIN\_PARKS | Urban Trail found within parks | ## Planning *NOTE: The following fields were left in the CTN as they were used in the planning process of the ASMP. They may soon be exported to a separate dataset, and removed from the CTN.* * JURISDICTI * JURISDIC\_1 * JURISDIC\_2 * IN\_ETJ --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://atd-dts.gitbook.io/atd-geospatial/comprehensive-transportation-network/ctn-data-dictionary.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.