Description: This dataset is used citywide as base layer for many purposes and applications, including CityWorks. The street centerline is available for reference purposes only and does not represent exact engineering specifications. All street segments lie generally within the boundaries of the City of Oakland. Each street segment has a unique identifier attribute.Shapefile Field Name and Definitions:FieldDefinitionHJWSTREETS2_IDLegacy IDGEO_IDLegacy IDONEWAYCodes one-way streets, values are FT or TF. See below.MILESShape length in milesPREFIXPrefix for full street nameST_NAMEName of streetTYPELabel type of street (Street, Avenue, Way, etc.)SUFFIXSuffix for full street nameNAMEFull street nameL_LADDAddressing related fieldL_HADDAddressing related fieldR_LADDAddressing related fieldR_HADDAddressing related fieldCLASS1See BelowCLASS2See BelowHJWCODELocal Oakland Street type code (legacy)LLTEMPAddressing related fieldLHTEMPAddressing related fieldRLTEMPAddressing related fieldRHTEMPAddressing related fieldSHIELDLabeling field for highway shieldsL_ZIP_IDZIP identifier leftRULEIDUnknown legacy fieldR_ZIP_IDZIP identifier rightFACILITYIDCityworks facility identifierLEGACYIDCityworks Storage field for legacy facility IDWARRANTYDATECityworks Unused warranty date fieldINSTALLDATECityworks Unused install date fieldCONDITIONCityworks Unused condition fieldPOSTED_SPDPosted Speed Limit in miles per hour (Last Updated: July, 2018)FEDCLASSFederal Functional Classification. See below.LANES_LNumber of Lanes; see explanation below (Last Updated: July, 2018)LANES_RNumber of Lanes; see explanation below (Last Updated: July, 2018)LINETYPETo be populated with the type of line segment: street, alley, access road, trail, etc. This field will replace the legacy fields CLASS1 and CLASS2.OWNERTo be populated with the owner of the line segment: City of Oakland, Port of Oakland, Caltrans, East Bay Regional Park District, private development, and various institutions (e.g. Mills College, Merritt College).PavingIDLOCATIONCityworks fieldM_COMMENTStreet in moratorium Y =Yes, E=Expired.M_DATEPAVEDate of street segment paved.M_DATEENDMoratorium end date. Five years after M_DATEPAVE.M_PROJNUMProject number for the street paved.M_3YPStreet is in 2019 3-Year Plan. MS= major street, LS= local street, CD= council discretion, UC= utility coordinationMore Information:ONEWAY -Segments with FT or TF denote street segments that are one-way streets. FT means “From To” and TF means “To From”, and both tags refer to how the segments were drawn in GIS. For example, a one-way street labeled FT is one-way in the same direction that the segment was drawn (From To). A one-way street labeled TF is one-way in the opposite direction that the segment as drawn (To From).CLASS1 and CLASS2 -While each class has specific values, there is no correlation between each set of values. It appears that the Class2 field may have been created as an effort – never completed – to clean up the Class1 field. Class1• 10-14: Freeways, Interstates, and Freeway Ramps• 20-21: Local Streets• 30-33: Trails and Off Roadway Bike FacilitiesClass2• 0: No Data• 30, 33: Access Roads, Trails, and Paths• 31,32,34,35,36: Local StreetsFEDCLASS Interstate – 1Other Freeways or Expressways – 2Other Principal Arterial – 3Minor Arterial – 4Major Collector – 5Minor Collector – 6Local – 7LANES_L and LANES_R -The number of travel lanes on the street segment. For streets oriented mostly north/south, the left and right designations assume one is facing north. For streets oriented mostly east/west, the left and right designations assume one is facing east. For example, a street oriented north/south with one southbound lane and two northbound lanes has Lanes_L=1 and Lanes_R=2. Similarly, a one-way street with two westbound travel lanes has Lanes_L=2 and Lanes_R=0.
Copyright Text: City of Oakland's Public Works/ IT updating this data.
City of Oakland's Department of Transportation, Bicycle & Pedestrian Program, added the fields for POSTED_SPD, LANES_L, and LANES_R, and corrected the data in the field ONEWAY.
Description: The California Protected Areas Database (CPAD) contains data on lands owned in fee by governments, non-profits and some private entities that are protected for open space purposes. Data includes all such areas in California, from small urban parks to large national parks and forests, mostly aligned to assessor parcel boundaries. Data is collected by Holdings (parcels) which are aggregated to Units (commonly named areas within a county) and Super Units (commonly named areas generally).
Copyright Text: California Protected Areas Database (CPAD - www.calands.org).
Description: This feature class was updated from our 2012 city boundary GIS data by extracting city boundaries from Tax Area Services Section (TASS) of the California Board of Equalization 2013-2015 data release. The city boundary lines were digitized to match available county parcel base information provided from TASS in the format of CAD DWG layers and/or the Tax Rate Area (TRA) maps in PDF file. TIGER/Line Parcel data and ESRI Basemap imagery were used as reference layers. Additional 3 nautical mile offshore polygons were digitized for the coastal cities located from south of San Francisco to the Mexican border according to TRA maps. We keep the offshore polygons separate from their city boundaries on the lands, and put “3 nautical mile offshore” label in the attribute “Notes” for those polygons. The attributes include 2010 United States Census population and land area information, the city incorporated dates and web links are listed as well. This GIS version of California City boundaries is intended for general reference, planning, and study purposes only and does not represent official property boundary determinations.
Copyright Text: Division of Research, Innovation and System Information (DRISI) of California Department of Transportation (Caltrans); Tax Area Services Section (TASS) of the State of California Board of Equalization.