TechniGraphics, Inc. 20080228 4th Quarter 2007 vector digital data This dataset includes buildings occupied by the headquarters of cabinet level state government executive departments, legislative offices buildings outside of the capitol building, offices and court rooms associated with the highest level of the judicial branch of the state government, and large multi-agency state office buildings. Because the research to create this data was primarily keyed off of the headquarters of cabinet level state government agencies, some state office buildings that don't house a headquarters for such an agency may have been excluded. Intentionally excluded from this dataset are government run institutions (e.g. schools, colleges, prisons, and libraries). Also excluded are state capitol buildings. State owned or leased buildings whose primary purpose is not to house state offices have also been intentionally excluded from this dataset. Examples of these include "Salt Domes", "Park Shelters", and "Highway Garages". All entities that have been verified to have no building name, have had their [NAME] attribute set to "NO NAME". If the record in the original source data had no building name and TGS was unable to verify the building name, the [NAME] attribute was set to "UNKNOWN". All phone numbers in this dataset have been verified by TGS to be the main phone for the building. If the building was verified not to have a main phone number, the [AREA] and [PHONE] fields have been left blank. All entities located on military bases have been removed from this dataset. The text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. All diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics. The currentness of this dataset is indicated by the [CONTDATE] attribute. Based upon this attribute, the oldest record dates from 2007/12/03 and the newest record dates from 2007/12/04. Homeland Security > Use Cases: Use cases describe how the data may be used and help to define and clarify requirements. > 1) There has been a natural or manmade disaster, such as a hurricane or earthquake. An assessment of what State property may be affected, and what State services may be impacted needs to be made. > 2) There is a predicted natural disaster, such as a hurricane. An assessment of what State property, personnel and services might be in the disaster's predicted footprint or path needs to be made. Preparations need to be made to evacuate personnel, secure property, and arrange for alternate methods of delivering the critical services that may be affected. > 3) There has been a terrorist threat against State property and/or personnel. Steps need to be taken to identify what is being threatened, counter the threat, and protect threatened personnel and property. Additional property may be impacted due to its proximity to the threatened property, or the threat may contain only a general spatial reference, and the spatial component of this dataset may need to be used to identify the threatened property. 20071203 20071204 ground condition Complete Unknown -123.034626 -122.641130 45.518210 44.922166 LCSH - Library of Congress subject headings (Washington, DC: LC, Cataloging Distribution Service) http://authorities.loc.gov/ Buildings ISO 19115 Topic Category structure LCSH - Library of Congress subject headings (Washington, DC: LC, Cataloging Distribution Service) http://authorities.loc.gov/ Oregon None None Mike Thompson TechniGraphics, Inc. Director of Geospatial Datasets Mailing and Physical Address

2000 Noble Drive

Wooster OH 44691 USA 330-263-6222 330-263-6294 mthompson@tgstech.com 8am - 5pm, Monday - Friday, Eastern Time DOD Unclassified Unclassified Microsoft Windows XP Professional Version 2002 Service Pack 2 TGS PinPoint v1.10.2 Metadata written using TKME by Peter N. Schweitzer (U.S. Geological Survey, Reston, VA 22092) version 2.9.17 <http://geology.usgs.gov/tools/metadata/> Metadata tested for compliance to FGDC-STD-001-1998 and converted to HTML using MP version 2.8.25 by Peter N. Schweitzer (U.S. Geological Survey) <http://geology.usgs.gov/tools/metadata/> For entities that were contacted, the name, address, city, state, and five (5) digit zip codes were verified to be correct as of the date indicated by the [CONTDATE] attribute. The existence of the entity was also verified, as well as whether or not it met the criteria for inclusion in this dataset. Four (4) digit zip code extensions were derived from USPS (United States Postal Service) data and were not verified. All records with a [GEOHOW] = "MANUAL" had the following checks performed on them. ID Check: The [ID] attribute is not blank and each of its values is unique. Coordinate Check: Coordinates are not null or zero and the x and y fields match the shape. Basic Address Check: Physical addresses were verified to be non blank and to not be a "PO Box", "General Delivery", "Highway Contract", or "Rural Route" address. Highway Address without Type Check: Physical addresses containing the word "Highway" or "Route" were verified to also contain a type designator such as "State", "US", or "County", if one actually exists for the highway or route. These type designators are often missing from addresses, leading to confusion if more than one "Highway" of the given number exists in an area. Basic Name Check: Entity name is not blank, is not the same as entity city, and has a minimum of 2 characters. Name does not contain punctuation characters that can interfere with database operations, such as " (quote) and * (asterisk). Basic Phone Check: All phone numbers (including the area code) are ten (10) numeric digits. Alphabetic characters have been converted to the corresponding numeric digit. City Check: Entity city is not blank and is found in the named places file within 25 miles. County FIPS to State Compare Check: The county represented by the tabular FIPS Code attribute is actually in the state specified by the state attribute. County Name to State Compare Check: The county represented by the tabular county name attribute is actually in the state specified by the state attribute. Phone Number Format Check: Phone numbers (including area code) were verified to be formatted as nnn-nnn-nnnn. NPA_NXX Check: Area codes (sometimes called "Number Planning Areas", or NPA's) and central office codes (sometimes known as exchanges, or NXX's) were validated against data from the North American Number Planning Administration (NANPA). In some cases, NPA-NXX combinations did not show up in the NANPA data but were verified to work. Area Code Distance Check: Area code (NPA) is valid and is within its area code boundary. Zip Code Check: The zip code is five (5) or nine (9) numeric digits, is listed in the postal database, is in the same state as indicated by the entity's [STATE] attribute, and is not a PO Box only zip code. Zip City Check: The entity's zip code and its city were verified to match according to the USPS Address Information System (AIS). Collocation Check: Entities with different addresses must not share the exact same geospatial location. Geographic Spell Check: Words that appear in the entity name were checked against a standard English word list (and Spanish word list for entities in Puerto Rico). Words not appearing in these standard word lists were then checked against names appearing in the Geographic Names Information System (GNIS) of geographic features that are located within 25 miles of the entity. Proper names were manually reviewed for correct spelling. See "Attribute_Accuracy_Report". Many of the checks described in that section check for both attribute accuracy and logical consistency. This dataset includes buildings occupied by the headquarters of cabinet level state government executive departments, legislative offices buildings outside of the capitol building, offices and court rooms associated with the highest level of the judicial branch of the state government, and large multi-agency state office buildings. Because the research to create this data was primarily keyed off of the headquarters of cabinet level state government agencies, some state office buildings that don't house a headquarters for such an agency may have been excluded. Initially, excluded from this dataset are government run institutions (e.g. schools, colleges, prisons, and libraries). Also excluded are state capitol buildings. State owned or leased buildings whose primary purpose is not to house state offices have also been intentionally excluded from this dataset. Examples of these include "Salt Domes", "Park Shelters", and "Highway Garages". The geographic location of contacted entities was verified to be correct relative to the street data and version indicated by the [ST_VENDOR] and [ST_VERSION] attributes. The horizontal accuracy is indicated by the [GEOPREC] attribute. A value of "BLOCKFACE" indicates the entity was geocoded on the correct block and correct side of the street. A value of "ONENTITY" indicates that the location is on the entity's facility, as determined by USGS DOQQ imagery, and is on the correct block and correct side of the street. Entities that are part of a larger institution (e.g., University Campus or Military Base) with "BLOCKFACE" precision may be located at the main entrance to the larger institution. State Partners and TGS research 2007 Unspecified vector digital data Online 2007 publication date State_Gov_Bldgs This was used as a source for State owned or leased buildings in the United States. NAVTEQ 2006 2006.4 CD-ROM 2006 publication date NAVTEQ_Streets_2006_Q4 NAVTEQ streets were used as reference for automatic geocoding and for the manual geolocating of entities during the Q407 processing. TGS 2007 Q4 Processing 1) Verified name, physical address, and phone numbers by contacting the entity or an authority responsible for the entity. 2) Determined or verified the geospatial location for the entity through contact with entity or authority responsible for entity. Entities were asked to describe their geospatial location relative to land marks visible in ortho imagery. 3) During PinPointing, TGS technicians looked for additional entitles to add to the dataset based upon the locations of the headquarters of cabinet level state agencies. 4) Every entity PinPointed during this update was reviewed by a TGS QC Technician. QC technicians are trained to look for inconsistencies within the data and between the data and reference sources, such as ortho imagery. Where inconsistencies exist, the TGS QC technician re-verified the information by contacting the entity. 5) All of the entities that were PinPointed during this update were examined as an aggregate (i.e., not every record was examined individually) by a TGS QC2 technician. The automated checks described above and in the Attribute_Accuracy_Report were used to find any inconsistencies that remained in the data. If necessary, information was re-verified. 6) County name and county FIPS codes were assigned through a spatial join. 7) Four (4) digit United States Postal Service (USPS) zip code extensions were assigned based upon the USPS Address Information System (AIS). 8) All text fields were set to all upper case. 9) Leading and trailing spaces were trimmed from all text fields. 10) Non printable and diacritic characters were removed from all text fields. State_Gov_Bldgs NAVTEQ_Streets_2006_Q4 20080228 OR_State_Government_Buildings Nicole Hackworth TechniGraphics, Inc. Project Manager Mailing and Physical Address

2000 Noble Drive

Wooster OH 44691 USA 330-263-6222 nhackworth@tgstech.com 8am - 5pm, Monday - Friday, Eastern Time Dataset copied.2008041616515200 Vector Entity point 23 0.000001 0.000001 Decimal degrees D_WGS_1984 WGS_1984 6378137.000000 298.257224 State Government Buildings in Oregon This dataset includes buildings occupied by the headquarters of cabinet level state government executive departments, legislative offices buildings outside of the capitol building, offices and court rooms associated with the highest level of the judicial branch of the state government, and large multi-agency state office buildings. TGS FID Internal feature number. ESRI Sequential unique whole numbers that are automatically generated. SHAPE Feature geometry. ESRI Coordinates defining the features. ID Unique identifier for feature. TGS Text METLNKID Link to Metadata. TGS Text FEATTYPE Geometry type of feature. TGS POINT Feature is represented by point. TGS SECCLASS Security classification of feature. TGS UNCLASSIFIED Entity is unclassified. TGS UNCLASSIFIED - TREAT AS FOUO Entity is unclassified and should be treated as "For Official Use Only". TGS NAME Name of entity. TGS Text AREA Three (3) digit telephone area code for entity. TGS Valid area codes without punctuation. Only numeric digits are used. A list of valid area codes can be found at http://www.nanpa.com PHONE Seven (7) digit telephone number for entity formatted as nnn-nnnn. All alphabetic characters have been translated to the corresponding numeric digit. TGS Phone numbers formatted as nnn-nnnn. Only numeric digits are used. The first three (3) digits (the exchange) must form a valid combination with the area code. A list of valid area code and exchange combinations can be obtained from http://www.nanpa.com ADDRESS Physical street address for entity. "PO Box", "General Delivery", "Rural Route", and "Highway Contract" addresses are not considered physical addresses and should not appear in this attribute. Some areas do not have regular city style addressing so entities in those areas may not have a street number. In such cases, the name of the road they are located on is listed in this attribute. Some rural areas may not have named roads. In these rare cases, this attribute will be blank. TGS Text ADDRESS2 Location within physical address, e.g., floor, suite, building. TGS Text CITY The name of the city associated with the entity's physical address. For physical addresses that the U.S. Postal Service (USPS) delivers to, this should be a "city" acceptable to the USPS as defined in their Address Information System (AIS). Sometimes the USPS does not deliver mail to a physical address but recognizes the location (i.e., they list the location as "undeliverable"). The cities associated with these locations are acceptable. In some cases, the USPS does not recognize individual physical addresses in a city, rather, they list the city as having "General Delivery". In these cases, the city and associated zip code are acceptable (the entity's [ADDRESS] attribute will contain a street address, not "general delivery"). The entity may not actually be located within the city limits of the "city" specified in its city field. Instead, it may actually be located within the city limits of another city. In some cases, the "city" that appears in this attribute may not even be a city in an administrative sense, but it is still an acceptable "city" to the USPS. An example of this is "Notre Dame, IN". There is no city in Indiana called "Notre Dame", but this is considered an acceptable city by the USPS for any delivery going to the University of Notre Dame which is actually located in the city of South Bend. "Notre Dame", like most USPS cities, is an easily recognized place, and it gives the user of the data a good general idea of where the entity is located (if the entity is located in a small municipality, the USPS "city" may be more recognizable than the name of the municipality), and it would be part of the address one would use to send a shipment to the entity's location. Using the USPS acceptable "city" also allows someone to do a logical consistency check between the zip code and the city by using the USPS AIS. Sometimes an entity may report a city that is not accepted by the USPS, and although TGS has tried to replace those cities with an acceptable alternative, some of them may remain in this dataset. TGS Text STATE Two (2) character abbreviation for state associated with the entity's physical address. In almost all cases this is the same as the state where the entity has been depicted geospatially. However, there are cases, particularly where an entity is part of a larger facility that cuts across state lines, where the entity's location may be depicted in a state other than the one indicated in this attribute. Also, the state in which an entity appears to be located may change depending on the scale of the state boundary theme being used. TGS Official USPS Abbreviations - State Abbreviations United States Postal Service http://www.usps.com/ncsc/lookups/usps_abbreviations.html ZIP Five (5) digit USPS zip code for entity's physical location. TGS USPS Address Information System - Domain is further restricted by only allowing physical (non PO Box) zip codes. United States Postal Service ZIPP4 Four (4) digit USPS zip code extension. This attribute was automatically assigned using the entity's physical address and USPS address information system (AIS) data. TGS USPS Address Information System (AIS) - ZIP9 United States Postal Service COUNTY County name where entity is located. TGS Geographic Names Information System (GNIS) US Department of the Interior - US Geologic Survey FIPS Five (5) digit FIPS (Federal Information Processing Standards) Code for the County where entity is located. The first two (2) digits represent the state and the last three (3) digits identify the county within the state. TGS Federal Information Processing Standards Publications - Counties and Equivalent Entities of the U.S., Its Possessions, and Associated Areas National Institute of Standards (NIST) http://www.itl.nist.gov/fipspubs/co-codes/states.txt DIRECTIONS Directions to entity location, or description of the entity's location. TGS Text EMERGTITLE Title of person or name of office for emergency point of contact. TGS Text EMERGPHONE Ten (10) digit telephone number of emergency point of contact formatted as nnn-nnn-nnnn. All alphabetic characters have been translated to the corresponding numeric digit. TGS Phone numbers, including area code, formatted as nnn-nnn-nnnn. A list of valid area code and exchange combinations can be found at http://www.nanpa.com EMERGEXT Telephone extension for emergency point of contact. TGS Text CONTDATE Date entity was contacted by TGS. TGS Date CONTHOW Method by which entity was contacted. TGS PHONE Entity was contacted by phone. TGS FAX Entity was contacted by fax. TGS MAIL Entity was contacted by mail. TGS EMAIL Entity was contacted by email. TGS WEB Entity information was gathered and/or verified by official entity website as a last resort. TGS ALT REF Geospatial reference information obtained from local authorities, e.g., downloadable parcel maps, 911 streets, and shapefiles. TGS GEODATE Date entity was geocoded by TGS. TGS Date GEOHOW Method by which entity was geocoded. TGS AUTO Entity was automatically geocoded. TGS MANUAL Entity was manually geocoded. TGS ADJUSTED Entity was shifted by TGS to an updated set of NAVTEQ streets. This only applies if the entity was manually geocoded by TGS to a previous version of NAVTEQ streets. TGS PROVIDED Entity was geocoded using coordinates provided by the state. TGS NAICSCODE NAICS (North American Industry Classification System) Code for entity. NAICS Codes (and NAICS Descriptions) have been assigned based upon the entity's primary function, regardless of if that is the function that qualified it to be included in this dataset. TGS North American Industry Classification System (NAICS 2002) US Census Bureau - http://www.census.gov/epcd/www/naics.html NAICSDESCR NAICS (North American Industry Classification System) Description for entity. The "Index Entries" that appear on the NAICS webpage (http://www.census.gov/epcd/www/naics.html) are being used to populate this attribute as opposed to the "NAICS Title". While there is a one to one correspondence between NAICS Codes and "NAICS Titles", there is a one to many relationship between NAICS Codes and the "Index Entries". By using the "Index Entries", we have placed the entities that make up this layer into more specific categories; however, the user of this data should be aware that this was not the intended purpose of these "Index Entries". The "Index Entries" were intended as a way to search the NAICS database and as a way of enumerating ways in which establishments falling under the given NAICS Code may be named. Thus, there are often two or more "Index Entries" that are synonyms, for example: "Prisons" and "Penitentiaries". In cases like this, we have standardized on one "Index Entry". NAICS Descriptions (and NAICS Codes) have been assigned based upon the entity's primary function, regardless of the function that qualified it to be included in this dataset. TGS PUBLIC PROPERTY MANAGEMENT SERVICES, GOVERNMENT PUBLIC PROPERTY MANAGEMENT SERVICES, GOVERNMENT-[NAICS Code 921190]: Entities that provide public property management services to the United States Government. TGS GEOLINKID Link ID for the street segment to which the entity was geocoded. Refer to the [ST_VENDOR] and [ST_VERSION] attributes for the street vendor and version that was used to geocode the entity. TGS Text X Longitude in WGS 84 Decimal Degrees. TGS -180 180 WGS 84 Decimal Degrees Y Latitude in WGS 84 Decimal Degrees. TGS -90 90 WGS 84 Decimal Degrees ST_VENDOR Indicates name of vendor providing original street data used for geocoding. TGS NAVTEQ NAVTEQ streets were used for geocoding. TGS TGS TGS drew in a new street segment that does not exist in the file supplied by NAVTEQ. TGS <BLANK> Entity was geocoded using coordinates provided by the original data source; therefore, the street vendor is unknown. TGS ST_VERSION Indicates the version of streets used for geocoding. TGS 2006Q4 2006Q4 NAVTEQ Street Data used for geocoding. TGS <BLANK> Entity was geocoded using coordinates provided by the original data source; therefore, the street version is unknown. TGS GEOPREC Geocoding precision. TGS BLOCKFACE Entity is geocoded to correct block and correct side of street per street data indicated by [ST_VENDOR] and [ST_VERSION]. TGS ONENTITY Entity is geocoded on entity rooftop per aerial imagery (in most cases USGS DOQQs). TGS <BLANK> Entity was geocoded using coordinates provided by the original data source; therefore, geocoding precision is unknown. TGS PHONELOC Indicates whether the phone number in the phone field rings to the actual location of the entity. TGS YES Phone number rings to the actual entity location. TGS NO Phone number does not ring to the actual entity location. It might ring to an administrative office or central location. TGS <BLANK> Unknown - It is not known if the entity's phone number rings to the entity's location. TGS QC_QA Organization that performed Quality Control/Quality Assurance on the record. TGS TGS TGS has performed Quality Control/Quality Assurance on the entity record after 01/01/2005. TGS <BLANK> The record is not TGS added or has not had Quality Control/Quality Assurance performed by TGS, or Quality Control/Quality Assurance was performed prior to 01/01/2005. TGS AGENCIES Indicates the agencies that are located in the building. Some of the values in this attribute have not been verified by TGS. TGS Text AGENCY_PH Indicates if the twelve digit phone number of an agency within the building. This phone number will correspond with the agency found in the [AGNECIES] field. TGS Phone numbers formatted as nnn-nnn-nnnn. Only numeric digits are used. 20080228 Mike Thompson TechniGraphics, Inc. Director of Geospatial Datasets Mailing and Physical Address

2000 Noble Drive

Wooster OH 44691 USA 330-263-6222 330-263-6294 mthompson@tgstech.com 8am - 5pm, Monday - Friday, Eastern Time FGDC Content Standards for Digital Geospatial Metadata FGDC-STD-001-1998 {BD94CF87-8E78-4CB9-A0C8-C9EF24F737FC}2008041616515200TRUEhttp://navigator.state.or.us/sdl/data/shapefile/k24/TGS_StateBuilding.zipHTTP