Historic Bridge Database Data Dictionary · 2015. 12. 15. · MEAD & HUNT – AKRF N133A076\N133-...

$: Historic Bridge Database Data Dictionary · 2015. 12. 15. · MEAD & HUNT – AKRF N133A076\N133- 99A(D3) \11–02 1 NYSDOT Historic Bridge Database Data Dictionary 1. Introduction$
Historic Bridge DatabaseData Dictionary

Task C2 of the Historic Bridge Inventory and

Management Plan

Prepared for:

New York State

Department of Transportation

Albany, New York

and

Federal Highway Administration

Albany, New York

Prepared by:

and

November 2002

Final Report

MEAD & HUNT – AKRFN133A076\N133-99A(D3)\11–02 i

Table of Contents

Page

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2. Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

3. Sources of Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

4. Historic Determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

5. Data Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

6. Database Update Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Cover photograph: Bridge depicted is BIN 1020920, State Route 30 over the Mine Kill, Region 9, SchoharieCounty.

MEAD & HUNT – AKRFN133A076\N133-99A(D3)\11–02 1

NYSDOT Historic Bridge DatabaseData Dictionary

1. Introduction

The New York State Department of Transportation (NYSDOT) Historic Bridge Database compiles

information for approximately 10,700 New York State bridges constructed before 1961. This data

dictionary provides information on the source of data, the meaning of each field, and codes used in

recording data. It has been prepared by Allee King Rosen & Fleming, Inc. (AKRF) and Mead &

Hunt, Inc.

2. Methodology

The Historic Bridge Database is one of the products of the Historic Bridge Inventory and

Management Plan project. This inventory collected and confirmed information on pre-1961 bridges

for the purposes of identifying National Register of Historic Places (National Register) eligibility.

The inventory was conducted through a five-part process intended to narrow the state’s more than

10,700 pre-1961 bridges down to a group for which National Register eligibility could be

determined.

These five stages were:

1. Elimination of bridges considered out of the scope of evaluation for this inventory. In this

stage, NYSDOT’s Bridge Identification and Inspection System (BIIS) database of more than

10,700 pre-1961 bridges (each represented by a unique Bridge Identification Number, or

BIN) was narrowed to approximately 6,300 bridges for which detailed information could be

gathered. Bridges that were removed from consideration were assigned an “Excluded From

Inventory” code and were not evaluated for eligibility. More than 4,000 pre-1961 bridges

were eliminated from the scope of evaluation. Item O identifies the reason for elimination

of each excluded bridge.

2. Research on bridges remaining in the inventory. For the remaining approximately 6,300

bridges, NYSDOT BIN Files were reviewed at the regional offices. In this fashion, BIIS

information was updated and augmented with available information on the details of the

bridge, the designer or builder, the construction date, major work on the bridge, and other

information, as outlined in this data dictionary.


3. Stratification of remaining bridges. Using a combination of information from the BIIS and

from the BIN file review, approximately 4,300 of the 6,300 bridges were eliminated from

further consideration; while approximately 2,000 bridges were deemed to warrant field

survey to determine potential eligibility. The Bridge Stratification Methodology and List of

Subgroups (December 1999) and Rationale for Evaluation Data Needs (May 2000) outlines

the process by which bridges were eliminated from consideration at this stage and Item O

identifies excluded bridges.

4. Field survey. In the summer of the year 2000, approximately 2,000 remaining bridges were

surveyed. Data gathered from the BIIS and BIN file reviews were checked and updated, if

necessary; photographs were taken; and additional information was gathered.

5. Determination of National Register eligibility. Using information from the BIIS, BIN file

review, and field survey, the eligibility of remaining bridges was assessed (see Items K

through N).

3. Sources of Information

Basic information from the BIIS is included for each bridge so the Historic Bridge Database can be

used independently of the BIIS, and also can be linked to the BIIS (using the BIN as a primary key).

The Historic Bridge Database contains:

• BIIS information on bridges constructed before 1961.

• Information from the Historic Bridge Inventory – Year 2000.

– BIN file information on a subset of bridges whose files were reviewed.

– Detailed field survey information on a further subset of bridges that required more

detailed information to assess eligibility.

• Data from updates on bridge management activities.

1 The field “Historic Determination” in the Historic Bridge Database should not beconfused with the field “Historical Significance” in the BIIS (Record Code 01, Column 113),which is a previous identification of historic status conducted by NYSDOT. The Historic BridgeInventory – Year 2000 “Historic Determination” supersedes the existing code in BIIS.


4. Historic Determination

In addition to BIIS data, every bridge also contains information in at least one additional field:

Historic Determination (Item K).1 This field notes whether or not a bridge was deemed eligible. It

also notes bridges that were not evaluated as part of the Historic Bridge Inventory. For those bridges

“not evaluated,” an additional field, “Excluded from Inventory” (Item O), notes the reason why they

were not evaluated. Bridges with “Excluded from Inventory” coding of “09 – Superstructure

replaced after 1960,” “10 – Superstructure removed,” “19 – Beam/Girder – loss of integrity,” and

“20 – Beam/Girder – no possible significance identified” were evaluated and received a “not

eligible” determination in Item K. For those bridges evaluated and determined eligible as part of the

Historic Bridge Inventory and Management Plan project, a third set of fields, “Reason for Historic

Determination” (Items L, M, and N), notes the reason why they were deemed eligible.

5. Data Dictionary

ITEM A: BRIDGE IDENTIFICATION NUMBER FIELD TYPE: Text(BIN) FIELD SIZE: 7

ORIGIN OF DATA: 1999 BIIS: Record Code ALL, Columns 3-9

INFORMATION: Unique 7-character BIN assigned to each individual bridge by the Bridge Inventoryand Inspection Unit of the NYSDOT Structures Division.

CODING: Unique 7-character bridge identifier.

ITEM B: REGION FIELD TYPE: Text(Region) FIELD SIZE: 1

ORIGIN OF DATA: 1999 BIIS: Record Code ALL, Column 1

INFORMATION: New York State Department of Transportation Region in which the bridge is

located.

CODING: 1 – Albany2 – Utica


ITEM B: REGION (CONT.) FIELD TYPE: Text(Region) FIELD SIZE: 1

3 – Syracuse4 – Rochester5 – Buffalo6 – Hornell7 – Watertown8 – Poughkeepsie9 – Binghamton0 – HauppaugeN – New York City

ITEM C: COUNTY FIELD TYPE: Text(County) FIELD SIZE: 1

ORIGIN OF DATA: 1999 BIIS: Record Code ALL, Column 2

INFORMATION: The county in which the bridge is located.

CODING: See Bridge Inventory Manual for complete list of county codes.

ITEM D: POLITICAL UNIT FIELD TYPE: Text(PoliticalUnit) FIELD SIZE: 4

ORIGIN OF DATA: 1999 BIIS: Record Code 01, Columns 18-21

INFORMATION: The political subdivision (town, village, or city) in which the bridge is located.

CODING: See Bridge Inventory Manual for complete list of political unit codes.

ITEM E: LOCATION FIELD TYPE: Text(Location) FIELD SIZE: 25


INFORMATION: Narrative location of the bridge tied to the junction of State or U.S. route; major

waterway; or nearest town, village, hamlet, or topographic feature.

CODING: Text description.


ITEM F: YEAR BUILT FIELD TYPE: Number(YearBuilt) FIELD SIZE: 4


INFORMATION: BIIS record of the year of original construction of bridge. For new and replacement

bridges, the year the contract was accepted or the bridge opened to traffic,whichever was earlier.

CODING: Four-digit number.

ITEM G: CONSTRUCTION DATE UPDATE FIELD TYPE: Number(ConstructionDateUpdate) FIELD SIZE: 4

ORIGIN OF DATA: Historic Bridge Inventory – Year 2000: BIN File Review, Field Survey

INFORMATION: BIIS Year Built (see Item F) updated based on BIN file data and/or bridge plateinformation.

CODING: Four-digit number.

ITEM H: CIRCA DATE FIELD TYPE: Number(CircaDate) FIELD SIZE: 1

ORIGIN OF DATA: Historic Bridge Inventory – Year 2000: BIN File Review

INFORMATION: Indicates if Construction Date Update (Item G) is a circa date.

CODING: 1 – Circa Date2 – Not a Circa Date

ITEM I: YEAR OF LAST MAJOR REHABILITATION FIELD TYPE: Text(YearofLastMajorRehab) FIELD SIZE: 4


INFORMATION: Year of last major rehabilitation of bridge. Includes any work on structuralelements of bridge which would result in a change in the load carrying capacity ofthe structure and which was eligible for funding under any of the Federal-Aidfunding categories.


ITEM I: YEAR OF LAST MAJOR REHABILITATION FIELD TYPE: Text(YearofLastMajorRehab) (CONT.) FIELD SIZE: 4

CODING: Four-digit year.N – No major rehabilitation.

ITEM J: FEATURE CARRIED FIELD TYPE: Text(FeatureCarried) FIELD SIZE: 17

ORIGIN OF DATA: 1999 BIIS: Record Code 12, Column 17 (“Description Type”)

INFORMATION: Written description of the feature carried by the bridge (road, route, etc.).


ITEM K: HISTORIC DETERMINATION FIELD TYPE: Text(HistoricDetermination) FIELD SIZE: 1

ORIGIN OF DATA: Historic Bridge Inventory – Year 2000

INFORMATION: Determination of the National Register status of the bridge.

CODING: 1 – Eligible (see also Items L, M, and N)2 – Not eligible3 – Not evaluated as part of Historic Bridge Inventory

ITEM L, M, N: REASON FOR HISTORIC DETERMINATION FIELD TYPE: Text(HistoricReason1) FIELD SIZE: 2(HistoricReason2)(HistoricReason3)


INFORMATION: Basis for determination of National Register eligibility.

CODING: 01 – Criterion A: associated with historic event(s) or activities02 – Criterion A: associated with historic trends03 – Criterion C: represents the work of a master04 – Criterion C: possesses high artistic values05 – Criterion C: demonstrates pattern or features common to a particular bridge

type


ITEM L, M, N: REASON FOR HISTORIC DETERMINATION FIELD TYPE: Text(HistoricReason1) (CONT.) FIELD SIZE: 2(HistoricReason2)(HistoricReason3)

06 – Criterion C: demonstrates individuality or variation of features within aparticular bridge type

07 – Criterion C: demonstrates evolution of a particular bridge typeNA – Not Applicable

ITEM O: EXCLUDED FROM INVENTORY FIELD TYPE: Text(ExcludedFromInventory) FIELD SIZE: 2


INFORMATION: Reasons why a bridge was not included in the pool of bridges for which NationalRegister eligibility was assessed.

CODING: 01 – Previously State/National Register listed

02 – Tunnel03 – Excluded owner04 – Culvert05 – In or near State/National Register listed district06 – On or over eligible parkway07 – Over eligible canal08 – On or over ineligible parkway09 – Superstructure replaced after 196010 – Superstructure removed11 – Ramp12 – Utility structure13 – Exclusively pedestrian bridge14 – Skywalk15 – Section 106 review completed16 – Elevated roadway17 – Railroad bridge18 – On NYSDOT 5-Year Capital Program19 – Beam/Girder – loss of integrity20 – Beam/Girder – no possible significance identified21 – Needs individual reviewNA – Not Applicable


ITEM P: GENERAL TYPE OF MAIN SPAN: FIELD TYPE: TextSTRUCTURAL CODES FIELD SIZE: 2(GTMSStructuralCodes)

ORIGIN OF DATA: 1999 BIIS; Historic Bridge Inventory – Year 2000: BIN File Review, Field Survey

INFORMATION: Updates 1999 BIIS information on structural type of the bridge superstructure

(Record Code 02, Column 14-15) with information gathered through BIN filereview and/or Field Survey.

CODING: 01 – Slab02 – Stringer/Multi-Beam or Girder03 – Girder and Floorbeam System04 – Tee Beam05 – Box Beam or Box Girders – Multiple06 – Box Beam or Box Girder – Single or Spread07 – Frame08 – Orthotropic09 – Truss – Deck10 – Truss – Thru11 – Arch – Deck12 – Arch – Thru [see also Item X: Arrangement]13 – Suspension14 – Stayed Girder15 – Movable – Lift16 – Movable – Bascule17 – Movable – Swing18 – Tunnel19 – Culvert20 – No Type is Dominant (Mixed Types)21 – Segmental Box Girder22 – Channel BeamRR – Replaced Bridge00 – Other

ITEM Q: GENERAL TYPE OF MAIN SPAN: FIELD TYPE: TextMATERIAL AND CONTINUITY CODES FIELD SIZE: 1(GTMSMatAndContinuity)

ORIGIN OF DATA: 1999 BIIS; Historic Bridge Inventory – Year 2000: BIN File Review, Field Survey

INFORMATION: Updates 1999 BIIS information on the type of material and continuity of the bridgesuperstructure (Record Code 02, Column 13) with information gathered throughBIN file review and/or Field Survey.


ITEM Q: GENERAL TYPE OF MAIN SPAN: (CONT.) FIELD TYPE: TextMATERIAL AND CONTINUITY CODES FIELD SIZE: 1(GTMSMatAndContinuity)

CODING: 1 – Concrete2 – Concrete Continuous3 – Steel4 – Steel Continuous5 – Prestress Concrete6 – Prestress Concrete Continuous7 – Timber8 – Masonry9 – Aluminum, Wrought Iron or Cast Iron0 – OtherA – Unpainted SteelB – Unpainted Steel ContinuousR – Replaced Bridge

ITEM R: MAIN SPAN: DESIGN TYPE FIELD TYPE: Text(MainSpanDesignType) FIELD SIZE: 2

ORIGIN OF DATA: 1999 BIIS; Historic Bridge Inventory – Year 2000: Field Survey

INFORMATION: Updates 1999 BIIS information on the primary structural makeup of main span(Record Code 15, Columns 17-18) with information gathered through Field Survey.

CODING: 01 – Slab

02 – Slab, Voided03 – Box, Adjacent04 – Box, Spread05 – Tee Beam06 – I-Beam (P/S)07 – Box, Channel (P/S)08 – Segmental Box09 – Rolled Beam, Multi-Girder10 – Rolled Beam – Floorbeam System, Deck11 – Rolled Beam – Floorbeam System, Thru12 – Rolled Beam Jack Arch13 – Plate Girder, Multi-Girder14 – Plate Girder – Floorbeam System, Deck15 – Plate Girder – Floorbeam System, Thru16 – Plate Girder Jack Arch17 – Truss, Deck18 – Truss, Thru (Overhead Bracing) 19 – Truss, Thru (No Overhead Bracing)


ITEM R: MAIN SPAN: DESIGN TYPE (CONT.) FIELD TYPE: Text(MainSpanDesignType) FIELD SIZE: 2

20 – Truss, Combination (Thru and Deck)21 – Truss, “Kit Bridge” (Bailey, Acrow, Mabey, etc.)22 – Arch, Thru23 – Arch, Thru, Tied24 – Arch, Deck – Open Spandrel25 – Arch, Deck – Filled Spandrel26 – Arch, Metal Plate (Pipe)27 – Frame28 – Frame with Floorbeam System29 – Movable, Bascule30 – Movable, Lift31 – Movable, Swing32 – Orthotropic33 – Preflex Plate Girder34 – Preflex Rolled Beam35 – Inverset Plate Girder36 – Inverset Rolled Beam37 – Suspension38 – Box, Single39 – Tunnel40 – Single Box Culvert41 – Multiple Pipe Culvert (FHWA)42 – Multiple Pipe Culvert (FHWA/NYS)43 – Multiple Box Culvert44 – Timber BeamRR – Replaced BridgeXX – OtherUU – Unknown

ITEMS S-U: BRIDGE TYPE DETAILS 1, 2, 3 FIELD TYPE: Text(BridgeTypeDetails1) FIELD SIZE: 2(BridgeTypeDetails2)(BridgeTypeDetails3)


INFORMATION: Three fields that record distinctive engineering or construction features that are

found on one or more bridge types.

CODING: 01 – Pinned (truss)02 – Riveted (truss)03 – Bolted (truss)


ITEMS S-U: BRIDGE TYPE DETAILS 1, 2, 3 (CONT.) FIELD TYPE: Text(BridgeTypeDetails1) FIELD SIZE: 2(BridgeTypeDetails2)(BridgeTypeDetails3)

04 – Welded (truss)05 – Unusual connection (truss)06 – Unknown connection (truss)07 – Brick form work (jack arch)08 – Timber form work (jack arch)09 – Corrugated iron form work (jack arch)10 – Form work unknown (jack arch)11 – Riveted (girder construction)12 – Welded (girder construction)13 – Girder construction unknown14 – Timber (girder construction)15 – Bridge plate16 – Polygonal top chord (Warren truss)17 – Standard plan18 – Jack arch runs perpendicular to stringers19 – Railroad rail members (truss and girder)20 – Toll/Operator’s houseNA – Not Applicable

ITEM V: TRUSS TYPE DETAIL 1 FIELD TYPE: Text(TrussTypeDetail1) FIELD SIZE: 2


INFORMATION: Records specific truss configuration, often named after the individual that holds the

patent.

CODING: 01 – King post02 – Queen post03 – Palmer arch-truss04 – Burr arch-truss05 – Long06 – Town lattice07 – Howe08 – Bowstring arch-truss09 – Fink10 – Bollman11 – Pennsylvania12 – Baltimore13 – Lenticular


ITEM V: TRUSS TYPE DETAIL 1 (CONT.) FIELD TYPE: Text(TrussTypeDetail1) FIELD SIZE: 2

14 – Stearns15 – Kellogg16 – Camelback17 – Truss leg bedstead18 – Wichert19 – Pratt20 – Warren21 – Parker22 – Unusual configurationNA – Not Applicable

ITEM W: TRUSS TYPE DETAIL 2 FIELD TYPE: Text(TrussTypeDetail2) FIELD SIZE: 2


INFORMATION: Records variants on the truss configuration that can be identified by examining the

arrangement of bridge members.

CODING: 1 – Half-hip2 – Double-intersection3 – Triple-intersectionNA – Not Applicable

ITEM X: ARRANGEMENT FIELD TYPE: Text(Arrangement) FIELD SIZE: 1


INFORMATION: For arch bridges with the deck passing between members of the structural system,distinguishes whether the deck is at the mid-point (half-through) or base (through)of the arch.

CODING: 1 – Half-through

2 – ThroughN – Not Applicable


ITEM Y: MOVABLE TYPE DETAIL FIELD TYPE: Text(MovableTypeDetail) FIELD SIZE: 1


INFORMATION: Denotes specific configuration and motion of movable span(s).

CODING: 1 – Retractile2 – Pontoon3 – Single-leaf bascule4 – Double-leaf basculeN – Not Applicable

ITEMS Z, AA, AB: INTEGRITY PROBLEMS 1, 2, 3 FIELD TYPE: Text(IntegrityProblems1) FIELD SIZE: 2(IntegrityProblems2)(IntegrityProblems3)


INFORMATION: Three fields that identify alterations to a bridge that affect its historic integrity.Does not reflect any structural deficiencies a bridge may have.

CODING: 01 – Raised vertical clearance

02 – Change in rail or parapet03 – Replacement of main members04 – Added main members (not original)05 – Parapet removed06 – Slab enlarged07 – Widened with additional members08 – Concrete veneer09 – Filled under arch rib or girder10 – Lengthened with additional members11 – Removed main members12 – MovedNA – Not Applicable

ITEM AC: ENGINEER/DESIGNER FIELD TYPE: Text(Engineer/Designer) FIELD SIZE: 1


INFORMATION: Identifies the jurisdictional level of the engineer or designer of the bridge.


ITEM AC: ENGINEER/DESIGNER (CONT.) FIELD TYPE: Text(Engineer/Designer) FIELD SIZE: 1

CODING: 1 – State2 – County3 – Local (city or village)4 – Known engineer/designer5 – State and local6 – County and known engineer/designer7 – Local and known engineer/designerU – Unknown

ITEM AD: NAME OF ENGINEER/DESIGNER FIELD TYPE: Text(Engineer/DesignerName) FIELD SIZE: 100


INFORMATION: Identifies the primary engineer or designer of the bridge.


ITEM AE: NAME OF BUILDER/MANUFACTURER FIELD TYPE: Text(Builder/ManufacturerName) FIELD SIZE: 100


INFORMATION: Identifies the builder or manufacturer of the bridge.


ITEMS AF-AH: SPECIAL RECOGNITION 1, 2, 3 FIELD TYPE: Text(SpecialRecognition1) FIELD SIZE: 1(SpecialRecognition2)(SpecialRecognition3)


INFORMATION: Identifies special aesthetic features and physical or historical associations that abridge may possess. Also records public acknowledgments of a bridge’ssignificance, including previous determinations of eligibility.


ITEMS AF-AH: SPECIAL RECOGNITION 1, 2, 3 (CONT.) FIELD TYPE: Text(SpecialRecognition1) FIELD SIZE: 1(SpecialRecognition2)(SpecialRecognition3)

CODING: 1 – Aesthetic treatment (see also Items AI-AL: Aesthetic Treatment)2 – Previously determined eligible district3 – Identified in surveys to local groups4 – Previously determined individually eligible5 – Covered8 – Known historic association (see also Item AM: Historic Association Detail)N – Not Applicable

ITEMS AI-AL: AESTHETIC TREATMENT 1, 2, 3, 4 FIELD TYPE: Text(AestheticTreatment1) FIELD SIZE: 2(AestheticTreatment2)(AestheticTreatment3)(AestheticTreatment4)


INFORMATION: Records decorative features that are applied to the superstructure.

CODING: 01 – Decorative portal

02 – Decorative rail or parapet03 – Decorative panels04 – Masonry veneer05 – Decorative arch06 – Decorative tower or cable stays07 – Decorative toll/operator's house08 – Decorative lighting09 – Concrete modillions or added features10 – Non-decorative parapetNA – Not Applicable

ITEM AM: HISTORIC ASSOCIATION DETAIL FIELD TYPE: Text(HistoricAssociationDetail) FIELD SIZE: 1


INFORMATION: Recognizes known links between a bridge and important events or people in the

past.


ITEM AM: HISTORIC ASSOCIATION DETAIL (CONT.) FIELD TYPE: Text(HistoricAssociationDetail) FIELD SIZE: 1

CODING: 1 – Unspecified2 – Depression-era funding3 – Association with individual4 – Memorial bridge5 – Bridge marker (not located on the structure)N – Not Applicable

ITEM AN: PLANS AVAILABLE UPDATE FIELD TYPE: Text(PlansAvailableUpdate) FIELD SIZE: 1

ORIGIN OF DATA: Historic Bridge Inventory – Year 2000: BIN File Review

INFORMATION: Indicates if plans for the bridge are available at the NYSDOT regional office.

CODING: Y – plans available at regional office

N – plans not available at regional officeU – unknown

ITEM AO: POSSIBLE HISTORIC DISTRICT FIELD TYPE: Text(PossibleHistoricDistrict) FIELD SIZE: 1

ORIGIN OF DATA: Historic Bridge Inventory – Year 2000: Field Survey

INFORMATION: Recognizes a concentration of historic resources adjacent to the bridge that could

possibly constitute a historic district.

CODING: Y – In or adjacent to a possible historic district (see also Items AP, AQ, and AR)

N – None identified


ITEM AP: ADJACENT STATE/LOCAL FIELD TYPE: Text

HISTORICAL MARKER FIELD SIZE: 1(AdjacentHistoricalMarker)


INFORMATION: Records the presence of a historical marker not related to the bridge.

CODING: Y – Historical marker present

N – None identified

ITEM AQ: LAND USE FIELD TYPE: Text(LandUse) FIELD SIZE: 1


INFORMATION: Describes land use(s) in the environs of a bridge where a possible historic district

has been identified.

CODING: 1 – Commercial2 – Industrial3 – Residential4 – Religious5 – Institutional6 – Park7 – Mixed commercial/residential8 – Other mixed useN – Not Applicable

ITEM AR: DEVELOPMENT FIELD TYPE: Text(Development) FIELD SIZE: 1


INFORMATION: Describes the density/type of development in the environs of a bridge where apossible historic district has been identified.

CODING: 1 – Urban

2 – Suburban3 – Village4 – RuralN – Not Applicable


ITEM AS: BRIDGE IDENTIFIED AS CONTRIBUTING FIELD TYPE: TextCOMPONENT OF ELIGIBLE DISTRICT FIELD SIZE: 1(BridgeContributingToDistrict)

ORIGIN OF DATA: Section 106 Documentation

INFORMATION: Status of bridge as component of an eligible or listed district.

CODING: 1 ! Contributing to district2 – Non-contributing to district3 – No eligible district identified4 – No evaluation for potential district

The following fields are for Current Historic Bridge Inventory table only:

ITEMS AT, AU: MANAGEMENT ACTIVITY – CURRENT 1,2 FIELD TYPE: Text(CurrentManagementActivity1) FIELD SIZE: 1(CurrentManagementActivity2)

ORIGIN OF DATA: Project information and Section 106 Documentation

INFORMATION: Records management activities completed for a National Register eligible or listed

bridge.

CODING: 1 – Rehabilitation maintaining historic integrity2 – Stabilized and closed3 – Bicycle/pedestrian traffic only4 – OtherN – Not applicable

ITEM AV, AW: YEAR OF MANAGEMENT ACTIVITY – CURRENT 1, 2 FIELD TYPE: Number(YRCurrentManagementActivity1) FIELD SIZE: 4(YRCurrentManagementActivity2)


INFORMATION: Records year of management activity.

CODING: Four-digit number. Default value is set to 0 (zero).


ITEMS AX-AZ: REHABILITATION ACTIVITY DETAIL – CURRENT 1, 2, 3 FIELD TYPE: Text(RehabilitationActivityDetail1) FIELD SIZE: 1(RehabilitationActivityDetail2)(RehabilitationActivityDetail3)


INFORMATION: Records rehabilitation activities conducted to maintain historic integrity of a

National Register eligible or listed bridge.

CODING: 1 – Rehabilitation of substructure2 – Replacement of members/elements in-kind3 – Decorative rail or parapet4 – Period lighting5 – Fabrication to match original elements6 – Repair of original structural elements7 – OtherN – Not applicable

ITEM BA: COMMENTS – CURRENT FIELD TYPE: Memo(Comments) FIELD SIZE: Unlimited


INFORMATION: Additional information about management activity.

CODING: Text

The following fields are for Historical Data for Removed and Replaced Bridges table only:

ITEMS AT, AU: MANAGEMENT ACTIVITY – HISTORIC 1, 2 FIELD TYPE: Text(HistManagmentActivity1) FIELD SIZE: 2(HistManagmentActivity2)


INFORMATION: Records management activities completed for a National Register eligible or listedbridge that has an inactive BIN.

CODING: 01 – Relocated

02 – Salvaged03 – Stored04 – Replaced with same basic bridge type05 – Replaced with different bridge type


ITEMS AT, AU: MANAGEMENT ACTIVITY – HISTORIC 1, 2 FIELD TYPE: Text(HistManagmentActivity1) (CONT.) FIELD SIZE: 2(HistManagmentActivity2)

06 – Demolished07 – HAER Documentation08 – Alternative or additional mitigation09 – Transferred to new owner10 – OtherNA – Not applicable

ITEM AV, AW: YEAR OF MANAGEMENT ACTIVITY- HISTORIC FIELD TYPE: Number(YRHistManagementActivity1) FIELD SIZE: 4(YRHistManagementActivity2)


INFORMATION: Records year of management activity.

CODING: Four-digit number. Default value is set to 0 (zero).

ITEM AX: COMMENTS – HISTORIC FIELD TYPE: Memo(Comments) FIELD SIZE: Unlimited


INFORMATION: Additional information about management activity.

CODING: Text

Historic Bridge Database Data Dictionary · 2015. 12. 15. · MEAD & HUNT – AKRF N133A076\N133-...

Documents

Transcript of Historic Bridge Database Data Dictionary · 2015. 12. 15. · MEAD & HUNT – AKRF N133A076\N133-...