Title 23 of the Grant County Code is comprised of Chapters 23.04 – Zoning Districts, 23.08 – Performance and Use-specific Standards, and 23.12 – Development Standards, and official zoning maps, and shall be known as the zoning code of Grant County, Washington.The zoning code is intended to carry out the goals and policies of the Grant County Comprehensive Plan, and to benefit the public as a whole and not any specific person or class of persons. The zoning code classifies, designates, and regulates the development of land for agriculture, mineral resource extraction, residential, commercial, industrial, recreation, tourism and public land uses for the unincorporated area of Grant County.Last update1/17/2020 – Comprehensive plan amendments of 2019:Parcel 201542000 converted from Urban Commercial 2 to Urban Residential 1Parcel 201358008 converted from Rural Residential 1 to AgriculturalParcel 160788000 converted from Rural Residential 1 to Urban Residential 2Parcel 151107000 converted from Rural Residential 1 to AgriculturalParcel 170983000 converted from Rural Remote to Urban Heavy IndustrialParcel 313169000 converted from Rural Urban Reserve to Urban Commercial 2Parcel 211912000 converted from Agricultural to Rural Residential 15/17/2019 – the boundary between AG and RC was corrected to follow the north parcel line of 201370001. The parcel boundary of 201370001 had changed in 2007 but the zoning wasn’t adjusted at that time.3/25/2019 – small areas within the Desert Aire open space area were corrected because they were inadvertently missed during the 7/2/2018 update.1/17/2019 - a small portion of Desert Aire zoning was changed from RVOC to RVC.8/1/2018 – minor designation errors were corrected.7/2/2018 – a new Comprehensive Plan was adopted.

This imagery service is for viewing only, no downloading of the raster images available.

This application can be used to help determine if an applicant's project meets the low/moderate income threshold for eligibility to be funded under the Lake County Illinois Community Development Block Grant program.

The TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB tha begin with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways.

This layer originated from ZCTAs and has been modified in places by Grant County GIS staff based on input from local US Postal Service staff and landowners.ZIP Code Tabulation Areas (ZCTAs™) are a statistical geographic entity produced by the U.S. Census Bureau for tabulating summary statistics from the 2010 Census, first developed for Census 2000. This entity was developed to overcome the difficulties in precisely defining the land area covered by each ZIP Code™, which is necessary in order to accurately tabulate census data for that area.ZCTAs are generalized area representations of U.S. Postal Service (USPS) ZIP Code service areas. They represent the most frequently occurring five-digit ZIP Code found in a given area. Simply put, each ZCTA is built by aggregating 2010 Census blocks, whose addresses use a given ZIP Code. Each resulting ZCTA is then assigned the most frequently occurring ZIP Code as its ZCTA code. For more information, please refer to the ZCTA Frequently Asked Questions (FAQ).

This layer is filtered to show qualifying sales by the year the sale occurred. A qualifying sale is defined as original sale price greater than $0, and the state qualification code includes the values of 00-Qualifying Sale, 01-Family Sale, 02-Transfer within Corporation, 03-Administrator of Estate, 07-Tax Exempt Property, 15-Forced Sale, 21-Plottage, 24-Current Use (84.34), 25-Change of Use, 26-Current Year Segregation.

This map provides the location of the original land grants within present day Loudoun County from the early 1700s to early 1800s. To view a list of sortable attributes of the information, please click on the Table button in the upper right corner of the map. For additional details, please visit here.

These are the original grantings of land within the Northern Neck Proprietary by Thomas, the 6th Lord of Fairfax and/or his agents until the mid 1780s during the settlement of Virginia. The map shows the approximate location of the original land grant as well as information on the grantee, the acreage of the grant (as calculated using the GIS), the year, and additional comments. The map is intended for historical reference only, as insufficient and incomplete original boundary surveys have resulted in potential inaccurate boundaries.

The original research for all of the land grants mapped in this application was completed by historian Wynne Saffer. They were originally mapped on USGS Quadrangles at a scale of 1:24000, then scanned to a digital file and the boundaries digitized by the Loudoun County Office of Mapping and Geographic Information staff.

The orginial land grant research is located at Thomas Balch Library. The land grants can be viewed on microfilm using the Record Number as a reference. This map is also located on the Office of Mapping and Geographic Information online map gallery, which can be found here.

For more information about Loudoun County's GIS, please contact Office of Mapping and Geographic Information.

The TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Linear Water Features includes single-line drainage water features and artificial path features that run through double-line drainage features such as rivers and streams, and serve as a linear representation of these features. The artificial path features may correspond to those in the USGS National Hydrographic Dataset (NHD). However, in many cases the features do not match NHD equivalent feature and will not carry the NHD metadata codes. These features have a MAF/TIGER Feature Classification Code (MTFCC) beginning with an "H" to indicate the super class of Hydrographic Features.

Cemetery districts are established to establish and operate cemeteries. Cemetery district is a variable in the computation of property tax.

Grant Township Tax Code

Road segments representing centerlines of all roadways or carriageways in a local government. Typically, this information is compiled from orthoimagery or other aerial photography sources. This representation of the road centerlines support address geocoding and mapping. It also serves as a source for public works and other agencies that are responsible for the active management of the road network.

sde_gis.GISUSER.CONSOLIDATED_PRECINCTS_2007_11_GRANT_sqlvw

Parcels - this layer shows the outer boundary of the land parcel. Be aware that the polygons representing land parcels are based on survey data, but do not always exactly represent the survey data. This data is only a representation of the location and size of land parcels. You are invited to submit corrections to the Data Steward. Polygons are edited continuously as land is subdivided and segregated. Updates are usually posted bi-monthly.OwnerListing - this table lists the owner names associated with each parcel. There can be multiple owners per parcel, and ownership changes over time.

Grant Township JAWA

This dataset is a compilation of road centerline data from Minnesota suppliers that have opted-in for their road centerline data to be included in this dataset.

It includes the following 45 suppliers that have opted-in to share their data openly as of the publication date of this dataset: Metropolitan Emergency Services Board (10 counties), Aitkin County, Becker County, Benton County, Cass County, Chippewa County, Clay County, Cook County, Crow Wing County, Douglas County, Fillmore County, Grant County, Houston County, Itasca County, Koochiching County, Lac qui Parle County, Lake County, Le Sueur County, Lyon County, Marshall County, McLeod County, Morrison County, Mower County, Murray County, Otter Tail County, Pipestone County, Polk County, Pope County, Renville County, Rock County, Saint Louis County, Stearns County, Stevens County, Waseca County, Winona County, Wright County, and Yellow Medicine County.

The two sources of road centerline data are the Minnesota Next Generation 9-1-1 (NG9-1-1) Program, in collaboration with local data suppliers, and the MetroGIS Road Centerlines (Geospatial Advisory Council Schema) which is on the Minnesota Geospatial Commons:

The Minnesota NG9-1-1 Program enterprise database provides the data outside of the Metro Region which is provide by the suppliers. The data have been aggregated into a single dataset which implements the MN NG9-1-1 GIS Data Model (https://ng911gis-minnesota.hub.arcgis.com/documents/79beb1f9bde84e84a0fa9b74950f7589/about ).

Only data which have meet the requirements for supporting NG9-1-1 are in the statewide aggregate GIS data. MnGeo extracts the available data, applies domain translations, and transforms it to UTM Zone 15 to comply with the GAC road centerline attribute schema: https://www.mngeo.state.mn.us/committee/standards/roadcenterline/index.html.

The MetroGIS Road Centerlines data was created by a joint collaborative project involving the technical and managerial GIS staff from the the Metropolitan Counties (Anoka, Carver, Chisago, Dakota, Hennepin, Isanti, Ramsey, Scott, Sherburne, and Washington), the Metropolitan Emergency Services Board, MetroGIS and the Metropolitan Council. The data are pulled from the Minnesota Geospatial Commons: https://gisdata.mn.gov/dataset/us-mn-state-metrogis-trans-road-centerlines-gac

‘Supplier’ is a term used throughout this document. A supplier will typically be a county, but it could also be a public safety answering point (PSAP), region, or tribal nation. The supplier is the agency which provides the individual datasets for the aggregated dataset. The trans_road_centerlines_open_metadata feature layer will contain the geometry/shape of the supplier boundaries, supplier name, supplier type, and feature count.

Aggregation Process:
1. Extract NG9-1-1 data from the Department of Public Safety (DPS) Enterprise database.
2. Download the latest MetroGIS data from the Geospatial Commons.
3. Extract, Translate, and Load (ETL) the DPS data to the GAC schema.
4. Combine NG9-1-1 data with MetroGIS data.
5. Filter the data for the Opt-In Open data counties

Grant Township High School

Index of the 10 km page extents of the Atlas of Grant County, WA. Click on the page of interest; in the popup, click on the more details hyperlink. The hyperlink is for the static .pdf atlas page, which shows road centerlines, address ranges, aerial photo background, points of interest, culverts, bridges, etc. The atlas is organized using the US National Grid reference system, at 10km squares.Index for Township Range Atlas of Grant County, WA. Shows road centerlines, address ranges, aerial photo background, points of interest, culverts, bridges, etc.

Applications of Lidar Data The State of Indiana has a variety of requirements for high quality elevation data. QL2 Lidar is utilized for mission critical activities at all levels of government, academia and private organizations and provides significant cost savings related to utilizing Lidar as a resource. Some of the major use cases identified include: Floodplain Mapping, Modeling and ManagementSurface and Ground Water Quality Assessments and ManagementEnvironmental and Disaster InformaticsSurveying, Engineering, Transportation and Construction projectsHomeland Security and Disaster ResponseGeologic MappingRenewable EnergyCoastal Zone and Maritime Management, Navigation and SafetyAviation Navigation and SafetyMilitary applications Acquisition of 3DEP QL2 Lidar in Indiana 3DEP acquisition of QL2 Lidar for the State of Indiana began in spring of 2016 and was completed in the spring of 2020, with the final data delivered in December 2020. This acquisition was accomplished through the following USGS 3DEP BAA initiatives: In 2015 the Indiana Geographic Information Council (IGIC) submitted a 3DEP BAA proposal to the USGS in partnership with 3 Indiana Counties (Marion, Hamilton and Wayne) to support the acquisition of new Quality Level 2 Lidar data products. This grant was awarded in 2016 and this project was completed in 2019. In 2016 the Indiana Geographic Information Council (IGIC) submitted a 3DEP BAA proposal to the USGS in partnership with the Indiana office of the USDA – Natural Resource Conservation Service (NRCS) to acquire new Quality Level 2 Lidar data products for 12 Indiana Counties in northeast Indiana. This proposal was selected by the USGS, but before this agreement was finalized the Indiana NRCS office was able to allocate additional funds (totaling $6.625 million), and along with additional 3DEP Federal Funds from the USGS, the original BAA proposal was expanded to collect new 3DEP Lidar data products for all remaining 89 counties in Indiana. This USGS grant was awarded to NRCS in 2017 and this project was completed in December 2020. Indiana 3DEP Lidar Base Products Include Lidar Tiles – individual tiles in LAS 1.4 Format (QL2 Lidar data consists of 2 laser pulses per meter spacing)DEM Tiles – individual tiles in IMG Format (Bare-Earth Hydro-Flattened Digital Elevation Model)Breaklines – GIS hydrography features (rivers and lake polygons) used to create Bare-Earth Hydro-Flattened DEMIntensity Data Tiles – individual tiles in TIF Format (2.5-foot pixel intensity image generated from the First Return Lidar Pulse recording of surface reflectance)DEM Mosaic – Merged countywide DEM mosaic file in IMG Format generated from #2 aboveCounty Delivery Tile Grid – GIS Shapefile showing all delivery tiles and their file namesFGDC Metadata This new Lidar data is providing valuable and exciting new elevation products for Indiana that are twice as detailed and twice as accurate as Indiana’s previous 2011 – 2013 statewide Lidar. With this accomplished, Indiana’s statewide GIS elevation data efforts are now focused on enhanced distribution of this new data, the development of derivative products, and the collection of new bathymetry Lidar data for inland river and stream channels. Read below to learn more about Lidar and for more information on the status of Indiana’s 3DEP Lidar initiatives. Mapping Indiana’s 3DEP Lidar Collection Dates Indiana’s Statewide 3DEP QL2 Lidar was collected in the spring over a five-year period (2016 – 2020) on a total of sixty-eight (68) different days. End-users of Indiana’s Lidar data can read the FGDC metadata published for the Lidar data set you are using [here] to see the general collection date information, but reporting the detailed Lidar date information stored in the Lidar point cloud files* provides important more detailed date information. Also, by publishing a detailed map showing these statewide Lidar collection dates, this important information shares and conveys more easily. * The method used was adapted from the original work - Mapping Lidar Collection Dates from LAS/LAZ Points (wordpress.com) published on February 3, 2014 by Kirk Waters, physical scientist at the NOAA Office for Coastal Management. For Indiana we used a point thinning method to select and reformat the GPSTime information from each Lidar file and then map the results. Indiana Example: Returning a thinned sampling on Lidar Ground Points per Lidar file The GPSTime results for each file were combined, summarized and then mapped to show Lidar dates by collection year (for all 92 Indiana counties – see map above), and also by specific file collection dates (for all 41,648 individual files - see example below). An interactive Esri ArcGIS Online Story Map / App was then published to share this detailed date information [here] with all end-users.

The lands actually receiving water from the Columbia Basin Project can be determined from the feature class called Farm Units. Additional areas of water use may be found in the Water Service Contracts and Municipal and Industrial Contracts of each irrigation district.Data received from the Ephrata, WA office of USBR and updated by data received from Quincy Irrigation District.

Grant Township Special Service Areas