Geospatial data about Grant County, Wisconsin Parcel Zoning. Export to CAD, GIS, PDF, CSV and access via API.

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.

The feature layers presented within this web app are for visualization of the geographic and administrative features pertinent to Grant County, WA. Contact gcgis@grantcountywa.gov with comments or questions on this app.

Geospatial data about Grant County, Washington Parcels. Export to CAD, GIS, PDF, CSV and access via API.

Geospatial data about Grant County, Arkansas Parcels. Export to CAD, GIS, PDF, CSV and access via API.

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.

Geospatial data about Grant County, Wisconsin Parcels. Export to CAD, GIS, PDF, CSV and access via API.

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.

WDFW’s “Shrubsteppe and Eastside Steppe General Locations” datasets shows the general location of shrubsteppe and eastside steppe as defined by WDFW’s Priority Habitats and Species program. The map shows where WDFW recommends counties and cities require site-scale information be gathered to inform site-scale land use decisions. It is the best available information regarding the general location of shrubsteppe and Eastside steppe in Washington – and it has important limitations. It is appropriate to use this map for its primary purpose: to identify where site-specific data should be gathered to inform site-scale decisions. It is also appropriate to expect that on-the-ground conditions will vary from this general information. The map relies upon several GIS layers that are maintained by other agencies and updated at various intervals. This map is updated episodically when input layers are updated with the most current information. WDFW data experts, in consultation with subject matter experts and Habitat Program’s Chief Scientist, may without prior notice, update the map (e.g., input data, methodology) to reflect the best available information, best available science, and evolving values and policies. While this is the best available information with respect to the location of shrubsteppe and Eastside steppe in Washington, it has important limitations that users should understand. Challenges of Scale: The fundamental building block of this map is USGS’ 2016 Landfire Remap Existing Vegetation Type (click here for more information). The great benefit of this data is that it provides comprehensive, wall-to-wall coverage of the state. The primary drawbacks of this layer are that it (a) is comprised of 30-meter square pixels (0.22 acres) and (b) is designed to be used when zoomed out to a regional scale. USGS recommends users zoom in no closer than a scale of 1:5,000 (at this scale, a map on a piece of 8½ by 11-inch piece of paper with 1” margins covers 230 acres). A map at this scale is of little use for many important land use decisions (e.g., regarding development, restoration) which occur on a parcel scale – around 1 acre plus or minus. WDFW created this map and explanation of its proper use to inform parcel-scale land use decisions made by local governments and other conservation partners in a way that takes advantage of the benefits of the regional data while working within its limitations. USGS’ Use Limitations: USGS has a carefully worded statement on use limitations for this data. The statement in full reads: Although LANDFIRE products are delivered as 30-meter pixels, they should not be used at the individual pixel level or on small groups of pixels. LANDFIRE products were designed to support 1) national (all states) strategic planning, 2) regional (single large states or groups of smaller states), and 3) strategic/tactical planning for large sub-regional landscapes and Fire Management Units (FMUs) (such as significant portions of states or multiple federal administrative entities). The applicability of LANDFIRE products to support fire and land management planning on smaller areas will vary by product, location, and specific use. Further investigation by local and regional experts should be conducted to inform decisions regarding local applicability. However, it is the responsibility of the local user, using LANDFIRE metadata and local knowledge, to determine if and/or how LANDFIRE can be used for particular areas of interest. LANDFIRE products are not intended to replace local products, but rather serve as a back-up by providing wall-to-wall cross-boundary products. It is the responsibility of the user to be familiar with the value, assumptions, and limitations of LANDFIRE products. Managers and planners must evaluate LANDFIRE data according to the scale and requirements specific to their needs.(emphasis added) Mindful of these limitations, WDFW experts have investigated the Landfire data and determined that applying it at a parcel-scale to inform decisions described herein is a proper use of the data. Appropriate Uses:While it is appropriate to use this data as described below, it is also important for users to realize that it is appropriate to expect that on-the-ground conditions will vary from this general information. This is because this data reflects many sources that depict ecological systems, roads, agricultural lands, buildings, waterbodies, railroads, and airports. Users should consider that (a) each source has its own date when the data was gathered, (b) each source has a scale at which it was gathered and for which it is intended to be used, (c) the differing projections of these data sources can cause features to be offset from the location shown, and (d) each source has known errors of omission and commission (meaning that the GIS layer may miss on-the-ground features or may show features that do not actually exist on the ground). These variances do not invalidate the data to be used as described below. It is appropriate to use this data to identify where site-specific data should be gathered to inform site-scale decisions. (WDFW strongly recommends that site-scale land use decisions be informed by site-scale data.) a) The land use decision under consideration drives the precise type of site-specific information to be gathered (e.g., shrubsteppe presence/absence, boundary, quality), methods used to gather it, and qualifications of the person gathering it. b) Where this regional data shows higher variability (i.e., smaller patches or more pixelated appearance), a rapid shrubsteppe assessment (rather than a more extensive assessment) may be appropriate to confirm or refute the presence of shrubsteppe. It is appropriate to presume that places indicated as shrubsteppe are shrubsteppe and that places that are not indicated as shrubsteppe are not shrubsteppe. a) This presumption is stronger where the layer shows a high degree of uniformity of shrubsteppe (or non-shrubsteppe); it is weaker where there is less uniformity. b) For a specific site, this presumption should yield to the professional opinion of a qualified person with first-hand knowledge and/or reliable site-specific data of the site. It is appropriate to use this information to broadly estimate aspects of shrubsteppe (a) spatial attributes such as patch size and interior vs. edge, (b) connectivity (e.g., with other shrubsteppe, cliffs, dunes, etc.), and (c) restoration potential (to the extent that restoration potential is related to proximity to large or more uniform patches of shrubsteppe). Such estimates, when derived by qualified persons using reasonable methods, should be presumed to be valid. Inappropriate uses: To clarify appropriate uses, we identify some inappropriate uses of the “Shrubsteppe and Eastside Steppe General Locations” map. These examples are not exhaustive. It is inappropriate to assume that the pixelated edges represent the actual edge of shrubsteppe (a site-scale boundary evaluation is needed for this purpose). Where there is variation in pixels (i.e., smaller patches or more pixelated appearance), it is inappropriate to assume that the individual or small groups of pixels of shrubsteppe or non-shrubsteppe represent the precise location of shrubsteppe and non-shrubsteppe areas (a site-scale evaluation of the existence/extent of shrubsteppe is needed for this purpose). It is inappropriate to consider this modeled information to be accurate when appropriately gathered, site-scale data, or the professional judgment of an informed, qualified person says otherwise.

FEMA Framework Basemap datasets comprise six of the seven FGDC themes of geospatial data that are used by most GIS applications (Note: the seventh framework theme, orthographic imagery, is packaged in a separate NFIP Metadata Profile): cadastral, geodetic control, governmental unit, transportation, general structures, hydrography (water areas & lines. These data include an encoding of the geographic extent of the features and a minimal number of attributes needed to identify and describe the features. (Source: Circular A16, p. 13)

Content from authoritative sources such as City of Moses Lake, City of Quincy, USFWS, Washington Department of Natural Resources, Department of Health, Department of Fish and Wildlife, USGS, etc.The maps sites referenced in this app are considered potentially useful for geospatial queries or visualization of Grant County, WA.

Geospatial data about Grant County, Wisconsin Municipal Boundaries. Export to CAD, GIS, PDF, CSV and access via API.

The Comprehensive Plan’s purpose and intent is to provide for local needs relating to the use of land and infrastructure, including the protection of property and water rights, and in so doing, to meet the State’s minimum planning law requirements. Comprehensive planning for Grant County will help ensure that the following goals will be accomplished:Tax dollars invested in public roads, water and sewer systems, fire stations, parks and other public services are spent wisely.Funding for development and capital improvement projects is secured. Long-range considerations are incorporated into decisions on short-range actions.Public interests, and the interest of the community at large, are promoted rather than the interests of individuals or special groups within the communities.Interests of property owners are protected.The analyses of existing conditions, issues, facilities, population projections, and other factors within the Comprehensive Plan will aid Grant County officials and the County Commissioners in their decision-making role. It seeks to establish a clear intent and policy base that can be used to develop and interpret municipal regulations. The Comprehensive Plan is also intended to maintain reasonable continuity in future decision-making as turnover occurs within the County's legislative body. However, the plan must be periodically reviewed and updated to reflect technological, social, economic, and political changes that may invalidate certain plans and policies.The Comprehensive Plan provides a legally recognized framework for making decisions about land use and other planning and policy priorities; however, it is fundamentally a policy document providing direction for how land use goals, policies, and regulations should be applied for the next 10 to 20 years in Grant County. The policies are required by the GMA to be implemented through the use of such regulatory tools as zoning and subdivision ordinances, as well as other innovative techniques. These regulations must be developed and maintained in accordance with the goals and policies of this Comprehensive Plan.Last update

1/17/2020. Comprehensive Plan amendments of 2019:Parcel 201542000 converted from Commercial (Urban) to Residential, SuburbanParcel 201358008 converted from Rural Residential 1 to Agriculture IrrigatedParcel 160788000 converted from Rural Residential 1 to Residential, Low DensityParcel 151107000 converted from Rural Residential 1 to Agriculture IrrigatedParcel 170983000 converted from Rural Remote to Industrial (Urban)Parcel 313169000 converted from Urban Reserve (Rural) to Commercial (Urban)Parcel 211912000 converted from Agriculture Irrigated to Rural Residential 13/25/2019.1/17/2019.8/1/2018. Minor designation errors were corrected.7/2/2018. An updated Comprehensive Land Use Plan was adopted.

Grant County Fire Districts. Some city limits are excluded from this feature class, as cities have urban fire districts. Fire district are Washington State areas established to eliminate fire hazards and protect life and property outside of incorporated cities and towns except where such cities and towns have been annexed into the district. Fire district is a variable in the computation of property tax.

Data from USBR and Quincy Columbia Basin Irrigation District. There are periodic changes to the farm units and irrigation districts.

Geospatial data about Grant County, Washington Zoning Boundaries. Export to CAD, GIS, PDF, CSV and access via API.

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. Edge refers to the linear topological primitives that make up MTDB. The All Lines Shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines Shapefile are available in relationship (.dbf) files that users must download separately. The All Lines Shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.

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.

Geospatial data about Grant County, Arkansas Mile Markers. Export to CAD, GIS, PDF, CSV and access via API.

See Grant County, Washington – Code of Ordinances, Title 9 Animals. Chapter 9.04 establishes that all of Grant County is a stock restricted area, except for the designated Open Range areas. Open Range areas are described in 9.04.030 (1973).Areas of the 1973 designated Open Range areas that are incorporated into city limits since 1973 are assumed to be excluded from the Open Range polygons for cartographic purposes.