Trip tables are two-dimensional matrices containing the estimated number of trips between any two origin/destination points in the Puget Sound region. The tables for our region are aggregated into 3,700 neighborhoods (or “zones”) for convenience, so the matrices are 3700x3700 in size. You can think of a trip table as a big “from/to” table, on a neighborhood-to-neighborhood scale.
Includes signs installed and maintained by the Seattle Department of Transportation within the public right of way. The inventory is maintained in SDOT’s Infor/Hansen Asset Management System, and displayed in GIS as point events along a block face. To download the shapefile set or the kmz (compressed kml) right click on the file in the Attachment section and select Save As and select where you want it saved.
Transportation features including rail, trails and pedestrian walkways with address ranges & names derived from digital orthophotography and GPS.
Purpose: Developed to support transportation planning & engineering; transit routing & transit operations within the Department of Transportation. The data supports the ATIS application used by the Regional Automated Trip Planning group. This group assists Metro bus riders to find the best itinerary possible. Trans_Network is a derived data layer from the TNET (Transportation Network) Geodatabase. TNET is the authoritative transportation network layer for King County. On-going maintenance to TNET is provided by multiple agencies and jurisdictions in King County.
A concurrency travel shed is a geographic area within unincorporated King County where all development within the travel shed would be likely to use or be affected by traffic on arterials within the travel shed.
Purpose: The travel shed data depicts the geographic layer of unincorporated King County by which to measure existing traffic conditions against the concurrency level-of-service standard.
he TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2010 Census blocks nest within every other 2010 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces.