Panchromatic 1936 Digital Aerial Imagery for Western King County

Frequently-anticipated questions:

• What does this data set describe?
  1. How should this data set be cited?
  2. What geographic area does the data set cover?
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
  5. What is the general form of this data set?
  6. How does the data set represent geographic features?
  7. How does the data set describe geographic features?
• Who produced the data set?
  1. Who are the originators of the data set?
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
• Why was the data set created?
• How was the data set created?
  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
  3. What similar or related data should the user be aware of?
• How reliable are the data; what problems remain in the data set?
  1. How well have the observations been checked?
  2. How accurate are the geographic locations?
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
  5. How consistent are the relationships among the data, including topology?
• How can someone get a copy of the data set?
  1. Are there legal restrictions on access or use of the data?
  2. Who distributes the data?
  3. What's the catalog number I need to order this data set?
  4. What legal disclaimers am I supposed to read?
  5. How can I download or order the data?
• Who wrote the metadata?

Title:

Panchromatic 1936 Digital Aerial Imagery for Western King County

Abstract:

1936 aerial imagery for western King County from scanned 3 foot by 3 foot prints (boards 0.5 in pixels resampled to 1 foot).

Supplemental_Information: None

1. How should this data set be cited?

   King County DOT - Road Services, 200507, Panchromatic 1936 Digital Aerial Imagery for Western King County: 1936 Section Aerials None, King County DOT - Road Services, King County; WA.

   Other_Citation_Details: None

2. What geographic area does the data set cover?

   West_Bounding_Coordinate: -122.564084

   East_Bounding_Coordinate: -121.940337

   North_Bounding_Coordinate: 47.796379

   South_Bounding_Coordinate: 47.151528

3. What does it look like?

4. Does the data set describe conditions during a particular time period?

   Beginning_Date: 1936

   Ending_Date: 1937

   Currentness_Reference: ground condition

5. What is the general form of this data set?

   Geospatial_Data_Presentation_Form: raster digital data

6. How does the data set represent geographic features?
   1. How are geographic features stored in the data set?

      This is a Raster data set. It contains the following raster data types:

      • Dimensions 232500 x 150000 x 1, type Pixel

   2. What coordinate system is used to represent geographic features?

      The map projection used is Lambert Conformal Conic.

      Projection parameters:

      Standard_Parallel: 48.733333

      Standard_Parallel: 47.500000

      Longitude_of_Central_Meridian: -120.833333

      Latitude_of_Projection_Origin: 47.000000

      False_Easting: 1640419.947507

      False_Northing: 0.000000

      Planar coordinates are encoded using row and column
      Abscissae (x-coordinates) are specified to the nearest 1.000000
      Ordinates (y-coordinates) are specified to the nearest 1.000000
      Planar coordinates are specified in international feet

      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257222.
      

7. How does the data set describe geographic features?

   Entity_and_Attribute_Overview: This is a raster data set and has not tabular attributes.

   Entity_and_Attribute_Detail_Citation: None

1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
   • King County DOT - Road Services

2. Who also contributed to the data set?

   King County DOT - Map and Record Center, King County DOT Road Maintenance, King County GIS Center

3. To whom should users address questions about the data?

   Jeff Gregg
   King County Dept of Transportation - Road Services Engineering Services
   Engineer III
   201 S Jackson St
   Seattle, WA 98104-3856
   USA
   

   206-296-3715 (voice)
   206-296-0567 (FAX)
   jeffery.gregg@metrokc.gov
   

   Hours_of_Service: 8am-4pm M-F

Historical comparison and Archiving original documents

1. From what previous works were the data drawn?

   aerial prints (source 1 of 1)

   County, King, 1936, 1936 Aerial Photos for western King County.

   Type_of_Source_Media: 3'x3' aerial section prints

   Source_Scale_Denominator: Unknown

   Source_Contribution: Original hardboard-mounted aerial prints

2. How were the data generated, processed, and modified?

   Date: Sep-2006 (process 1 of 6)

   Scanned 3'x3' aerial section prints using a Xerox 8830 scanner (200 dpi) into a uncompressed TIFF format. The original 0.5 foot pixel resolution was resampled to 1 foot pixel.

   Person who carried out this activity:
   

   Jeff Gregg
   King County DOT Road Services Engineering Services
   Engineer III
   201 S. Jackson St
   Seattle, WA 98104-3856
   USA
   

   206-296-3715 (voice)
   206-296-0567 (FAX)
   jeffery.gregg@metrokc.gov
   

   Hours_of_Service: 8am-4pm M-F

   Data sources used in this process:

   • XES

   Data sources produced in this process:

   • TIFF

   Date: Dec-2006-200702 (process 2 of 6)

   Georeferenced section scans using KCMonument, t-net, hydro, parcels and PLSS layers for heads-up referencing

   Data sources used in this process:

   • TIFF

   Data sources produced in this process:

   • GeoTIFF

   Date: Feb-2007 (process 3 of 6)

   Mosaiced section scans into King County 7500' tiling sceme

   Person who carried out this activity:
   

   Jeff Gregg
   King County DOT - Road Services, Engineering Services
   Engineer III
   201 S Jackson St
   Seattle, WA 98104-3856
   USA
   

   206-296-3715 (voice)
   206-296-0567 (FAX)
   jeffery.gregg@metrokc.gov
   

   Hours_of_Service: 8am-4pm M-F

   Data sources used in this process:

   • GeoTIFF

   Data sources produced in this process:

   • idxp7500

   Date: May-2007 (process 4 of 6)

   7500 tiles delivered to enterprise Spatial Data Warehouse. Scripts used to assemble the correct set of 7500 tiles for each township-range tile. MrSid v5 used to compress TIFF files into township-range mosaics as Generation 3 sids at 7x compression.

   Data sources used in this process:

   • aabb_36p100.tif

   Data sources produced in this process:

   • txxryy_36p100.sid

   Date: May-2007 (process 5 of 6)

   7500 tiles were assembled and compressed at 15x into MrSid Generation 3 mosaics for the two zone tiles, znw_36p100.sid and zsw_36p100.sid.

   Data sources used in this process:

   • aabb_36p100.tif

   Data sources produced in this process:

   • zxx_36p100.sid

   Date: May-2007 (process 6 of 6)

   Entire set of 7500 tiles were assembled and mosaiced into Generation 3 MrSid mosaic as reg_36p100.sid. This mosaic was compressed at 30x.

   Data sources used in this process:

   • aabb_36p100.tif

   Data sources produced in this process:

   • reg_36p100.sid

3. What similar or related data should the user be aware of?

1. How well have the observations been checked?

   There are no attributes associated with these raster data formats.

2. How accurate are the geographic locations?

   None

3. How accurate are the heights or depths?

4. Where are the gaps in the data? What is missing?

   Western portion of King County WA

5. How consistent are the relationships among the observations, including topology?

   None

Are there legal restrictions on access or use of the data?

Access_Constraints:

Access to the data is limited to King County government agencies. The data is not to be redistributed in digital form to any other users. Limited use within a defined scope-of-work may be allowed for non-KC entities working for King County.

Use_Constraints:

King County digital data may not be reproduced or redistributed in any form or by any means without the express written authorization of the King County Department of Natural Resources and Parks/KCGIS-Center or King County Department of Transportation Road Services Division

1. Who distributes the data set? (Distributor 1 of 1)

   Jeff Gregg
   King County DOT - Road Services Division, Engineering Services
   Engineer III
   201 S Jackson St
   Seattle, WA 98104-3856
   USA
   

   206-296-3715 (voice)
   206-296-0567 (FAX)
   jeffery.gregg@metrokc.gov
   

   Hours_of_Service: 8am-4pm M-F

2. What's the catalog number I need to order this data set?

   /plibrary3/idxp7500/ortho_1936kc_pan/xy##_36p100.tif /plibrary3/idxptrmbr/ortho_1936kc_pan/txxryy_36p100.sid /plibrary3/idxpzone/northwest/znw_36p100.sid /plibrary3/idxpzone/southwest/zsw_36p100.sid /plibrary3/keyregion/orthoimagery/reg_36p100.sid

3. What legal disclaimers am I supposed to read?

   King County disclaims any warranty of use of any digital product or data beyond that for which it was designed. 1936 Aerials will not be distributed in digital form. For King County internal use only.

4. How can I download or order the data?
   • Availability in digital form:

     Data format:	SID
     Network links:	\\gisdw\kclib\plibrary3\idxptrmbr\ortho_1936kc_pan
     Media you can order:	Not Available (format Not applicable)

   • Cost to order the data: Data is not redistributable

5. Is there some other way to get the data?

   No orders for digital data are accepted

Dates:

Last modified: 14-May-2007

Metadata author:

Jeff Gregg
King County Dept of Transportation, Road Services Engineering Section
Engineer III
201 S Jackson St
Seattle, WA 98104-3856
USA

206-296-3715 (voice)
206-296-0567 (FAX)
jeffery.gregg@metrokc.gov

Hours_of_Service: 8am-4pm M-F

Metadata standard:

FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)

Metadata extensions used:

• <http://www.esri.com/metadata/esriprof80.html>