20241216 13094900 1.0 FGDC CSDGM Metadata FALSE AP_FLIGHT_LINE 002 Geographic GCS_North_American_1983 Angular Unit: Degree (0.017453) <GeographicCoordinateSystem xsi:type='typens:GeographicCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/3.3.0'><WKT>GEOGCS[&quot;GCS_North_American_1983&quot;,DATUM[&quot;D_North_American_1983&quot;,SPHEROID[&quot;GRS_1980&quot;,6378137.0,298.257222101]],PRIMEM[&quot;Greenwich&quot;,0.0],UNIT[&quot;Degree&quot;,0.0174532925199433],AUTHORITY[&quot;EPSG&quot;,4269]]</WKT><XOrigin>-400</XOrigin><YOrigin>-400</YOrigin><XYScale>999999999.99999988</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>8.98315284119521e-09</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><LeftLongitude>-180</LeftLongitude><WKID>4269</WKID><LatestWKID>4269</LatestWKID></GeographicCoordinateSystem> 20260112 10495300 20260112 10495300 150000000 5000 dataset external 5a5e623f2f1754e1ac1730244bffa682caeb0e82 Scott Kiefer Bureau of Land Management (BLM), Oregon State Office GS0301 - Geographic Information System Specialist P.O. Box 2965 Portland OR 97208 US skiefer@blm.gov Name: Scott Kiefer Organization: Bureau of Land Management (BLM), Oregon State Office Position: GIS Specialist Role: Unknown Name: Scott Kiefer Organization: Bureau of Land Management (BLM), Oregon State Office Position: GIS Specialist Role: Unknown True Name: Scott Kiefer Organization: Bureau of Land Management (BLM), Oregon State Office Position: GS0301 - Geographic Information System Specialist Role: Unknown 20250422 ArcGIS Metadata 1.0 Eric Hiebenthal Bureau of Land Management, Oregon State Office GIS Data Management Specialist 503-808-6565 503-808-6419 P.O. Box 2965 Portland OR 97208 US ehiebent@blm.gov Arc GIS Feature Class Feature Class Winzip Winzip https://gbp-blm-egis.hub.arcgis.com/pages/oregon File Geodatabase Feature Class BLM-STATE Oregon Washington BLM-THEME Forest Geospatial Range Vegetation NONE Aerial Photography Bathymetry Contour Drone Hyperspectral Imagery LiDAR PrimaryData RADAR Remote Sensing Remotely Sensed Data Satellite UAS Unmanned Aircraft System U.S. Department of the Interior, Bureau of Land Management (BLM) BLM OR Aerial Photography Flightlines Line 2026-01-12 Bureau of Land Management Portland, Oregon vector digital data AP_FLIGHT_LINE: Line data depicting aerial photography flight lines over BLM lands in Oregon and Washington. This data is used for describing and locating remotely sensed data from imagery and elevation acquisition projects. Layer files are used to simplify searches by such means as lumping photography by decades or separating projects with large footprints. OR/WA BLM; Bureau of Land Management (BLM), Oregon State Office Corey Plank Bureau of Land Management Cartographer/Remote Sensing Acquisition (503) 808-6145 P.O. Box 2965 Portland OR 97204 US cplank@blm.gov Aerial Photography Bathymetry Contour Drone elevation environment Forest geoscientificInformation Geospatial Hyperspectral Imagery imageryBaseMapsEarthCover inlandWaters LiDAR Oregon PrimaryData RADAR Range Remote Sensing Remotely Sensed Data Satellite UAS Unmanned Aircraft System Vegetation Washington These data are provided by Bureau of Land Management (BLM) 'as is' and might contain errors or omissions. The User assumes the entire risk associated with its use of these data and bears all responsibility in determining whether these data are fit for the User's intended use. The information contained in these data is dynamic and may change over time. The data are not better than the sources from which they were derived, and both scale and accuracy may vary across the data set. These data might not have the accuracy, resolution, completeness, timeliness, or other characteristics appropriate for applications that potential users of the data may contemplate. The User is encouraged to carefully consider the content of the metadata file associated with these data. These data are neither legal documents nor land surveys, and must not be used as such. Official records may be referenced at most BLM offices. Please report any errors in the data to the BLM office from which it was obtained. The BLM should be cited as the data source in any products derived from these data. Any Users wishing to modify the data should describe the types of modifications they have performed. The User should not misrepresent the data, nor imply that changes made were approved or endorsed by BLM. This data may be updated by the BLM without notification. The BLM assumes no responsibility for errors or omissions. No warranty is made by the BLM as to the accuracy, reliability, or completeness of these data for individual use or aggregate use with other data; nor shall the act of distribution to contractors, partners, or beyond, constitute any such warranty for individual or aggregate data use with other data. Although these data have been processed successfully on computers of BLM, no warranty, expressed or implied, is made by BLM regarding the use of these data on any other system, or for general or scientific purposes, nor does the fact of distribution constitute or imply any such warranty. In no event shall the BLM have any liability whatsoever for payment of any consequential, incidental, indirect, special, or tort damages of any kind, including, but not limited to, any loss of profits arising out of the use or reliance on the geographic data or arising out of the delivery, installation, operation, or support by BLM. None, these data are considered public domain. ESRI Arc Catalog 10.4 true -125 -116 49.5 41.5 publication date 2026-01-12 A published revision of the Department Manual’s Part 305: Departmental Science Effects, Chapter 3: Integrity of Scientific and Scholarly Activities (305 DM 3), effective December 16, 2014, is available online at http://elips.doi.gov/ELIPS/DocView.aspx?id=4056. Scholarly information considered in Departmental decision making must be robust, of the highest quality, and the result of as rigorous scientific and scholarly processes as can be achieved. Most importantly, it must be trustworthy. This policy helps us to achieve that standard (http://www.doi.gov/scientificintegrity/index.cfm) -125 -116 49 42 Non classified None Last metadata review date: 20230609 Non classified None These data are provided by Bureau of Land Management (BLM) 'as is' and might contain errors or omissions. The User assumes the entire risk associated with its use of these data and bears all responsibility in determining whether these data are fit for the User's intended use. The information contained in these data is dynamic and may change over time. The data are not better than the sources from which they were derived, and both scale and accuracy may vary across the data set. These data might not have the accuracy, resolution, completeness, timeliness, or other characteristics appropriate for applications that potential users of the data may contemplate. The User is encouraged to carefully consider the content of the metadata file associated with these data. These data are neither legal documents nor land surveys, and must not be used as such. Official records may be referenced at most BLM offices. Please report any errors in the data to the BLM office from which it was obtained. The BLM should be cited as the data source in any products derived from these data. Any Users wishing to modify the data should describe the types of modifications they have performed. The User should not misrepresent the data, nor imply that changes made were approved or endorsed by BLM. This data may be updated by the BLM without notification. None, these data are considered public domain. None o Description: An instance of the Reference group o Geometry: Simple line features o Topology: No topology rules enforced o Integration Requirements: None This data is complete as of 20210701 Unknown. Based on an estimate of the amount of error expected in eyeballing and digitizing. Individual flight lines were either digitized from maps or created by snapping to photo center points. Individual project shapefiles were appended to a new geodatabase feature class. 2021-06-15 Corey Plank BLM Oregon State Office Lead Cartographer 503-808-6145 503-808-6190 PO Box 2965 Portland OR 97208-2965 US cplank@blm.gov 475 EPSG 6.5(3.0.1) AP_FLIGHT_LINE aerial photography flight line BLM Feature Class 475 OBJECTID Internal feature number. ESRI Sequential unique whole numbers that are automatically generated. Shape Feature geometry. ESRI Coordinates defining the features. PROJ_NAME Project Name The overall name for the remote sensing project. BLM Examples: O-98-SAL, Panther Creek ROLL Film Roll The film roll number for the project. The default value for this field is 0. BLM Examples: 2,19, 1X FLIGHT Flight Line The assigned photo flight line number unique to the project. The basic format is an integer value (overall flight line) with an optional modifier (letter or decimal value indicating a discontinuous piece. The letter “R” indicates a re-flight of rejected flight line. BLM Examples: 2A, 7, 33.4 STREAM_NAME Stream Name The stream name associated with the flight line. BLM Examples: Cow Creek, Swift Creek GLOBALID GLOBALID An alpha-numeric code that serves as the universal and unique identifier for each feature within the feature class or table of a geodatabase. Software generated value. A field of type UUID (Universal Unique Identifier) in which values are automatically assigned by the geodatabase when a row is created. This field is not editable and is automatically populated when it is added for existing data. BLM Example: {4747B796-44B4-4628-B069-2D496422E59F} SHAPE_Length Length of feature in internal units. Esri Positive real numbers that are automatically generated. For full attribute and domain descriptions see Remotely Sensed Data Indexes Spatial Data Standard. https://doimspp.sharepoint.com/sites/blm-or/datamgmt/Data%20Standards/Forms/Group%20by%20Standard.aspx Contact Data Steward for full descriptions and documentation.