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.

Boundary of incorporated areas in the City of San Jose, CA.Data is published on Mondays on a weekly basis.

Descriptions of Metropolitan Transportation Commission's 34 Super DistrictsSuper District #1 - Greater Downtown San Francisco: This area, the northeastern quadrant of the city, is bounded by Van Ness Avenue on the west, 11th Street on the southwest, and Townsend Street on the south. This Super District includes the following neighborhoods and districts: Financial District, Union Square, Tenderloin, Civic Center, South of Market, South Park, Rincon Hill, Chinatown, Jackson Square, Telegraph Hill, North Beach, Nob Hill, Russian Hill, Polk Gulch and Fisherman's Wharf. Treasure Island and Yerba Buena Island are also part of Super District #1.Super District #2 - Richmond District: This area, the northwestern quadrant of the city, is bounded by Van Ness Avenue on the east, Market Street on the southeast, and 17th Street, Stanyan Street, and Lincoln Way on the south. Super District #2 includes the following neighborhoods and districts: the Presidio, the Western Addition District, the Marina, Cow Hollow, Pacific Heights, Cathedral Hill, Japantown, Hayes Valley, Duboce Triangle, the Haight-Ashbury, the Richmond District, Inner Richmond, Outer Richmond, Laurel Heights, Sea Cliff, and the Golden Gate Park.Super District #3 - Mission District: This area, the southeastern quadrant of the city, is bounded by Townsend Street, 11th Street, Market Street, 17th Street, Stanyan Street, and Lincoln Way on the northern boundary; 7th Avenue, Laguna Honda, Woodside Avenue, O'Shaughnessy Boulevard and other smaller streets (Juanita, Casita, El Verano, Ashton, Orizaba) on the western boundary; and by the San Mateo County line on the southern boundary. Super District #3 includes the following neighborhoods and districts: China Basin, Potrero Hill, Inner Mission, Outer Mission, Twin Peaks, Parnassus Heights, Dolores Heights, Castro, Eureka Valley, Noe Valley, Bernal Heights, Glen Park, Ingleside, Ocean View, the Excelsior, Crocker-Amazon, Visitacion Valley, Portola, Bayview, and Hunters Point.Super District #4 - Sunset District: This area, the southwestern quadrant of the city, is bounded by Lincoln Way (Golden Gate Park) on the north; 7th Avenue, Laguna Honda, Woodside Avenue, O'Shaughnessy Boulevard and other smaller streets (Juanita, Casita, El Verano, Ashton, Orizaba) on the eastern boundary; and by the San Mateo County line on the southern boundary. Super District #4 includes the following neighborhoods and districts: Inner Sunset, the Sunset District, Sunset Heights, Parkside, Lake Merced District, Park-Merced, Ingleside Heights, West Portal and St. Francis Wood.Super District #5 - Daly City/San Bruno: This northern San Mateo County Super District includes the communities of Daly City, Colma, Brisbane, South San Francisco, Pacifica, San Bruno, Millbrae, and the north part of Burlingame. The boundary between Super District #5 and Super District #6 is Broadway, Carmelita Avenue, El Camino Real, Easton Drive, the Hillsborough / Burlingame city limits, Interstate 280, Skyline Boulevard, the Pacifica city limits, and the Montara Mountain ridgeline extending to Devil's Slide on the coast.Super District #6 - San Mateo/Burlingame: The central San Mateo County Super District includes the communities of Hillsborough, San Mateo, Foster City, Belmont, the southern part of Burlingame, and the coastside communities of Montara, Moss Beach, El Granada, and Half Moon Bay. The southern boundary of Super District #6 is the Foster City city limits, the Belmont/San Carlos city limits, Interstate 280, Kings Mountain, Lobitos Creek extending to Martins Beach on the coast.Super District #7 - Redwood City/Menlo Park: The southern San Mateo County Super District includes the communities of San Carlos, Redwood Shores, Redwood City, Atherton, Menlo Park, East Palo Alto, Woodside, Portola Valley, and the coastside communities of San Gregorio and Pescadero.Super District #8 - Palo Alto/Los Altos: This Santa Clara County Super District includes the communities of Palo Alto, Los Altos, Los Altos Hills, and the western part of Mountain View. Boundaries include the San Mateo County line, US-101 on the north, and Cal-85 (Stevens Creek Freeway) and Stevens Creek on the east.Super District #9 - Sunnyvale/Mountain View: This is the "Silicon Valley" Super District and includes the communities of Mountain View (eastern part and shoreline), Sunnyvale, Santa Clara (northern part), Alviso, and San Jose (northern part). Also included in this Super District is the "Golden Triangle" district. Super District #9 is bounded by US-101, Cal-85, Stevens Creek on the western boundary; Homestead Road on the southern boundary; Pierce Street, Civic Center Drive and the SP tracks in Santa Clara City; and Interstate 880 as the eastern boundary.Super District #10 - Cupertino/Saratoga: This Super District is located in south central Santa Clara County and includes the communities of Cupertino, Saratoga, Santa Clara City (southern part), Campbell (western part), San Jose (western part), Monte Sereno, Los Gatos and Redwood Estates. This area is bounded by Stevens Creek and the Santa Cruz Mountains on the west, Homestead Road on the north, Interstate 880/California Route 17 on the east; Union Avenue, Camden Avenue and Hicks Road (San Jose) also on the eastern boundary; and the Santa Clara/Santa Cruz county line on the south.Super District #11 - Central San Jose: This central Santa Clara County Super District is comprised of San Jose (central area), Santa Clara City (downtown area), and Campbell (east of Cal-17). The general boundaries of Super District #11 are Interstate 880/California Route 17 on the west; US-101 on the east; and the Capitol Expressway, Hillsdale Avenue, Camden Avenue, and Union Avenue on the south boundary.Super District #12 - Milpitas/East San Jose: This eastern Santa Clara County Super District includes the City of Milpitas, and the East San Jose communities of Berryessa, Alum Rock, and Evergreen. Boundaries include Interstate 880 and US-101 freeways on the west; San Jose City limits (Evergreen) on the south; and the mountains on the east.Super District #13 - South San Jose: This south-central Santa Clara County Super District includes the southern part of San Jose including the Almaden and Santa Teresa neighborhoods. Super District #13 is surrounded by Super District #10 on the west; Super District #11 on the north; Super District #12 on the northeast; and Super District #14 on the south at Metcalf Road (Coyote).Super District #14 - Gilroy/Morgan Hill: This area of Santa Clara County is also known as "South County" and includes the communities of Gilroy, Morgan Hill, San Martin and the Coyote Valley. Also included in this Super District are Loma Prieta (western boundary of the Super District) and Mount Hamilton in the northeastern, rural portion of Santa Clara County. This area is bounded by Santa Cruz and San Benito Counties on the south, and Merced and Stanislaus Counties on the eastern border.Super District #15 - Livermore/Pleasanton: This is the eastern Alameda County Super District including the Livermore and Amador Valley communities of Livermore, Pleasanton, Dublin, San Ramon Village, and Sunol. This Super District includes all of eastern Alameda County east of Pleasanton Ridge and Dublin Canyon.Super District #16 - Fremont/Union City: The southern Alameda County Super District includes the communities of Fremont, Newark and Union City. The boundaries for this Super District are the Hayward/Union City city limits on the north side; the hills to the immediate east; the Santa Clara/Alameda County line on the south; and the San Francisco Bay on the west.Super District #17 - Hayward/San Leandro: This southern Alameda County Super District includes the communities of Hayward, San Lorenzo, San Leandro, Castro Valley, Cherryland, and Ashland. The northern border is the San Leandro/Oakland city limits.Super District #18 - Oakland/Alameda: This northern Alameda County Super District includes the island city of Alameda, Oakland, and Piedmont. The Oakland neighborhoods of North Oakland and Rockridge are in the adjacent Super District #19. The border between Super Districts #18 and #19 are the Oakland/Emeryville city limits; 52nd and 51st Streets; Broadway; and Old Tunnel Road.Super District #19 - Berkeley/Albany: This northern Alameda County Super District includes all of Emeryville, Berkeley, and Albany, and the Oakland neighborhoods in North Oakland and Rockridge. The Super District is surrounded by the Alameda/Contra Costa County lines; the San Francisco Bay; and the Oakland Super District.Super District #20 - Richmond/El Cerrito: This is the western Contra Costa Super District. It includes the communities of Richmond, El Cerrito, Kensington, Richmond Heights, San Pablo, El Sobrante, Pinole, Hercules, Rodeo, Crockett, and Port Costa. The eastern boundary to Super District #20 is defined as the Carquinez Scenic Drive (east of Port Costa); McEwen Road; California Route 4; Alhambra Valley Road; Briones Road through the Regional Park; Bear Creek Road; and Wildcat Canyon Road to the Alameda/Contra Costa County line.Super District #21 - Concord/Martinez: This is one of three central Contra Costa County Super Districts. Super District #21 includes the communities of Concord, Martinez, Pleasant Hill, Clayton, and Pacheco. This area is bounded by Suisun Bay on the north; Willow Pass and Marsh Creek on the east; Mt Diablo on the southeast; and Cowell Road, Treat Boulevard, Oak Grove Road, Minert Road, Bancroft Road, Oak Park Boulevard, Putnam Boulevard, Geary Road, and Pleasant Hill Road on the south; and Briones Park, Alhambra Valley Road and Cal-4 on the west.Super District #22 - Walnut Creek: This central Contra Costa County Super District includes the communities of Walnut Creek, Lafayette, Moraga and Orinda. The latter three communities are more popularly known as Lamorinda. The border with Super District #23 generally follows the southern city limits of Walnut Creek.Super

Land Use Zoning Districts in San Jose, CA.

A dataset containing zip codes in San Jose, California, and their respective populations.

This dataset includes open, closed, future, seasonal, and under construction parks and trails in San Jose, Santa Clara County, and parts of San Mateo County. It covers trail land and parkland owned by and/or maintained by the San Jose Department of Parks, Recreation and Neighborhood Services, other San Jose city departments, City of San Jose, City of Santa Clara, Santa Clara County, State of California, Federal government, various school districts, Caltrans, Santa Clara Water District, Valley Transit Authority, Midpen Open Space Authority, and other agencies. Privately owned parks and open space are included as well. Parkland open space types in this dataset include community centers, community gardens, civic grounds, dog parks, libraries, neighborhood parks, open space, school grounds, special districts, trails and trail lands, privately owned public open spaces (POPOS), private recreation facilities, proposed trails, regional parks, reuse centers, sports facilities, and trails. Attribute information in this dataset includes, among other information, park name, address (often street and cross street), park type, park class, park subclass, current status, date opened, Park District, acreage, developed acreage, undeveloped acreage, open space acreage, park supervisor, park manager, park owner, PBCE Planning Area, Specific Plan or Urban Village area, and notes.Data is published on Mondays on a weekly basis.

The Santa Clara County Planning Office is part of the Department of Planning and Development. Their primary function is to plan and regulate land use and development within the unincorporated portions of Santa Clara County. Other responsibilities include policy analysis, GIS services, research and technical assistance relating to land use, housing, environmental protection, historic preservation and demographics. The Geographic Information Services Department has taken on all those activities related to GIS data and GIS process and procedures that cross organizational boundaries. Santa Clara County encompasses 15 cities and approximately 1.7 million people. This coverage can be used for basic applications such as viewing, querying, and map output production, or to provide a basemap to support graphical overlays and analyses of geospatial data.

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. Data has never been updated.

The California Association Local Agency Formation Commissions defines a sphere of influence (SOI) as "a planning boundary outside of an agency’s legal boundary (such as the city limit line) that designates the agency’s probable future boundary and service area." This feature set represents the SOIs of the incorporated jurisdictions for the San Francisco Bay Region. The Metropolitan Transportation Commission (MTC) updated the feature set in late 2019 as part of the jurisdiction review process for the BASIS data gathering project. Changes were made to the growth boundaries of the following jurisdictions based on BASIS feedback and associated work: Antioch, Brentwood, Campbell, Daly City, Dublin, Fremont, Hayward, Los Gatos, Monte Sereno, Newark, Oakland, Oakley, Pacifica, Petaluma, Pittsburg, Pleasanton, San Bruno, San Francisco (added to reflect other jurisdictions whose SOI is the same as their jurisdiction boundary), San Jose, San Leandro, Santa Clara, Saratoga, and Sunnyvale. Notes: With the exception of San Mateo and Solano Counties, counties included jurisdiction (city/town) areas as part of their SOI boundary data. San Mateo County and Solano County only provided polygons representing the SOI areas outside the jurisdiction areas. To create a consistent, regional feature set, the Metropolitan Transportation Commission (MTC) added the jurisdiction areas to the original, SOI-only features and dissolved the features by name.Because of differences in base data used by the counties and the MTC, edits were made to the San Mateo County and Solano County SOI features that should have been adjacent to their jurisdiction boundary so the dissolve function would create a minimum number of features. Original sphere of influence boundary acquisitions:Alameda County - CityLimits_SOI.shp received as e-mail attachment from Alameda County Community Development Agency on 30 August 2019 Contra Costa County - BND_LAFCO_Cities_SOI.zip downloaded from https://gis.cccounty.us/Downloads/Planning/ on 15 August 2019Marin County - 'Sphere of Influence - City' feature service data downloaded from Marin GeoHub on 15 August 2019Napa County - city_soi.zip downloaded from their GIS Data Catalog on 15 August 2019 City and County of San Francisco - does not have a sphere of influence San Mateo County - 'Sphere of Influence' feature service data downloaded from San Mateo County GIS open data on 15 August 2019 Santa Clara County - 'City Spheres of Influence' feature service data downloaded from Santa Clara County Planning Office GIS Data on 15 August 2019 Solano County - SphereOfInfluence feature service data downloaded from Solano GeoHub on 15 August 2019 Sonoma County - 'SoCo PRMD GIS Spheres Influence.zip' downloaded from County of Sonoma on 15 August 2019

These are locations that are to be used as an elevation reference and contain the official elevation and last known latitude and longitude. App: The data can be viewed in web map format at: Survey BenchmarksData is published on Mondays on a weekly basis.

This layer was created for the redistricting project map. BUSD provided a powerpoint file that showed the boundaries since they could not locate the original shapefile that was used. The core information used the generate the boundaries are the image in the powerpoint file and the 2020 census block boundaries. The source of image used is described below by the original contractor Bruce Wicinas. I was drafted to help BUSD around 1991. At that time they used planning software authored by a San Jose company, "Educational Data Systems." This was long before ESRI was known to the likes of school districts or acknowledged by the Census Bureau. "Educational Data Systems," which had many school district clients around the U.S., performed their own particle-ization of school district geography. They divided districts into rectangles of approximately 4 - 8 city blocks. These they called "planning areas." They were convenient. BUSD they divided into 445, a number neither too fine nor too coarse.Many years later, .shp files became widely available. Alas, not all Planning Area perimeters coincide with line segments of .shp files. In the Berkeley flatlands the discrepancies are not so bad. But in the hills, there aren't "blocks" but meandering strips. "Planning Areas" have line segments which don't correspond to streets or perimeters of .shp files.About 15 years ago I enhanced my custom software to read shp files. Thus I could superimpose Planning Areas and .shp files, observing the overlap discrepancies. I'll omit for now the rest of this story; what I did about the discrepancy between census Block Groups and Planning Areas. I could go into that if you are interested.I got "Planning Areas" into my custom software from the ancient EdSys data, somehow ,decades ago. I may have read a file containing polygon coordinates. At that time I could export the planning area polygons via DXF. But they have no relationship to .shp. I could provide a representation of GIS planning areas in coordinates such as "State Plane" but this probably does you no good. I have never written an ".shp" file exporter. The .shp file format is mind-boggling; archaic compared to modern methods.About 25 years ago I wrote an on-line means by which staff at BUSD can type in a Berkeley address and get the corresponding socio-ec category number. It does this by determining the "planning area number" - 1 through 445 - containing the address. That on-line software could provide the attendance zone as well but no one ever asked for that. The student assignment software used by the high school and by admissions performs that function internally. Every student has an attendance zone number as soon as they get added to the database.

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.Data is published on Mondays on a weekly basis.

Storm Water Structure is a Point FeatureClass representing the various storm water structures in the City of Cupertino. It is primarily used as an inventory layer in Cityworks and as a reference layer. The layer is updated as needed by the Public Works Department and the GIS Division. Storm Water Structure has the following fields:

OBJECTID: Unique identifier automatically generated by Esri type: OID, length: 4, domain: none

Enabled:

type: SmallInteger, length: 2, domain: EnabledDomain domain values:['False', 'True']

AncillaryRole:

type: SmallInteger, length: 2, domain: AncillaryRoleDomain domain values:['None', 'Source', 'Sink']

AssetID: Cupertino maintained GIS primary key type: String, length: 20, domain: none

LegacyID: Old identifiers used to track asset migration type: String, length: 20, domain: none

Location: Further description of the location type: String, length: 50, domain: none

Status: The active or construction status of the asset in the field type: String, length: 20, domain: pwStatus domain values:['Abandoned', 'Proposed', 'Auction', 'Denied', 'Active', 'Removed', 'Not Connected']

OwnedBy: Organization which owns the asset type: String, length: 50, domain: shdOwnedBy domain values:['Cupertino', 'San Jose Water', 'CalTrans', 'PGE', 'Los Altos', 'Santa Clara', 'Private HOA', 'Saratoga', 'Other Public', 'Santa Clara County', 'San Jose', 'Santa Clara Valley Water District', 'Private', 'California Water Service', 'State Parks', 'Sunnyvale', 'Cupertino Sanitary District', 'CWA']

MaintainedBy: Organization who is responsible for maintenance of asset type: String, length: 50, domain: shdOwnedBy domain values:['Cupertino', 'San Jose Water', 'CalTrans', 'PGE', 'Los Altos', 'Santa Clara', 'Private HOA', 'Saratoga', 'Other Public', 'Santa Clara County', 'San Jose', 'Santa Clara Valley Water District', 'Private', 'California Water Service', 'State Parks', 'Sunnyvale', 'Cupertino Sanitary District', 'CWA']

PlanNumber: Origniating plan number if known type: String, length: 50, domain: none

PlanName: The name of the plan associated with the storm water structure type: String, length: 50, domain: none

AsbuiltDate: Asbuilt date type: Date, length: 8, domain: none

PrimaryImage: Hyperlink to photo or DMS type: String, length: 100, domain: none

CreateDate: The date the database row was initially created type: Date, length: 8, domain: none

UpdateDate: The date the database row was last updated type: Date, length: 8, domain: none

DataSource: Description of what methods were used for data capture/migration type: String, length: 100, domain: shdDataSource domain values:['Digitized Plan as Reference', 'GPS SubFoot', 'Unknown Source', 'iStreetView', 'Field Verified', 'GPS SubMeter', 'Digitized Landbase as Reference', 'Legacy WO System', 'Digitized Ortho as Reference', 'Approximated Historical Source', 'Need Verification', 'Cogo from Plans']

SubWatershed: Field indicating what sub water shed is associated with the storm water structure type: String, length: 10, domain: swSubWaterShed

InstallDate: The date the storm water structure was installed type: Date, length: 8, domain: none

StructureType: Field indicating the type of storm water structure type: String, length: 20, domain: swStructureType domain values:['Thru Curb Drain', 'Area Drain', 'Catch Basin', 'BubbleUp', 'Pump Station', 'Outfall', 'Drop Inlet', 'Treatment Device', 'Unknown', 'Manhole', 'Clean Out', 'Dry Well', 'Inlet Culvert', 'Energy Dissipator']

IsCityStandard:

type: String, length: 4, domain: shdBooleanYesNo domain values:['Yes', 'No']

Depth:

type: Double, length: 8, domain: none

RimElev:

type: Double, length: 8, domain: none

AccessDiameter: Field indicating the diameter of the strucutre access type: SmallInteger, length: 2, domain: swAccessDiameter domain values:['24 inch', '48 inch', '36 inch']

CoverType: Filed indicating the cover type of the associated storm water structure type: String, length: 15, domain: swCoverType domain values:['Grate', 'Standard Lid', 'Bolt Down', 'Open Pipe']

HasHeadWall: Field indicating whether or not the pipe has a head wall type: String, length: 4, domain: shdBooleanYesNo domain values:['Yes', 'No']

HasFlapGate: Field indicating whether or not the pipe has a flap gate type: String, length: 4, domain: shdBooleanYesNo domain values:['Yes', 'No']

HasLadder: Field indicating whether or not the pipe has a ladder type: String, length: 4, domain: shdBooleanYesNo domain values:['Yes', 'No']

HasStencil: Field indicating whether or not the pipe has a stencil type: String, length: 4, domain: shdBooleanYesNo domain values:['Yes', 'No']

HasButton: Field indicating whether or not the pipe has a button type: String, length: 4, domain: shdBooleanYesNo domain values:['Yes', 'No']

HasPrivateBMP: Field indicating whether or not the pipe has a private BMP type: String, length: 4, domain: shdBooleanYesNo domain values:['Yes', 'No']

ErrosionControl:

type: String, length: 10, domain: swErosionControl domain values:['Boulder', 'Sacrete', 'Gabion', 'RipRap', 'Concrete', 'T']

IsCheckPoint:

type: String, length: 4, domain: shdBooleanYesNo domain values:['Yes', 'No']

IsInlineCheckValve:

type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']

Rotation: Field used for assigning rotation degree in Maplex Labeling Engine type: Double, length: 8, domain: none

CheckValveInstallDate: The date the check valve was installed type: Date, length: 8, domain: none

CheckValvePlanNumber: The plan number associated with the check valve type: String, length: 50, domain: none

HasHeavyGrate: Field indicating whether or not the pipe has a heavy grate type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']

ManualClean:

type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']

IsFloodProne:

type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']

BuinessLotFeed: EnterTextDescription type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']

hasSmartCover: Field indicating whether or not the pipe has a smart cover type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']

hasInspection: Field indicating whether or not the pipe has an inspection type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']

Shape: Field that stores geographic coordinates associated with feature type: Geometry, length: 4, domain: none

GlobalID: Unique identifier automatically generated for features in enterprise database type: GlobalID, length: 38, domain: none

EOA:

type: String, length: 50, domain: none

DeviceModelType: The model type of the storm water structure device type: String, length: 50, domain: swDeviceModelType domain values:['Pipe Screen', 'Manual Retractable', 'Wing Gate']

HasTrashCaptureInsert: Field indicating whether or not the pipe has a trash capture insert type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']

TrashCaptureInsertManufacturer: The manufacturer of the trash capture insert type: String, length: 255, domain: swStructureManufacturer domain values:['Hydra', 'United', 'Stormtek', 'REM']

TrashCaptureInsertDeviceModelTy: The model type of the trash capture device type: String, length: 50, domain: swDeviceModelType domain values:['Pipe Screen', 'Manual Retractable', 'Wing Gate']

TrashCaptureInsertInstallDate: The date the trash capture insert was installed type: Date, length: 8, domain: none

HasCurbScreen: Field indicating whether or not the pipe has a curb screen type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']

CurbScreenManufacturer: The manufacturer of the curb screen type: String, length: 255, domain: swStructureManufacturer domain values:['Hydra', 'United', 'Stormtek', 'REM']

CurbScreenDeviceModelType: The model type of the curb screen type: String, length: 50, domain: swDeviceModelType domain values:['Pipe Screen', 'Manual Retractable', 'Wing Gate']

CurbScreenInstallDate: The date the curb screen was installed type: Date, length: 8, domain: none

HasDebrisRack: Field indicating whether or not the pipe has a debris rack type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']

DebrisRackManufacturer: The manufacturer of the debris rack type: String, length: 255, domain: swStructureManufacturer domain values:['Hydra', 'United', 'Stormtek', 'REM']

DebrisRackDeviceModelType: The model type of the debris rack type: String, length: 50, domain: swDeviceModelType domain values:['Pipe Screen', 'Manual Retractable', 'Wing Gate']

DebrisRackInstallDate: The date the debris rack was installed type: Date, length: 8, domain: none

HasDrainInsert: Field indicating whether or not the pipe has a drain insert type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']

DrainInsertManufacturer: The manufacturer of the drain insert type: String, length: 255, domain: swStructureManufacturer domain values:['Hydra', 'United', 'Stormtek', 'REM']

DrainInsertDeviceModelType: The model type of the drain insert type: String, length: 50, domain: swDeviceModelType domain values:['Pipe Screen', 'Manual Retractable', 'Wing Gate']

DrainInsertInstallDate: The date the drain insert was installed type: Date, length: 8, domain: none

HasFilterFabric: Field indicating whether or not the pipe has a filter fabric type: String, length: 3, domain: shdBooleanYesNo domain values:['Yes', 'No']

FilterFabricManufacturer: The manufacturer of the filter fabric type: String, length: 255, domain: swStructureManufacturer domain values:['Hydra', 'United', 'Stormtek', 'REM']

FilterFabricDeviceModelType: The model type of the filter fabric device type: String, length: 50, domain: swDeviceModelType domain values:['Pipe Screen', 'Manual Retractable', 'Wing Gate']

FilterFabricInstallDate: The date the filter fabric was installed type: Date, length: 8, domain: none

HasFiltersCatchPan: Field indicating whether or not the pipe has a