Riverside County's GIS web viewer that supplies various datasets containing parcel, transportation, environmental, and boundary layers and more.

The San Bernardino County map viewer is a collection of maps and apps related to various administrative boundaries in San Bernardino County. All data is publicly available. The San Bernardino County map viewer contains the following maps:Parcels: Find and identify parcels by APN or address.Flood Control: Find and identify Flood Control facilities within San Bernardino CountyBoundaries: Explore various administrative boundaries in San Bernardino County, such as Supervisor districts, city limits, US Senate districts and moreHistorical Imagery: Imagery archives for the years 2008 - 2023Power Outages: Power outage data from CalOES showing power outages within San Bernardino County3D Scene: Interactively explore San Bernardino County geographic data in 3D.DIY Map Viewer: Create your own map using a variety of provided datasets, or add your ownThe San Bernardino County Map viewer was created by San Bernardino County's Information Services Department. For more information please contact the Information Services Department (ISD) Help Desk at (909)884-4884.

This map includes change areas for city and county boundaries filed in accordance with Government Code 54900. The initial dataset was first published on October 20, 2021, and was based on the State Board of Equalization's tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax jurisdictions. The boundaries are continuously being revised when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions and should not be used to determine precise city or county boundary line locations.The data is updated within 10 business days of the CDTFA receiving a copy of the Board of Equalization's acknowledgement letter.BOE_CityAnx Data Dictionary: COFILE = county number - assessment roll year - file number (see note*); CHANGE = affected city, unincorporated county, or boundary correction; EFFECTIVE = date the change was effective by resolution or ordinance (see note*); RECEIVED = date the change was received at the BOE; ACKNOWLEDGED = date the BOE accepted the filing for inclusion into the tax rate area system; NOTES = additional clarifying information about the action.*Note: A COFILE number ending in "000" is a boundary correction and the effective date used is the date the map was corrected.BOE_CityCounty Data Dictionary: COUNTY = county name; CITY = city name or unincorporated territory; COPRI = county number followed by the 3-digit city primary number used in the Board of Equalization's 6-digit tax rate area numbering system (for the purpose of this map, unincorporated areas are assigned 000 to indicate that the area is not within a city).

These parcel boundaries represent legal descriptions of property ownership, as recorded in various public documents in the local jurisdiction. The boundaries are intended for cartographic use and spatial analysis only, and not for use as legal descriptions or property surveys. Tax parcel boundaries have not been edge-matched across municipal boundaries.

This map shows recent COVID-19 Trends with arrows that represent each county's recent trend history, and weekly new case counts for U.S. counties. The map data is updated weekly and featured in this storymap.It shows COVID-19 Trend for the most recent Monday with a colored arrow for each county. The larger the arrow, the longer the county has had this trend. An up arrow indicates the number of active cases continue upward. A down arrow indicates the number of active cases is going down. The intent of this map is to give more context than just the current day of new data because daily data for COVID-19 cases is volatile and can be unreliable on the day it is first reported. Weekly summaries in the counts of new cases smooth out this volatility.Click or tap on a county to see a history of trend changes and a weekly graph of new cases going back to February 1, 2020. This map is updated every Tuesday based on data through the previous Sunday. See also this version of the map for additional perspective.COVID-19 Trends show how each county is doing and are updated daily. We base the trend assignment on the number of new cases in the past two weeks and the number of active cases per 100,000 people. To learn the details for how trends are assigned, see the full methodology. There are five trends:Emergent - New cases for the first time or in counties that have had zero new cases for 60 or more days.Spreading - Low to moderate rates of new cases each day. Likely controlled by local policies and individuals taking measures such as wearing masks and curtailing unnecessary activities.Epidemic - Accelerating and uncontrolled rates of new cases.Controlled - Very low rates of new cases.End Stage - One or fewer new cases every 5 days in larger populations and fewer in rural areas.For more information about COVID-19 trends, see the full methodology.Data Source: Johns Hopkins University CSSE US Cases by County dashboard and USAFacts for Utah County level Data.

This web map displays the California Department of Education's (CDE) core set of geographic data layers. This content represents the authoritative source for all statewide public school site locations and school district service areas boundaries for the 2018-19 academic year. The map also includes school and district layers enriched with student demographic and performance information from the California Department of Education's data collections. These data elements add meaningful statistical and descriptive information that can be visualized and analyzed on a map and used to advance education research or inform decision making.

FOR PLAT MAPS AND OTHER LAND DOCUMENTS, PLEASE VISIT THE COUNTY CLERK’S OFFICIAL RECORDS SEARCH: HTTPS://BEXAR.TX.PUBLICSEARCH.US.The Bexar County GIS Team does not have purview over plat maps and other land records. Please visit the Bexar County Clerk’s Official Records Search.

GIS Map view look up parcel information including owner, taxes, market value and more.Important Mailing Label Information:The "Mailing Labels" button is is copy of the Parcels Layer and is intended to be turned OFF on the map, and is there just for the "Public Notification" Widget. This widget obtains information on the pop-up of a selected layer to create "Mailing Labels." This said, this layer contains the Owners Mailing Address information. Below is Arcaded used to customize the pop-up:Made three custom Arcade Lines below: Proper($feature["OWNER_NAM1"]) + Proper($feature["OWNER_NAM2"])Proper($feature["OWNER_ADDR"])Proper($feature["OWNER_CITY"]) + ',' + $feature["OWNER_STAT"] + ',' + $feature["OWNER_ZIP"]Below is the custom pop-up:{expression/expr0}{expression/expr1}{expression/expr2}

Several historic, multi-fault ruptures in the Eastern California Shear Zone (ECSZ) reinforce the need to understand how this rupture style contributes to seismic hazard in complex and diffuse fault zones. Several historic earthquakes in the ECSZ, the 1992 Landers, the 1999 Hector Mine, and the 2019 Ridgecrest rupture sequence, involved complex and multi-fault rupture. However, paleoseismic evidence of multi-fault ruptures in the ECSZ is poorly resolved in the rock record. Here I investigate paleoseismic evidence for complex rupture in Panamint Valley, located ~50 km northeast of the 2019 Ridgecrest ruptures. Late Holocene scarps in the 10 km-wide transtensional relay between the Ash Hill and Panamint Valley faults display surface rupture geometries analogous to those produced during the 1992 Landers and 1999 Hector Mine earthquakes. I produce a 1:4000 scale tectonogeomorphic map of the 40 km² area between the Ash Hill and Panamint Valley faults using my locally-calibrated relative-age alluvial fan chronology and using NCALM lidar DEMs and aerial imagery to identify ruptures. I bracket earthquakes with post-IR feldspar infrared-stimulated luminescence dating of offset deposits. I record vertical and lateral offsets at over 250+ locations using field mapping and backslipped reconstructions of newly generated high resolution (5 cm) drone-based structure from motion digital surface models. My mapping shows that the transtensional relay consists of 100+ fault strands that occur in parallel and en échelon arrays 5-7 km in length, with spacings of 1s to 100s of meters. Using my relative-age fan stratigraphy, geochronologic dating of offset deposits, and relative cumulative offset, I identify four late Holocene ruptures at ~0.3 – ~0.7 ka, ~0.7 – 2.4 ka, ~2.6 – 3.6 ka, and ~3.6 – 4.2 ka. Displacement magnitude per event ranges from 0.6 – 1.0 m of lateral slip and 0 – 0.2 m of dip slip. Displacement-length scaling relationships suggest that these mapped faults cannot rupture independently of a larger fault system. My results show overlap in the timing of ruptures in the transtensional relay, on the Ash Hill and Panamint faults, and that the Ash Hill and transtensional relay are kinematically similar. These similarities suggest this region acts as a zone for complex strain transfer between the Ash Hill and Panamint faults over multiple earthquake cycles. These relationships may support a geometric link at depth or the reoccupation of preexisting weaknesses at depth capable of transferring strain over larger distances.

This map is used to author a map service for the My Government Services application.

This dataset was created by the Transportation Planning and Programming (TPP) Division of the Texas Department of Transportation (TxDOT) for planning and asset inventory purposes, as well as for visualization and general mapping. County boundaries were digitized by TxDOT using USGS quad maps, and converted to line features using the Feature to Line tool. This dataset depicts a generalized coastline.Update Frequency: As NeededSource: Texas General Land OfficeSecurity Level: PublicOwned by TxDOT: FalseRelated LinksData Dictionary PDF [Generated 2025/03/14]

Do not use this data to make zoning determinations. This data does not show all zoning regulations for an address, including overlays and situations where an address has more than one zoning. Also, the data may be out of date. Use the interactive mapping application https://maps.austintexas.gov/GIS/PropertyProfile/ to make zoning determinations, and call 311 if you have questions about zoning. Zoning only applies to addresses within the City of Austin city limits. This dataset is a list of addresses with their zoning provided to answer questions such as "what property addresses have CS zoning." This data is derived from GIS layer for address and zoning. The place_id field is provided for linking to the addresses GIS layer. This product is produced by the City of Austin for informational purposes. No warranty is made they City of Austin regarding specific accuracy or completeness.

Olmsted County city limits, townships, township sections, and county boundary lines. This data references GIS_Publication on GISSQLProd (updated automatically with Olmsted County GIS updates), which was published as a Map Service and Feature Service to ArcGIS Server. Feature Server Layer was added as an "item" in AGOL and shared to the Open Data group, to allow AGOL users to pull these services into their maps. Users can add them to a map by searching for the layer in "My Organization" in the AGOL portal in both ArcGIS Online and ArcGIS Pro. Notes about this service: FeatureServer and MapServer ID for each layer is used by AGOL, and should be maintained in the publishing map in ArcGIS Pro. The map used to publish this service to ArcGIS Server is on the Olmsted County GIS K drive > GIS Development > ArcGIS_Online > AGOL_OpenData > OpenData_Layers.

This map provides information on speed limits that are posted on state-maintained roadways in Virginia. Cities and towns set their own speed limits and these are not available to show on the map. Zoom in on the map to display the speed limits. Speed limits exist for all roads however; where this information is not available for mapping, they are not displayed. Most roads where speed limits are not shown are either rural, secondary roads (routes numbered 600 or greater) where a statutory 55 mph speed limit typically applies, or subdivision streets where a statutory 25 mph speed limit usually applies. These statutory speed limits are often are not posted on these roads. Click on any roadway to display the speed limit information.

Vector polygon map data of city limits from Houston, Texas containing 731 features.

City limits GIS (Geographic Information System) data provides valuable information about the boundaries of a city, which is crucial for various planning and decision-making processes. Urban planners and government officials use this data to understand the extent of their jurisdiction and to make informed decisions regarding zoning, land use, and infrastructure development within the city limits.

By overlaying city limits GIS data with other layers such as population density, land parcels, and environmental features, planners can analyze spatial patterns and identify areas for growth, conservation, or redevelopment. This data also aids in emergency management by defining the areas of responsibility for different emergency services, helping to streamline response efforts during crises..

This city limits data is available for viewing and sharing as a map in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.

Macon-Bibb County School District boundaries for elementary, middle and high schools. Information is maintained by the Macon-Bibb County Planning and Zoning Department. For more information about the Macon-Bibb County District visit https://www.bcsdk12.net.

This pipe feature class represents current wastewater information of the mainline sewer in the City of Los Angeles. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most rigorous geographic information of the storm drain system using a geometric network model, to ensure that its storm drains reflect current ground conditions. The conduits and inlets represent the storm drain infrastructure in the City of Los Angeles. Storm drain information is available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works.Associated information about the wastewater Pipe is entered into attributes. Principal attributes include:PIPE_SUBTYPE: pipe subtype is the principal field that describes various types of lines as either Airline, Force Main, Gravity, Siphon, or Special Lateral.For a complete list of attribute values, please refer to (TBA Wastewater data dictionary). Wastewater pipe lines layer was created in geographical information systems (GIS) software to display the location of sewer pipes. The pipe lines layer is a feature class in the LACityWastewaterData.gdb Geodatabase dataset. The layer consists of spatial data as a line feature class and attribute data for the features. The lines are entered manually based on wastewater sewer maps and BOE standard plans, and information about the lines is entered into attributes. The pipe lines are the main sewers constructed within the public right-of-way in the City of Los Angeles. The ends of line segments, of the pipe lines data, are coincident with the wastewater connectivity nodes, cleanout nodes, non-structures, and physical structures points data. Refer to those layers for more information. The wastewater pipe lines are inherited from a sewer spatial database originally created by the City's Wastewater program. The database was known as SIMMS, Sewer Inventory and Maintenance Management System. For the historical information of the wastewater pipe lines layer, refer to the metadata nested under the sections Data Quality Information, Lineage, Process Step section. Pipe information should only be added to the Wastewater Pipes layer if documentation exists, such as a wastewater map approved by the City Engineer. Sewers plans and specifications proposed under private development are reviewed and approved by Bureau of Engineering. The Department of Public Works, Bureau of Engineering's, Brown Book (current as of 2010) outlines standard specifications for public works construction. For more information on sewer materials and structures, look at the Bureau of Engineering Manual, Part F, Sewer Design, F 400 Sewer Materials and Structures section, and a copy can be viewed at http://eng.lacity.org/techdocs/sewer-ma/f400.pdf.List of Fields:STREET: This is the street name and street suffix on which the pipe is located.PIPE_LABEL: This attribute identifies the arc segment between two nodes, which represents the pipe segment. There could be any number of pipes between the same two maintenance holes and at least one. If there is more than one pipe between the same two maintenance holes, then a value other than 'A' is assigned to each pipe, such as the value 'B', 'C', and so on consecutively. Also, when a new pipe is constructed, some old pipes are not removed from the ground and the new pipe is added around the existing pipe. In this case, if the original pipe was assigned an 'A', the new pipe is assigned a 'B'.C_UP_INV: This is the calculated pipe upstream invert elevation value.PIPE_MAT: The value signifies the various materials that define LA City's sewer system. Values: • TCP - Terra Cotta pipe. • CMP - Corrugated metal pipe. • RCP - Reinforced concrete pipe. Used for sewers larger than 42inch, with exceptions. • PCT - Polymer concrete pipe. • CON - Concrete or cement. • DIP - Ductile iron pipe. • ABS - Acrylonitrile butadiene styrene. • STL - Steel. • UNK - Unknown. • ACP - Asbestos cement pipe. • RCL - Reinforced concrete pipe lined. • OTH - Other or unknown. • VCP - Vitrified clay pipe. • TRS - Truss pipe. • CIP - Cast iron pipe. • PVC - Polyvinyl chloride. • BRK - Brick. • RCPL - Lined Reinforced concrete pipe. Used for sewers larger than 42inch, with exceptions. • B/C - Concrete brick pipe. • FRP - Centrifugally cast fiberglass reinforced plastic mortar pipe.DN_INV: This is the downstream invert elevation value.PIPE_WIDTH: This value is the pipe dimension for shapes other than round.C_SLOPE: This is the calculated slope.ENABLED: Internal feature number.DN_STRUCT: This attribute identifies a number at one of two end points of the line segment that represents a sewer pipe. A sewer pipe line has a value for the UP_STRUCT and DN_STRUCT fields. This point is the downstream structure that may be a maintenance hole, pump station, junction, etc. Each of these structures is assigned an identifying number that corresponds to a Sewer Wye data record. The 8 digit value is based on an S-Map index map using a standardized numbering scheme. The S-Map is divided into 16 grids, each numbered sequentially from west to east and north to south. The first three digits represent the S-Map number, the following two digits represent the grid number, and the last three digits represent the structure number within the grid. This field also relates to the (name of table or layer) node attribute table.PIPE_SIZE: This value is the inside pipe diameter in inches.MON_INST: This is the month of the pipe installation.PIPE_ID: The value is a combination of the values in the UP_STRUCT, DN_STRUCT, and PIPE_LABEL fields. This is the 17 digit identifier of each pipe segment and is a key attribute of the pipe line data layer. This field named PIPE_ID relates to the field in the Annotation Pipe feature class and to the field in the Wye line feature class data layers.REMARKS: This attribute contains additional comments regarding the pipe line segment.DN_STA_PLS: This is the tens value of the downstream stationing.EASEMENT: This value denotes whether or not the pipe is within an easement.DN_STA_100: This is the hundreds value of the downstream stationing.PIPE_SHAPE: The value signifies the shape of the pipe cross section. Values: • SE - Semi-Elliptical. • O1 - Semi-Elliptical. • UNK - Unknown. • BM - Burns and McDonald. • S2 - Semi-Elliptical. • EL - Elliptical. • O2 - Semi-Elliptical. • CIR - Circular. • Box - Box (Rectangular).PIPE_STATUS: This attribute contains the pipe status. Values: • U - Unknown. • P - Proposed. • T - Abandoned. • F - As Built. • S - Siphon. • L - Lateral. • A - As Bid. • N - Non-City. • R - Airline.ENG_DIST: LA City Engineering District. The boundaries are displayed in the Engineering Districts index map. Values: • O - Out LA. • V - Valley Engineering District. • W - West LA Engineering District. • H - Harbor Engineering District. • C - Central Engineering District.C_PIPE_LEN: This is the calculated pipe length.OWNER: This value is the agency or municipality that constructed the pipe. Values: • PVT - Private. • CTY - City of LA. • FED - Federal Facilities. • COSA - LA County Sanitation. • OUTLA - Adjoining cities.CRTN_DT: Creation date of the line feature.TRTMNT_LOC: This value is the treatment plant used to treat the pipe wastewater.PCT_ENTRY2: This is the flag determining if the second slope value, in SLOPE2 field, was entered in percent as opposed to a decimal. Values: • Y - The value is expressed as a percent. • N - The value is not expressed as a percent.UP_STA_100: This is the hundreds value of the upstream stationing.DN_MH: The value is the ID of the structure. This point is the structure that may be a maintenance hole, pump station, junction, etc. The field name DN_MH signifies the structure is the point at the downstream end of the pipe line segment. The field DN_MH is a key attribute to relate the pipe lines feature class to the STRUCTURE_ID field in the physical structures feature class.SAN_PIPE_IDUSER_ID: The name of the user carrying out the edits of the pipe data.WYE_MAT: This is the pipe material as shown on the wye card.WYE_DIAM: This is the pipe diameter as shown on the wye card.SLOPE2: This is the second slope value used for pipe segments with a vertical curve.EST_YR_LEV: This value is the year installed level.EST_MATL: This is the flag determining if the pipe material was estimated.LINER_DATE: This value is the year that the pipe was re-lined.LAST_UPDATE: Date of last update of the line feature.SHAPE: Feature geometry.EST_YEAR: This is the flag indicating if the year if installation was estimated.EST_UPINV: This is the flag determining if the pipe upstream elevation value was estimated.WYE_UPDATE: This value indicates whether the wye card was updated.PCT_ENTRY: This is the flag determining if the slope was entered in percent as opposed to a decimal. Values: • N - The value is not expressed as a percent. • Y - The value is expressed as a percent.PROF: This is the profile drawing number.PLAN1: This is the improvement plan drawing number.PLAN2: This is the supplementary improvement plan drawing number.EST_DNINV: This is the flag determining if the pipe downstream elevation value was estimated.UP_STRUCT: This attribute identifies a number at one of two end points of the line segment that represents a sewer pipe. A sewer pipe line has a value for the UP_STRUCT and DN_STRUCT fields. This point is the upstream structure that may be a maintenance hole, pump station, junction, etc. Each of these structures is assigned an identifying number that corresponds to a Sewer Wye data record. The 8 digit value is based on an S-Map index map

Map built for use during the virtual water week event. Address search can be used to determine what watershed is in that area.

This web map is used as a basemap and a reference map for the What's My Watershed Web Application and Healthy Waterways Story Map. The NJDEP authoritative data layers are directly accessed through AGO resources.

View layer for the rest end point Park Roads for the "Who Plows My Roads?" Map.