Description: <DIV STYLE="text-align:Left;"><P><SPAN>Docks for the rentable bike share program found around the City. This data is updated by the bike team periodically. Bike share is currently provided by Lyft Bay Wheels.</SPAN></P><P><SPAN>Data is updated as needed.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><DIV><DIV><P><SPAN>5G cellular antennas operated by AT&T, Verizon, or Mobilitie. The City of San Jose rents street light poles to telecom companies for their 5G technology antennas to provide faster and better wireless data coverage.</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Some streetlight poles, primarily downtown and in business corridors, have banner mounts for advertising purposes. The City collects revenue from event planners who use them to increase awareness of upcoming events and also uses them to advertise it's own messages.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Locations of all crashes known to the City since 1977. Crash reports are logged by the Police Deprtment and collected by the Department of Transportation which analyzes them to inform roadway safety improvements. The "Crash Vehicles Involved" dataset is related to each crash location.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Locations of all crashes known to the City since 1977. Crash reports are logged by the Police Deprtment and collected by the Department of Transportation which analyzes them to inform roadway safety improvements. The "Crash Vehicles Involved" dataset is related to each crash location.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Related to the "Crash Locations" dataset. The vehicle dataset contains one record for every vehicle involved in a crash (usually 2, but can be 1 if self inflicted, or more). Details about each crash involved vehicle can be found in the attributes.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Heritage trees are trees that have significant value to the City. A heritage tree may be found on public or private property and has special significance to the community due to its history, girth, height, species, or unique quality.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Locations of all street trees in the City of San Jose. Street trees are trees along city right-of-way and sidewalk, but do not include trees on private property or large lots like parks. It is the responsibility of the adjacent property owner to properly care for the street tree and comply with City laws and best practices. Permits must be obtained for most work on street trees to ensure it is done accordining to the requirements of the City code. Some street trees in City medians and road backups are maintained entirely by the City.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Locations of intersections and road crossings that have traffic signals, flashing beacons, or pedestrian flashing warnings in the City of San Jose. The attributes can be filtered to show only traffic signal intersections, or other specific types of pedestrian only crossings. Future and shutdown traffic signals / crossings are also present in the data.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>This dataset contains Average Daily Traffic (ADT) counts collected for the City of San Jose for the previous 15 years and is updated on a yearly basis. This dataset can be read as follows: The count location is given as “Collected on ‘Street One’, ‘Direction’, ‘Street Two’, in a ‘Travel Direction.’” ADT values are then given as: ‘ADT One’ and ‘ADT Two’ which correspond to the ADT collected in the recorded travel directions. If the street is a one-way street, a travel direction of ‘one-way’ is recorded and ‘ADT One’ and ‘ADT Two’ are left blank. ‘ADT’ corresponds to the total ADT which is a sum of ‘ADT One’ and ‘ADT Two.’ Putting it all together gets the following: “A total ADT of 39, 057 was recorded on 9/26/2018 along Murphy Rd. east of Oakland Road. Travel flows along Murphy Rd. in an East/West direction with a corresponding ADT One of 21,444 and ADT Two of 17,613.” Note that only counts collected after January 2018 will have a travel direction and corresponding ADT One and ADT Two values listed.</SPAN></SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>This dataset contains the roadway typology designation by street segment for non-residential streets in San Jose per the City’s 2040 General Plan. Typologies indicate which mode should be prioritized on a street. These are 1) Freeways/Expressways (Vehicles Prioritized), 2) Grand Boulevards (Transit Prioritized), 3) On-Street Primary Bike Facilities (Bikes Prioritized), 4) Main Streets (Pedestrians Prioritized), and 5) City/Local Connectors (All Modes Prioritized). This dataset uses the spatial data derived from the City’s Street Centerline dataset. Roadway Typologies are subject to change as part of the Department of Transportation’s Multimodal Transportation Improvement Plan (MTIP) Planning process.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The Utility Inspector layer shows utility inspector zone boundaries where utility inspectors review utility permits and installation of utilities in and around roadway. Utilities include water pipes, sewer pipes, natural gas pipes, communications conduit, and electric connections. </SPAN></P><P><SPAN>Data is updated as needed.</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><P><SPAN>Development inspector zone boundaries in San Jose, CA. Development Inspectors endute that the new development projects comply with applicable regulations and provide the necccessary public infrastructure including, but not limited to: streets, sidewalks, storm and sanitary sewers, streetlights, landscaping in frontages ans street islands, and traffic signals. </SPAN></P><P><SPAN>Data is updated as needed.</SPAN></P></DIV>
Name: Multimodal Transportation Improvement Plan Areas
Display Field: MTIPNAME
Type: Feature Layer
Geometry Type: esriGeometryPolygon
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>This dataset contains the Multimodal Transportation Improvement Plan (MTIP) Areas for the City of San Jose. An MTIP is an area-based prioritized list of projects and programs intended to facilitate realization of goals and objectives identified in a long-range plan. Projects and programs included in an MTIP are defined and designed enough to develop reasonable cost estimates. An MTIP is an intermediate step between conceptual transportation plans and programming of the projects and programs included in, or implied by, the conceptual transportation plans. This dataset is only updated periodically to reflect new MTIP planning efforts.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>This dataset contains Turning Movement counts (TMC) collected for the City of San Jose for the previous 10 years and is updated on a semi-annual basis. TMC data for autos, bicycles, and pedestrians are included where available. Auto and Bike counts include 12 different movements while Pedestrian counts include 8 movements. For pedestrian movements, “CW” stands for Clockwise and “CCW” stands for Counterclockwise to reflect movements through a crosswalk around an intersection. This dataset uses spatial data derived from the City’s Street Intersection layer.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>This dataset contains the Transportation Analysis Zones (TAZ) structure as currently used by the City of San Jose’s travel demand model.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>The City of San Jose contains a large number of road crossings over creek beds, waterways, and other roads. The locations of all bridge crossings, and if they are inspected by City staff or Caltrans, can be found in this dataset. Large freeway crossings are owned entirely by Caltrans and are not present in this data.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><DIV><P><SPAN>This dataset represents the railroad intersection within the City of San Jose, CA. </SPAN></P></DIV></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Streets in the City of San Jose that do not require undergrounding of electrical utility wires and which are designated for overhead pole power transmission.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><DIV><DIV><P><SPAN>A list of all road closures and partial closures planned in the City of San Jose public roads. Closures have date fields stating the period during which the closure is planned. Some roads listed will be closed intermittently during the time specified, but an exact time is not known. Further information can be found on the City's Cone Zone application: https://gis.sanjoseca.gov/maps/conezone</SPAN></P></DIV></DIV></DIV>
WAZESUBTYPE
(
type: esriFieldTypeString, alias: Closure Sub Type, length: 25
, Coded Values:
[ROAD_CLOSED_CONSTRUCTION: Lane Closures due to Construction]
, [ROAD_CLOSED_EVENT: Lane Closures due to an Event]
, [ROAD_CLOSED_HAULROUTE: Project Trucking Haul Route]
)
PROJECTDESCRIPTION
(
type: esriFieldTypeString, alias: Project Description, length: 255
, Coded Values:
[Delivery of construction materials: Delivery of construction materials]
, [Installation of new traffic signal: Installation of new traffic signal]
, [Installation of utility services: Installation of utility services]
, ...19 more...
)
TRAFFICIMPACTPRIMARY
(
type: esriFieldTypeString, alias: Primary Traffic Impact, length: 100
, Coded Values:
[Lane shift and lane closure, slow traffic thru construction zone: Lane shift and lane closure, slow traffic thru construction zone]
, [Lane shift, slow traffic thru construction zone: Lane shift, slow traffic thru construction zone]
, [Left turn lane closure, detour in effect: Left turn lane closure, detour in effect]
, ...10 more...
)
TRAFFICIMPACTSECONDARY
(
type: esriFieldTypeString, alias: Secondary Traffic Impact (Specific Time), length: 100
, Coded Values:
[Lane shift and lane closure, slow traffic thru construction zone: Lane shift and lane closure, slow traffic thru construction zone]
, [Lane shift, slow traffic thru construction zone: Lane shift, slow traffic thru construction zone]
, [Left turn lane closure, detour in effect: Left turn lane closure, detour in effect]
, ...10 more...
)
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Street sweeping routes in busy large roads. Multiple lines may be overlapping for each route. Major road sweeping is swept during nighttime hours by City Staff.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Street sweeping routes in residential areas. Multiple lines may be overlapping for each route. Residential sweeping is swept during daylight hours by a contractor.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Specific corridors designated by the Department of Transportation's Vision Zero program as vulnerable areas which will receive special attention for new safety improvements.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>The City of San Jose assesses the pavement condition of all city streets. The condition is checked every 3-5 years with a contracted electronic assessment vehicle. In the off years the pavement condition is updated by an estimate algorithm based on the use level of the road. The results of the current calendar year's PCI update is found in this layer.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Repaving projects of city streets that were completed in past calendar years.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Repaving projects of city streets that are underway this calendar year.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Repaving projects of city streets planned for the next three years. The three year plan is updated at the start of every calendar year.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Locations of red no parking curb faces in downtown San Jose. This layer may be expanded to citywide in the future.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><DIV><P><SPAN>This dataset represents the centerline of the railroads traveled way used to move passengers and freight within the City of San Jose, CA. </SPAN></P></DIV></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Districts established by law in the City of San Jose that require the undergrounding of electrical utility wires.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Vacant City owned lots and small strips of land need to have weeds removed regularly as they are unsightly and present a fire hazard. This layer shows the locations of lots where contractors remove the weeds and the type of removal work allowed in these areas.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>City streets often have medians and backups (side of road between sidewalk and fence) that contain decorative landscaping. The different types and locations of land covering are shown in this layer, as well as the maintenance responsibility.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Locations of downtown parking lots and garages that are open to the public always or part time for a fee or for free.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Illegal dumping of trash, furniture, and debris along the roadway reported and picked up by the City of San Jose. Reports are collected using the San Jose 311 smartphone app by local citizens.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>This layer contains information on deed restricted affordable rental housing projects in the City of San Jose - with funding committed to, under construction or completed. Data to be edited on a quarterly basis.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Faith based organizations in San Jose, CA. Includes churches, temples, parishes, mosques, synagogues, and others. The list is for reference, is not an official inventory, and not guaranteed to be accurate.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>A Letter of Map Amendment (LOMA) is an official amendment, by letter, to an effective National Flood Insurance Program (NFIP) map.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><DIV><DIV><P><SPAN>Poles that support street light lamps. Poles are usually simple steel, but can also be made of other decorative materials or are sometimes shared with wooden powerline poles. Poles are referred to as Vertical Assets by city staff as they often support more than just lamps. Poles can also include signals, cameras, radar, wireless, banners, and more. Other vertical asset layers with associated pole numbers can be found as other datasets. </SPAN></P><P><SPAN /></P><P><SPAN>This layer is updated on a weekly basis. The data includes records of removed streetlights as historical reference.</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><DIV><DIV><P><SPAN>Light fixture, or lamp types found on poles in the City of San Jose, CA. The city is working to replace all lamps in the city from the yellow low pressure sodium (LPS) to white light emitting diodes (LED) to improve visibility and cost.</SPAN></P><P><SPAN /></P><P><SPAN>This layer is updated on a weekly basis. The data includes records of removed streetlights as historical reference. It also includes around 4000 fixture records introduced from DOT's maintenance database. These maintenance records are incomplete, contains no location and still needs to be reconciled. Please be mindful when conducting queries. </SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Locations and types of parking meters operated by the City of San Jose to collect fees for on street parking.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>City installed and maintained bike parking racks. Many more bike racks exist citywide which are provided by private owners and shopping centers, but they may not be shown here.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>A sewer plug is a barrier inserted into a sanitary sewer line undergoing rehabilitation or repair to prevent flow into work areas.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>This dataset represents abandoned or disconnected sanitary pipes from the system and left underground.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Sanitary sewer manholes used for access to sewer pipes during inspection and maintenance. </SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Stormwater fittings are plugs placed at the end of a storm pipe to stop the flow of storm water. The plugs will be removed and pipe will be connected to another pipe during a future development.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Stormwater clean outs are structures that allow access to a storm drain for cleaning.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>A storm manhole is an entrance provided to a stormwater drain system for the purpose of inspection and cleaning.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Storm Inlets or Catch Basins are portion of a drainage facility through which stormwater enters.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Stormwater discharge points or outlets are used to reduce storm water velocity and dissipate the energy of flow leaving a storm drain before it empties into channels.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>City installed and maintained litter cans. Many more litter cans exist citywide which are provided by private owners and shopping centers, but they may not be shown here.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>The Site Address Points dataset was created and moved into GIS production January 31st, 2018. The feature class was created as part of a consultant project to add missing addresses to the GIS address points. Several sources of addresses such as AMANDA property records, County GIS points, Assessor records, a commercial mailing list, and the phone company's ALI database were checked against each other and the most valid addresses were added increasing the address points from the original 264,375 to 367,746 at the time of this entry. The project also adopted a NENA-compliant data model to become more NG 9-1-1 ready. Many fields may remain empty until NG 9-1-1 as the resources of information for these fields will become more available.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Condo points represent the condominium units within the Condo Parcel layer.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>The Base Flood Elevation (BFE) table is required for any digital data where BFE lines will be shown on the corresponding FIRM, with the exception of newly studied areas where a profile exists. The S_BFE contains information about the BFEs within a Flood Risk Project area. The spatial elements representing BFE features are lines extending from Special Flood Hazard Area (SFHA) boundary to SFHA boundary. Each BFE is represented by a single line with no pseudo-nodes. The use of BFE lines is only required in special cases. See FIRM Database Technical Reference document for more information.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>After a street is repaved the City does not allow digging in the street for construction for three years to keep the pavement good quality for as long as possible. The moratorium layer shows street segments currently not allowing digging.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Locations of zones of restricted high demand parking where only residents are allowed to park on street at certain times. Residents must apply to the City to obtain parking stickers.</SPAN></P></DIV>
EXPIRATIONDATE
(
type: esriFieldTypeString, alias: Expiration Date, length: 80
, Coded Values:
[January 31st of every EVEN year: January 31st of every EVEN year]
, [December 31st of every ODD year: December 31st of every ODD year]
, [August 31st of every ODD year: August 31st of every ODD year]
, ...13 more...
)
STREETNAME
(
type: esriFieldTypeString, alias: Street Name, length: 60
)
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Bike lanes, routes, and trails across the City. The City is converting many bike lanes to protected bike lanes. See the attributes of the data to filter the types of bike lanes or if they are existing, programmed, or planned. Programmed means that the route has been funded and scheduled to be built but is not built yet.</SPAN></P></DIV>
BIKEPLAN2020
(
type: esriFieldTypeString, alias: Bike Plan 2020, length: 50
, Coded Values:
[Primary Bikeway: Primary Bikeway]
, [Basic Bikeway: Basic Bikeway]
, [Not included in BP 2020: Not included in BP 2020]
)
STREETNAME
(
type: esriFieldTypeString, alias: Street Name, length: 50
)
STREETCLASS
(
type: esriFieldTypeString, alias: Street Class, length: 10
)
FULLSTREETNAME
(
type: esriFieldTypeString, alias: Full Street Name, length: 50
)
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Sanitarysewer pipe casing or coverings to protect damage from heavy load on the top of the pipe in areas like railroad crossings.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>This dataset represents abandoned or disconnected sanitary pipes from the system and left underground.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Stormwater pipe casing or coverings protect damage from heavy load on the top of storm pipes in areas like railroad crossings.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Stormwater pipe contains precipitation runoff water from impermeable surfaces such as roads, roofs and paved surfaces.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Stormwater pressurized pipes that are used to push stormwater upstream against gravity.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><DIV><DIV><P><SPAN>Street segments representing centerlines of all roadways within San Jose, CA. The City operates 1,500 miles of streets within its border.</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>The point where two or more streets intersect within the City of San Jose. The City has over 900 traffic signalized intersections, and 5,000 stop-signed intersections.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><DIV><DIV><P><SPAN>Private street segments representing centerlines of all roadways in San Jose and supports address geocoding, mapping, and e911 emergency dispatch. It also serves as a source for public works, transportation and other agencies that are responsible for the active management of the road network.</SPAN></P><P><SPAN /></P><P><SPAN>Private streets are maintained by property owners (typically apartment complexes) and, while part of the City's road network, are not under jurisdiction of the City. Some private streets have restricted access.</SPAN></P><P><SPAN> </SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><DIV><DIV><P><SPAN>Public Street within the City of San Jose, CA. </SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><DIV><DIV><P><SPAN>A representation of the edge of pavement of freeways to determine the furthest reaches of freeway's width. Freeways are divided highways with no tolls, pedestrians, signals or intersections.</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><DIV><DIV><P><SPAN>A representation of the edge of pavement of ramps on or off a freeway, highway, or interstate, to determine the furthest reaches of a freeway's , highway's, or interstate's width. Ramps are accesses or exits where freeways, highways or interstate roads split or merges.</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><DIV><DIV><P><SPAN>Public right of way line on which one side has parcels and the other is a public street. This dataset represents easements areas where the City of San Jose can perform projects for example digging out pipes or clean utility manholes.</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><DIV><DIV><P><SPAN>Private right of way line on which one side has parcels and the other is a private street. This dataset represents easements areas where the City of San Jose can't perform any projects because the areas is located inside a private property.</SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Footprints of new large developments underway by private developers in the City of San Jose, CA. Stage of progress can be found as a field. The layer is updated every few weeks.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Property based improvement district boundary in San Jose, CA. The district is formed around the downtown area and funds special projects and services exclusive to the downtown area.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>This dataset contains information about the flood hazards within the Flood Risk Project area. These zones are used by FEMA to designate the Special Flood Hazard Area (SFHA) and for insurance rating purposes. These data are the regulatory flood zones designated by FEMA. The spatial elements representing the flood zones are polygons. The entire area of the jurisdiction(s) mapped by the FIRM should have a corresponding flood zone polygon. There is one polygon for each contiguous flood zone designated. See pages 45- 47 in the FIRM Database Technical Reference document for Flood Zone and Zone Subtype Cross-Walk.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>The LOMR layer incorporates the results of effective Letter of Map Revisions (LOMRs) into FIRM data submitted to FEMA and is stored in the NFHL database for future PMRs. The S_LOMR feature class should contain at least one record for each LOMR incorporated into the NFHL. Multipart polygons are not allowed.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Some select parts of the City of San Jose are inside special tax districts known as Special Landscape Assessment Districts. An additional property tax is paid by the property owners in these districts to have enhanced landscaping often including fountains, flowers, exotic plants, and pocket parks. The different types and locations of land covering are shown in this layer, as well as the maintenance responsibility.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>The General Plan is an adopted statement of the official policy regarding the future character of development in the City of San José. It attempts to balance economic, housing, and transportation needs with environmental concerns.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>This dataset represents the urban growth boundaries in San Jose, CA.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Approved annexations or disannexations to and from the City of San Jose</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Boundaries depicting areas with natural asbestos, obtained from State Water Resources Control Board's GeoTracker.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>General service area boundaries of all the water providers in San Jose, CA.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>An above ground or below ground facility, such as a pond or tank, that temporarily stores stormwater runoff and subsequently releases it at a slower rate than it is collected by the drainage facility system.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>City of San Jose Redevelopment Agency Project Areas; Redevelopment Agencies were dissolved in February 2012 but some policies and provisions extend beyond this closure.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Wildland Urban Interface represents areas that have wildland/vegetation fire that can be a threat to structures or other human development.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><DIV><P><SPAN>The representation of real property areas, and may be combined with assessing and tax information. This feature class contains only parcels with a single APN and may include townhomes and may include condominiums with a single APN.</SPAN></P></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Since 1978, voters have elected council members from among candidates living within their district, plus the mayor who is elected at large citywide. With the subsequent release of decennial census data by the US Census Bureau in the years 1980, 1990, 2000, and 2010, City Council District boundaries have been adjusted to meet legal requirements and San Jose's own redistricting criteria. The City Council District boundaries are updated every ten years. </SPAN></P><P><SPAN>This is an archive dataset of the Council District boundaries as established in 1978 and effective through February 10, 2022. See CityCouncilDistrict dataset for current boundaries. This dataset is for historic reference and is not updated.</SPAN></P></DIV></DIV></DIV>
Copyright Text: Department of Planning, Building & Code Enforcement
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Since 1978, voters have elected council members from among candidates living within their district, plus the mayor who is elected at large citywide. With the subsequent release of decennial census data by the US Census Bureau in the years 1980, 1990, 2000, and 2010, City Council District boundaries have been adjusted to meet legal requirements and San Jose's own redistricting criteria. The City Council District boundaries are updated every ten years. </SPAN></P><P><SPAN>This is an archive dataset of the Council District boundaries as established in 2001 and effective until the 2011 redistricting was finalized. See CityCouncilDistrict dataset for current boundaries. This dataset is for historic reference and is not updated.</SPAN></P></DIV></DIV></DIV>
Copyright Text: Department of Planning, Building & Code Enforcement
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Since 1978, voters have elected council members from among candidates living within their district, plus the mayor who is elected at large citywide. With the subsequent release of decennial census data by the US Census Bureau in the years 1980, 1990, 2000, and 2010, City Council District boundaries have been adjusted to meet legal requirements and San Jose's own redistricting criteria. The City Council District boundaries are updated every ten years. </SPAN></P><P><SPAN>This is an archive dataset of the Council District boundaries as established in 1991 and effective until the 2001 redistricting was finalized. See CityCouncilDistrict dataset for current boundaries. This dataset is for historic reference and is not updated.</SPAN></P></DIV></DIV></DIV>
Copyright Text: Department of Planning, Building & Code Enforcement
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Since 1978, voters have elected council members from among candidates living within their district, plus the mayor who is elected at large citywide. With the subsequent release of decennial census data by the US Census Bureau in the years 1980, 1990, 2000, and 2010, City Council District boundaries have been adjusted to meet legal requirements and San Jose's own redistricting criteria. The City Council District boundaries are updated every ten years. </SPAN></P><P><SPAN>This is an archive dataset of the Council District boundaries as established in 1981 and effective until the 1991 redistricting was finalized. See CityCouncilDistrict dataset for current boundaries. This dataset is for historic reference and is not updated.</SPAN></P></DIV></DIV></DIV>
Copyright Text: Department of Planning, Building & Code Enforcement
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Since 1978, voters have elected council members from among candidates living within their district, plus the mayor who is elected at large citywide. With the subsequent release of decennial census data by the US Census Bureau in the years 1980, 1990, 2000, and 2010, City Council District boundaries have been adjusted to meet legal requirements and San Jose's own redistricting criteria. The City Council District boundaries are updated every ten years. </SPAN></P><P><SPAN>This is an archive dataset of the Council District boundaries as established in 1978 and effective until the 1981 redistricting was finalized. See CityCouncilDistrict dataset for current boundaries. This dataset is for historic reference and is not updated.</SPAN></P></DIV></DIV></DIV>
Copyright Text: Department of Planning, Building & Code Enforcement
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Tract Boundaries represent the geographic extent of non-incorporated areas within and outside of San Jose.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;"><P><SPAN>The Planning Areas Map includes fifteen (15) planning areas, which are large sub-areas of San José. Due to their permanent boundaries, these areas are especially valuable in the collection and analysis of data over long periods of time. For example, the Planning Division uses planning areas to monitor the supply and absorption of vacant land and to track and forecast development activity. </SPAN></P><P><SPAN>Data has never been updated.</SPAN></P></DIV>
Copyright Text: Department of Planning, Building & Code Enforcement
Description: <DIV STYLE="text-align:Left;font-size:12pt"><DIV><P><SPAN>These are locations that are to be used as an elevation reference and contain the official elevation and last known latitude and longitude. </SPAN></P></DIV></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>This layer represents the trails in San Jose, CA. It was created from legacy trails data as updated from San Jose Trails Program spread sheet. Last update spring 2018. Includes open and future status of trails. See attributes to filter desired data. </SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;"><P><SPAN>This layer represents information about the trails in San Jose, CA, broken down by reach. Trail reaches are individual trail segments that are generally separated by intersections with streets, railroad tracks, and waterways. This dataset is distinct from the Trails Primary layer in that it includes start and end locations for each reach. The attribute information in this dataset includes, among other categories, trail name, development status, property owner, trail type, surface, regional trail, length in miles, length in feet, park district, start location, and end location. </SPAN></P><P><SPAN>Data is updated on an as needed basis.</SPAN></P></DIV>
Copyright Text: Department of Parks, Recreation and Neighborhood Services
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Boundaries of community center buildings in San Jose, CA. Includes hub (large main center, 1 per council district), hybrid (fulfills multiple roles), neighborhood (small local), pool, and reuse (given to non-profits) centers, as well as open, closed status of centers. See attributes to filter desired data.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Parks in the City of San Jose, CA. Includes local and county parks within the city limits, as well as open, closed, and future status of parks. See attributes to filter desired data. Some city pocket parks are maintained separately, see the Department of Transportation's special districts landscaping and HOA landscaping layers.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>This is a representation of the outline of condominiums and contains only parcels (units) with multiple APNs such as in condominium situations.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;"><P><SPAN>Line feature data in Capital Improvement Projects like sanitary sewer lines, stormwater lines, streets, trails etc.</SPAN></P><P><SPAN>Data is updated Monthly.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;"><P><SPAN>Point feature data in Capital Improvement Projects like streetlight points, facilities locations, and traffic signal locations.</SPAN></P><P><SPAN>Data is updated Monthly.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;"><P><SPAN>Polygon feature data in Capital Improvement Projects like parks and airport.</SPAN></P><P><SPAN>Data is updated Monthly.</SPAN></P></DIV>
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>This demographics data package is part of a 3 layer set for Tracts, Block Groups, and Blocks across all of Santa Clara County. A field is present in each to allow filtering for the geometries that are only in The City of San Jose. Each of the data layers contains the most commonly requested demographic fields from the U.S. Census/American Community Survey. Please note these fields are not exactly the same as found in the census tables, the goal was to standardize the field names so that they will always remain the same regardless of if the census changes the field names or range values. San Jose GIS Enterprise staff will update these fields once a year. Please check the field that states the last time it was updated and from what source. Please also note that Tracts has the most data fields, Block Groups slightly less, and Blocks has very few. The finer scaled geometries have less data available from the U.S. Census, so those fields were dropped.</SPAN></P></DIV>
Copyright Text: U.S. Census, San Jose Enterprise GIS Team
LEPINDOEUROPEAN
(
type: esriFieldTypeInteger, alias: Limited English Proficiency Speaks Indo European
)
LEPASIANPACIFICISLAND
(
type: esriFieldTypeInteger, alias: Limited English Proficiency Speaks Asian or Pacific Islander
)
LEPOTHER
(
type: esriFieldTypeInteger, alias: Limited English Proficiency Speaks Other Language
)
LEPLANGMOSTSPOKEN
(
type: esriFieldTypeString, alias: Language Most Spoken by Those with Limited English Proficiency, length: 100
)
LEPLANGMOSTSPOKENPERCENT
(
type: esriFieldTypeString, alias: Language Most Spoken by Those with Limited English Proficiency (List of Percentages), length: 255
)
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>This demographics data package is part of a 3 layer set for Tracts, Block Groups, and Blocks across all of Santa Clara County. A field is present in each to allow filtering for the geometries that are only in The City of San Jose. Each of the data layers contains the most commonly requested demographic fields from the U.S. Census/American Community Survey. Please note these fields are not exactly the same as found in the census tables, the goal was to standardize the field names so that they will always remain the same regardless of if the census changes the field names or range values. San Jose GIS Enterprise staff will update these fields once a year. Please check the field that states the last time it was updated and from what source. Please also note that Tracts has the most data fields, Block Groups slightly less, and Blocks has very few. The finer scaled geometries have less data available from the U.S. Census, so those fields were dropped.</SPAN></P></DIV>
Copyright Text: U.S. Census, San Jose Enterprise GIS Team
LEPINDOEUROPEAN
(
type: esriFieldTypeInteger, alias: Limited English Proficiency Speaks Indo European
)
LEPASIANPACIFICISLAND
(
type: esriFieldTypeInteger, alias: Limited English Proficiency Speaks Asian or Pacific Islander
)
LEPOTHER
(
type: esriFieldTypeInteger, alias: Limited English Proficiency Speaks Other Language
)
LEPLANGMOSTSPOKEN
(
type: esriFieldTypeString, alias: Language Most Spoken by Those with Limited English Proficiency, length: 100
)
LEPLANGMOSTSPOKENPERCENT
(
type: esriFieldTypeString, alias: Language Most Spoken by Those with Limited English Proficiency (List of Percentages), length: 255
)
LANGENGLISHONLY
(
type: esriFieldTypeInteger, alias: Language Spoken English Only
)
LANGSPANISH
(
type: esriFieldTypeInteger, alias: Language Spoken Spanish
)
LANGINDOEUROPEAN
(
type: esriFieldTypeInteger, alias: Language Spoken Indo European
)
LANGASIANPACIFICISLAND
(
type: esriFieldTypeInteger, alias: Language Spoken Asian Pacific Islander
)
LANGOTHER
(
type: esriFieldTypeInteger, alias: Language Spoken Other
)
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>This demographics data package is part of a 3 layer set for Tracts, Block Groups, and Blocks across all of Santa Clara County. A field is present in each to allow filtering for the geometries that are only in The City of San Jose. Each of the data layers contains the most commonly requested demographic fields from the U.S. Census/American Community Survey. Please note these fields are not exactly the same as found in the census tables, the goal was to standardize the field names so that they will always remain the same regardless of if the census changes the field names or range values. San Jose GIS Enterprise staff will update these fields once a year. Please check the field that states the last time it was updated and from what source. Please also note that Tracts has the most data fields, Block Groups slightly less, and Blocks has very few. The finer scaled geometries have less data available from the U.S. Census, so those fields were dropped.</SPAN></P></DIV>
Copyright Text: U.S. Census, San Jose Enterprise GIS Team
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This dataset provides a framework for prioritizing investments from an equity standpoint using a simple scoring system. The index generates scores in four component areas: race (percent BIPOC), income (median household income), language (percent limited English proficiency), and education (percent of adults with less than HS diploma or equivalent). Each component score is on a scale of 1 (low priority) to 5 (high priority), where each value (1-5) covers approximately 20 percent of the population. A combined score is also provided in the EQUITYSCORECOMBINED field. The combined score is the sum of the race and income scores and is based on a scale of 2 to 10. The combined score has been adopted as the standard equity score. Language and education scores are provided for reference only and do not factor into the combined score.</SPAN></P><P><SPAN>This layer is based on demographics from ACS 2022 5-year estimates at the census tract level. New versions of the index are produced annually when ACS estimates are released. </SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>In 2020, neighborhood boundaries were established throughout the City in partnership with Council offices. These neighborhoods are collections of one or more census block groups. Neighborhood boundaries are not expected to be updated unless census geographies change. However, each year a new neighborhood demographics dataset is produced that aggregates ACS estimates by neighborhood. </SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>A representation of the neighborhood and business association boundaries across San Jose, CA. </SPAN></P><P><SPAN>Data is updated as needed.</SPAN></P></DIV></DIV></DIV>
Copyright Text: Department of Planning, Building & Code Enforcement
Description: <DIV STYLE="text-align:Left;"><P><SPAN>These are commercial areas along both sides of a street, which function in their neighborhoods or communities as central business districts, providing community focus and identity through the delivery of goods and services. In addition, Neighborhood Business Districts may include adjacent non-commercial land uses. Neighborhood Business Districts (NBDs) contain a variety of commercial and noncommercial uses which contribute to neighborhood identity by serving as a focus for neighborhood activity. This designation facilitates the implementation of a NBD Program by identifying target areas. The NBD Program seeks to preserve, enhance, and revitalize San José’s neighborhood-serving commercial areas through the coordination of public and private improvements, such as streetscape beautification, facade upgrading, business organization activities, business development, and promotional events. Consistent with its Implementation and Community Design Policies, the City will schedule, coordinate, and design public improvements in Neighborhood Business Districts so that allocated funding is consistent with the City’s growth strategies. </SPAN></P><P><SPAN>The NBD designation functions as an “overlay” designation which is applied to predominantly commercial land use designations. It is typically applied to two types of commercial areas. The first is older commercial areas where connected buildings create a predominant pattern of a continuous street façade with no, or very small setbacks from the sidewalk. Examples of this include Lincoln Avenue between Coe and Minnesota Avenues, Jackson Street between 4th and 6th Streets, and the segment of Alum Rock Avenue between King Road and Interstate 680. The second commercial area where the NBD overlay is applied typically contains a series of one or more of the following development types: parking lot strips (buildings set back with parking in front), neighborhood centers (one or two anchors plus smaller stores in one complex), or traditional, older commercial areas as described in the first NBD typology.</SPAN></P><P><SPAN>NBDs generally surround Main Street designations on the Transportation Network Diagram. The exceptions are The Alameda and East Santa Clara Street, which are noted as Grand Boulevards. NBDs can extend beyond the parcels immediately adjacent to a Main Street or Grand Boulevard, and they often overlap with Urban Village Boundary Area designations. Within an NBD overlay, residential and commercial uses, together with related parking facilities, are seen to be complementary uses, although commercial uses oriented to occupants of vehicles, such as drive-through service windows, are discouraged along major thoroughfares within NBD areas. In areas with an NBD overlay designation, any new development or redevelopment must conform to the underlying land use designation and applicable Urban Village Plans, Land Use Policies, and Community Design Policies. Such development must also conform to design guidelines adopted by the City.</SPAN></P><P><SPAN>Data has never been updated.</SPAN></P></DIV>
Copyright Text: Department of Planning, Building & Code Enforcement