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

This archive reproduces a figure titled "Figure 3.2 Boone County population distribution" from Wang and vom Hofe (2007, p.60). The archive provides a Jupyter Notebook that uses Python and can be run in Google Colaboratory. The workflow uses the Census API to retrieve data, reproduce the figure, and ensure reproducibility for anyone accessing this archive.The Python code was developed in Google Colaboratory, or Google Colab for short, which is an Integrated Development Environment (IDE) of JupyterLab and streamlines package installation, code collaboration, and management. The Census API is used to obtain population counts from the 2000 Decennial Census (Summary File 1, 100% data). Shapefiles are downloaded from the TIGER/Line FTP Server. All downloaded data are maintained in the notebook's temporary working directory while in use. The data and shapefiles are stored separately with this archive. The final map is also stored as an HTML file.The notebook features extensive explanations, comments, code snippets, and code output. The notebook can be viewed in a PDF format or downloaded and opened in Google Colab. References to external resources are also provided for the various functional components. The notebook features code that performs the following functions:install/import necessary Python packagesdownload the Census Tract shapefile from the TIGER/Line FTP Serverdownload Census data via CensusAPI manipulate Census tabular data merge Census data with TIGER/Line shapefileapply a coordinate reference systemcalculate land area and population densitymap and export the map to HTMLexport the map to ESRI shapefileexport the table to CSVThe notebook can be modified to perform the same operations for any county in the United States by changing the State and County FIPS code parameters for the TIGER/Line shapefile and Census API downloads. The notebook can be adapted for use in other environments (i.e., Jupyter Notebook) as well as reading and writing files to a local or shared drive, or cloud drive (i.e., Google Drive).

This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) 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 shapefile 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 that begins 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.

The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual- chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The file is georeferenced to earth's surface using the Ohio North Stateplane projection and coordinate system. The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at scales of 1:6000 and 1:12,000.

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)

This data set is a digital soil survey and generally is the most detailed level of soil geographic data developed by the National Cooperative Soil Survey. The information was prepared by digitizing maps, by compiling information onto a planimetric correct base and digitizing, or by revising digitized maps using remotely sensed and other information. This data set consists of georeferenced digital map data and computerized attribute data. The map data are in a 7.5 minute quadrangle format and include a detailed, field verified inventory of soils and nonsoil areas that normally occur in a repeatable pattern on the landscape and that can be cartographically shown at the scale mapped. A special soil features layer (point and line features) is optional. This layer displays the location of features too small to delineate at the mapping scale, but they are large enough and contrasting enough to significantly influence use and management. The soil map units are linked to attributes in the National Soil Information System relational database, which gives the proportionate extent of the component soils and their properties.

This digital geologic map compilation presents new polygon (i.e., geologic map unit contacts), line (i.e., fault, fold axis, and structure contour), and point (i.e., structural attitude, contact elevations) vector data for the Jasper 7 1/2' quadrangle in northern Arkansas. The map database, which is at 1:24,000-scale resolution, provides geologic coverage of an area of current hydrogeologic, tectonic, and stratigraphic interest. The Jasper quadrangle is located in northern Newton and southern Boone Counties about 20 km south of the town of Harrison. The map area is underlain by sedimentary rocks of Ordovician, Mississippian, and Pennsylvanian age that were mildly deformed by a series of normal and strike-slip faults and folds. The area is representative of the stratigraphic and structural setting of the southern Ozark Dome. The Jasper quadrangle map provides new geologic information for better understanding groundwater flow paths in and adjacent to the Buffalo River watershed.

The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual- chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA).The file is georeferenced to earth's surface using the Lambert Conformal Conic projection and the Arkansas State Plane NAD83 South Zone coordinate system. The specifications for the horizontal control of Base Map data files are consistent with those required for mapping at a scale of 1:24,000

Digital orthographic imagery datasets contain georeferenced images of the Earth's surface, collected by a sensor in which object displacement has beeen removed for sensor distortions and orientation, and terrain relief. Digital orthoimages have the geometric characteristics of a map, and image qualities of a photograph. (Source: Circular A-16, p. 16)

no abstract provided

'TASK NAME: 2013 Indiana Statewide Imagery and LiDAR Program The Indiana Statewide Imagery and LiDAR project includes data captured at the following specifications: New 1 = 200 scale 4-band orthoimagery (TIF and ECW formats) at a 1-foot pixel resolution for all Indiana counties New 1 = 100 scale 4-band orthoimagery (TIF and ECW formats) at a 0.5-foot pixel resolution for the following Indiana counties: 2011: Marion, St. Joseph, Elkhart, Kosciusko, Bartholomew, and Harrison 2012: Hamilton, Noble, Dearborn, Madison, Whitley, Shelby, Steuben, Allen, De Kalb and Floyd. 2013: Dubois, Lake, LaPorte , Marion, Porter and Spencer Counties New Statewide LiDAR data at a 1.5-meter average post spacing for all Indiana counties, except: Steuben, Noble, De Kalb, Allen, Madison, Delaware, Hendricks, Marion, Hancock, Morgan, Johnson, Shelby, Monroe, and portions of Vermillion, Parke, Vigo, Clay, Sullivan, Knox, Gibson, and Posey. Optional 1.0-meter Average Post Spacing: 2011-Boone County, 2012-Dearborn and Floyd, 2013 - Lake, LaPorte, Porter, Tippecanoe, Jasper and Newton. The project is divided into three geographic areas: Area 1 2011 - Indiana central counties: St. Joseph, Elkhart, Starke, Marshall, Kosciusko, Pulaski, Fulton, Cass, Miami, Wabash, Carroll, Howard, Clinton, Tipton, Boone, Hendricks, Marion, Morgan, Johnson, Monroe, Brown, Bartholomew, Lawrence, Jackson, Orange, Washington, Crawford, and Harrison. Area 2 2012 - Indiana eastern counties: LaGrange, Steuben, Noble, DeKalb, Whitley, Allen, Huntington, Wells, Adams, Grant, Blackford, Jay, Hamilton, Madison, Delaware, Randolph, Hancock, Henry, Wayne, Shelby, Rush, Fayette, Union, Decatur, Franklin, Jennings, Ripley, Dearborn, Ohio, Scott, Jefferson, Switzerland, Clark, and Floyd. Area 3 2013 - Indiana western counties: Lake, Porter, LaPorte, Newton, Jasper, Benton, White, Warren, Tippecanoe, Fountain, Montgomery, Vermillion, Parke, Putnam, Vigo, Clay, Owen, Sullivan, Greene, Knox, Daviess, Martin, Gibson, Pike, Dubois, Posey, Vanderburgh, Warrick, Spencer, Perry, plus imagery for Marion County was flown as an out-of-cycle buy-up. Area 1 data was acquired in 2011. Area 2 data was acquired in 2012. Area 3 was acquired in 2013. Projection Reference: EPSG2965: NAD83 Indiana East (ftUS) and EPSG2966: NAD83 Indiana West (ftUS). Note: The ground control survey performed to support the Orthophotography and LiDAR data used the NAD 1983 NSRS2007 (ftUS) projection. To facilitate usability by multiple software versions the Orthophotography and LiDAR is only referenced to NAD 83, and the file projection/header information was written to the files using ERDAS IMAGINE.'An orthoimage is remotely sensed image data in which displacement of features in the image caused by terrain relief and sensor orientation have been mathematically removed. Orthoimagery combines the image characteristics of a photograph with the geometric qualities of a map. There is no image overlap between adjacent files. Data received at Earth Resources Observation and Science Center (EROS) were reprojected from: Projection: NAD_1983_StatePlane_Indiana_West_FIPS_1302_Feet Resolution: 1 foot Type: 4 Band to: Standard Product Projection: NAD_1983_UTM_Zone_16N Standard Product Resolution: 0.3000 m Rows: 5000 Columns: 5000 and resampled to align to the U.S. National Grid (USNG) using The National Map. The naming convention is based on the U.S. National Grid (USNG), taking the coordinates of the SW corner of the orthoimage. The metadata were imported and updated for display through The National Map at http://nationalmap.gov/viewer.html Chip-level metadata are provided in HTML and XML format. Data were compressed utilizing IAS software. The compression was JPEG2000 Lossy Compressed. The file format created was .jp2.