U.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
USGS is assessing the feasibility of map projections and grid systems for lunar surface operations. We propose developing a new Lunar Transverse Mercator (LTM), the Lunar Polar Stereographic (LPS), and the Lunar Grid Reference Systems (LGRS). We have also designed additional grids designed to NASA requirements for astronaut navigation, referred to as LGRS in Artemis Condensed Coordinates (ACC), but this is not released here. LTM, LPS, and LGRS are similar in design and use to the Universal Transverse Mercator (UTM), Universal Polar Stereographic (LPS), and Military Grid Reference System (MGRS), but adhere to NASA requirements. LGRS ACC format is similar in design and structure to historic Army Mapping Service Apollo orthotopophoto charts for navigation. The Lunar Transverse Mercator (LTM) projection system is a globalized set of lunar map projections that divides the Moon into zones to provide a uniform coordinate system for accurate spatial representation. It uses a transverse Me ...
https://en.wikipedia.org/wiki/Public_domainhttps://en.wikipedia.org/wiki/Public_domain
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 primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri, Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The boundaries for counties and equivalent entities are as of January 1, 2017, primarily as reported through the Census Bureau's Boundary and Annexation Survey (BAS).
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
The Residential Schools Locations Dataset in shapefile format contains the locations (latitude and longitude) of Residential Schools and student hostels operated by the federal government in Canada. All the residential schools and hostels that are listed in the Indian Residential School Settlement Agreement are included in this data set, as well as several Industrial schools and residential schools that were not part of the IRRSA. This version of the dataset doesn’t include the five schools under the Newfoundland and Labrador Residential Schools Settlement Agreement. The original school location data was created by the Truth and Reconciliation Commission, and was provided to the researcher (Rosa Orlandini) by the National Centre for Truth and Reconciliation in April 2017. The data set was created by Rosa Orlandini, and builds upon and enhances the previous work of the Truth and Reconcilation Commission, Morgan Hite (creator of the Atlas of Indian Residential Schools in Canada that was produced for the Tk'emlups First Nation and Justice for Day Scholar's Initiative, and Stephanie Pyne (project lead for the Residential Schools Interactive Map). Each individual school location in this dataset is attributed either to RSIM, Morgan Hite, NCTR or Rosa Orlandini. Many schools/hostels had several locations throughout the history of the institution. If the school/hostel moved from its’ original location to another property, then the school is considered to have two unique locations in this data set,the original location and the new location. For example, Lejac Indian Residential School had two locations while it was operating, Stuart Lake and Fraser Lake. If a new school building was constructed on the same property as the original school building, it isn't considered to be a new location, as is the case of Girouard Indian Residential School. When the precise location is known, the coordinates of the main building are provided, and when the precise location of the building isn’t known, an approximate location is provided. For each residential school institution location, the following information is provided: official names, alternative name, dates of operation, religious affiliation, latitude and longitude coordinates, community location, Indigenous community name, contributor (of the location coordinates), school/institution photo (when available), location point precision, type of school (hostel or residential school) and list of references used to determine the location of the main buildings or sites. The geographic coordinate system for this dataset is WGS 1984. The data in shapefile format [IRS_locations.zip] can be viewed and mapped in a Geographic Information System software. Detailed metadata in xml format is available as part of the data in shapefile format. In addition, the field name descriptions (IRS_locfields.csv) and the detailed locations descriptions (IRS_locdescription.csv) should be used alongside the data in shapefile format.
This shapefile contains center-beam depths for approximately 5804 trackline kilometers of Simrad EM122 multibeam-bathymetry data collected in the Gulf of Alaska during U.S. Geological Survey (USGS) cruise MGL1109 aboard the R/V Marcus G. Langseth. The depth values were extracted from gridded data which were reduced for position, elevation, orientation, water-column sound-speed, and refraction effects.
https://en.wikipedia.org/wiki/Public_domainhttps://en.wikipedia.org/wiki/Public_domain
This dataset represents States and equivalent entities, which are the primary governmental divisions of the United States. 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. In addition to the fifty States, the Census Bureau treats the District of Columbia, Puerto Rico, and each of the Island Areas (American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the U.S. Virgin Islands) as the statistical equivalents of States for the purpose of data presentation.
The Elevation KML shapefile and coordinates. Visit https://dataone.org/datasets/https%3A%2F%2Fpasta.lternet.edu%2Fpackage%2Fmetadata%2Feml%2Fknb-lter-luq%2F11%2F9 for complete metadata about this dataset.
Attribution-NoDerivs 3.0 (CC BY-ND 3.0)https://creativecommons.org/licenses/by-nd/3.0/
License information was derived automatically
The seamless, county-wide parcel layer was digitized from official Assessor Parcel (AP) Maps which were originally maintained on mylar sheets and/or maintained as individual Computer Aided Design (CAD) drawing files (e.g., DWG). The CRA office continues to maintain the official AP Maps in CAD drawings and Information Systems Department/Geographic Information Systems (ISD/GIS) staff apply updates from these maps to the seamless parcel base in the County’s Enterprise GIS. This layer is a partial view of the Information Sales System (ISS) extract, a report of property characteristics taken from the County’s Megabyte Property Tax System (MPTS). This layer may be missing some attributes (e.g., Owner Name) which may not be published to the Internet due to privacy conditions under the California Public Records Act (CPRA). Please contact the Clerk-Recorder-Assessor (CRA) office at (707) 565-1888 for information on availability, associated fees, and access to other versions of Sonoma County parcels containing additional property characteristics.The seamless parcel layer is updated and published to the Internet on a monthly basis.The seamless parcel layer was developed from the source data using the general methodology outlined below. The mylar sheets were scanned and saved to standard image file format (e.g., TIFF). The individual scanned maps or CAD drawing files were imported into GIS software and geo-referenced to their corresponding real-world locations using high resolution orthophotography as control. The standard approach was to rescale and rotate the scanned drawing (or CAD file) to match the general location on the orthophotograph. Then, appropriate control points were selected to register and rectify features on the scanned map (or CAD drawing file) to the orthophotography. In the process, features in the scanned map (or CAD drawing file) were transformed to real-world coordinates, and line features were created using “heads-up digitizing” and stored in new GIS feature classes. Recommended industry best practices were followed to minimize root mean square (RMS) error in the transformation of the data, and to ensure the integrity of the overall pattern of each AP map relative to neighboring pages. Where available Coordinate Geometry (COGO) & survey data, tied to global positioning systems (GPS) coordinates, were also referenced and input to improve the fit and absolute location of each page. The vector lines were then assembled into a polygon features, with each polygon being assigned a unique identifier, the Assessor Parcel Number (APN). The APN field in the parcel table was joined to the corresponding APN field in the assessor property characteristics table extracted from the MPTS database to create the final parcel layer. The result is a seamless parcel land base, each parcel polygon coded with a unique APN, assembled from approximately 6,000 individual map page of varying scale and accuracy, but ensuring the correct topology of each feature within the whole (i.e., no gaps or overlaps). The accuracy and quality of the parcels varies depending on the source. See the fields RANK and DESCRIPTION fields below for information on the fit assessment for each source page. These data should be used only for general reference and planning purposes. It is important to note that while these data were generated from authoritative public records, and checked for quality assurance, they do not provide survey-quality spatial accuracy and should NOT be used to interpret the true location of individual property boundary lines. Please contact the Sonoma County CRA and/or a licensed land surveyor before making a business decision that involves official boundary descriptions.
TIGER road data for the MSA. When compared to high-resolution imagery and other transportation datasets positional inaccuracies were observed. As a result caution should be taken when using this dataset. TIGER, TIGER/Line, and Census TIGER are registered trademarks of the U.S. Census Bureau. ZCTA is a trademark of the U.S. Census Bureau. The Census 2000 TIGER/Line files are an extract of selected geographic and cartographic information from the Census TIGER data base. The geographic coverage for a single TIGER/Line file is a county or statistical equivalent entity, with the coverage area based on January 1, 2000 legal boundaries. A complete set of census 2000 TIGER/Line files includes all counties and statistically equivalent entities in the United States, Puerto Rico, and the Island Areas. The Census TIGER data base represents a seamless national file with no overlaps or gaps between parts. However, each county-based TIGER/Line file is designed to stand alone as an independent data set or the files can be combined to cover the whole Nation. The Census 2000 TIGER/Line files consist of line segments representing physical features and governmental and statistical boundaries. The boundary information in the TIGER/Line files are for statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes does not constitute a determination of jurisdictional authority or rights of ownership or entitlement. The Census 2000 TIGER/Line files do NOT contain the Census 2000 urban areas which have not yet been delineated. The files contain information distributed over a series of record types for the spatial objects of a county. There are 17 record types, including the basic data record, the shape coordinate points, and geographic codes that can be used with appropriate software to prepare maps. Other geographic information contained in the files includes attributes such as feature identifiers/census feature class codes (CFCC) used to differentiate feature types, address ranges and ZIP Codes, codes for legal and statistical entities, latitude/longitude coordinates of linear and point features, landmark point features, area landmarks, key geographic features, and area boundaries. The Census 2000 TIGER/Line data dictionary contains a complete list of all the fields in the 17 record types. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.
This dataset contains shapefiles outlining 558 neighborhoods in 50 major cities in New York state, notably including Albany, Buffalo, Ithaca, New York City, Rochester, and Syracuse. This adds context to your datasets by identifying the neighborhood of any locations you have, as coordinates on their own don't carry a lot of information.
What's inside is more than just rows and columns. Make it easy for others to get started by describing how you acquired the data and what time period it represents, too. What fields does it include? What's the time period of the data and how was it collected?
Four files are included containing data about the shapes: an SHX file, a DBF file, an SHP file, and a PRJ file. Including all of them in your input data are necessary, as they all contain pieces of the data; one file alone will not have everything that you need.
Seeing how none of these files are plaintext, it can be a little difficult to get set up with them. I highly recommend using mapshaper.org to get started- this site will show you the boundaries drawn on a plane, as well as allow you to export the files in a number of different formats (e.g. GeoJSON, CSV) if you are unable to use them in the format they are provided in. Personally, I have found it easier to work with the shapefile format though.
To get started with the shapefile in R, you can use the the rgdal and rgeos packages. To see an example of these being used, be sure to check out my kernel, "Incorporating neighborhoods into your model".
These files were provided by Zillow and are available under a Creative Commons license.
I'll be using these in the NYC Taxi Trip Duration competition to add context to the pickup and dropoff locations of the taxi rides and hopefully greatly improve my predictions.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Analysis of ‘Geography Lookup Table’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/801e1bd7-e19b-4cb9-8959-b34b8fc61ab7 on 12 February 2022.
--- Dataset description provided by original source is as follows ---
Summary data of fixed broadband coverage by geographic area. License and Attribution: Broadband data from FCC Form 477, and data from the U.S. Census Bureau that are presented on this site are offered free and not subject to copyright restriction. Data and content created by government employees within the scope of their employment are not subject to domestic copyright protection under 17 U.S.C. § 105. See, e.g., U.S. Government Works.
While not required, when using content, data, documentation, code and related materials from fcc.gov or broadbandmap.fcc.gov in your own work, we ask that proper credit be given. Examples include: • Source data: FCC Form 477 • Map layer based on FCC Form 477 • Code data based on broadbandmap.fcc.gov
The geography look ups are created from the US census shapefiles, which are in Global Coordinate System North American Datum of 1983 (GCS NAD83). The coordinates do not get reprojected during processing. The "centroid_lng", "centroid_lat" columns in the lookup table are the exact values from the US census shapefile (INTPTLON, INTPTLAT). The "bbox_arr" column is calculated from the bounding box/extent of the original geometry in the shapefile; no reprojection or transformations are done to the geometry.
--- Original source retains full ownership of the source dataset ---
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Shape files (see also Scotland study area.shp) for the mapping the intermediate zones for Scotland.
Summary data of fixed broadband coverage by geographic area. License and Attribution: Broadband data from FCC Form 477, and data from the U.S. Census Bureau that are presented on this site are offered free and not subject to copyright restriction. Data and content created by government employees within the scope of their employment are not subject to domestic copyright protection under 17 U.S.C. § 105. See, e.g., U.S. Government Works. While not required, when using content, data, documentation, code and related materials from fcc.gov or broadbandmap.fcc.gov in your own work, we ask that proper credit be given. Examples include: • Source data: FCC Form 477 • Map layer based on FCC Form 477 • Code data based on broadbandmap.fcc.gov The geography look ups are created from the US census shapefiles, which are in Global Coordinate System North American Datum of 1983 (GCS NAD83). The coordinates do not get reprojected during processing. The "centroid_lng", "centroid_lat" columns in the lookup table are the exact values from the US census shapefile (INTPTLON, INTPTLAT). The "bbox_arr" column is calculated from the bounding box/extent of the original geometry in the shapefile; no reprojection or transformations are done to the geometry.
Attribution 3.0 (CC BY 3.0)https://creativecommons.org/licenses/by/3.0/
License information was derived automatically
This dataset and its metadata statement were supplied to the Bioregional Assessment Programme by a third party and are presented here as originally supplied.
This dataset contains 4 different scale GEODATA TOPO series, Geoscience Australia topographic datasets. 1M, 2.5M, 5M and 10M with age ranges from 2001 to 2004.
1:1 Million - Global Map Australia 1M 2001 is a digital dataset covering the Australian landmass and island territories, at a 1:1 million scale. Product Specifications -Themes: It consists of eight layers of information: Vector layers - administrative boundaries, drainage, transportation and population centres Raster layers - elevation, vegetation, land use and land cover -Coverage: Australia -Currency: Variable, based on GEODATA TOPO 250K Series 1 -Coordinates: Geographical -Datum: GDA94, AHD -Medium: Free online -Format: -Vector: ArcInfo Export, ESRI Shapefile, MapInfo mid/mif and Vector Product Format (VPF) -Raster: Band Interleaved by Line (BIL)
1:2.5 Million - GEODATA TOPO 2.5M 2003 is a national seamless data product aimed at regional or national applications. It is a vector representation of the Australian landscape as represented on the Geoscience Australia 2.5 million general reference map and is suitable for GIS applications. The product consists of the following layers: built-up areas; contours; drainage; framework; localities; offshore; rail transport; road transport; sand ridges; Spot heights; and waterbodies. It is a vector representation of the Australian landscape as represented on the Geoscience Australia 1:2.5 million scale general reference maps. This data supersedes the TOPO 2.5M 1998 product through the following characteristics: developed according to GEODATA specifications derived from GEODATA TOPO 250K Series 2 data where available. Product Specifications Themes: GEODATA TOPO 2.5M 2003 consists of eleven layers: built-up areas; contours; drainage; framework; localities; offshore; rail transport; road transport; sand ridges; spot heights; and waterbodies Coverage: Australia Currency: 2003 Coordinates: Geographical Datum: GDA94, AHD Format: ArcInfo Export, ArcView Shapefile and MapInfo mid/mif Medium: Free online - Available in ArcInfo Export, ArcView Shapefile and MapInfo mid/mif
1:5 Million - GEODATA TOPO 5M 2004 is a national seamless data product aimed at regional or national applications. It is a vector representation of the Australian landscape as represented on the Geoscience Australia 5 million general reference map and is suitable for GIS applications. Offshore and sand ridge layers were sourced from scanning of the original 1:5 million map production material. The remaining nine layers were derived from the GEODATA TOPO 2.5M 2003 dataset. Free online. Available in ArcInfo Export, ArcView Shapefile and MapInfo mid/mif. Product Specifications: Themes: consists of eleven layers: built-up areas; contours; drainage; framework; localities; offshore; rail transport; road transport; sand ridges, spot heights and waterbodies Coverage: Australia Currency: 2004 Coordinates: Geographical Datum: GDA94, AHD Format: ArcInfo Export, ArcView Shapefile and MapInfo mid/mif Medium: Free online
1:10 Million - The GEODATA TOPO 10M 2002 version of this product has been completely revised, including the source information. The data is derived primarily from GEODATA TOPO 250K Series 1 data. In October 2003, the data was released in double precision coordinates. It provides a fundamental base layer of geographic information on which you can build a wide range of applications and is particularly suited to State-wide and national applications. The data consists of ten layers: built-up areas, contours, drainage, Spot heights, framework, localities, offshore, rail transport, road transport, and waterbodies. Coverage: Australia Currency: 2002 Coordinates: Geographical Datum: GDA94, AHD Format: ArcInfo Export, Arcview Shapefile and MapInfo mid/mif Medium: Free online
1:1Million - Vector data was produced by generalising Geoscience Australia's GEODATA TOPO 250K Series 1 data and updated using Series 2 data where available in January 2001. Raster data was sourced from USGS and updated using GEODATA 9 Second DEM Series 2, 1:5 million, Vegetation - Present (1988) and National Land and Water Resources data. However, updates have not been subjected to thorough vetting. A more detailed land use classification for Australia is available at www.nlwra.gov.au.
Full Metadata - http://www.ga.gov.au/metadata-gateway/metadata/record/gcat_48006
1:2.5Million - Data for the Contours, Offshore, and Sand ridge layers was captured from 1:2.5 million scale mapping by scanning stable base photographic film positives of the original map production material. The key source material for Built-up areas, Drainage, Spot heights, Framework, Localities, Rail transport, Road transport and Waterbodies layers was GEODATA TOPO 2.5M 2003
Full Metadata - http://www.ga.gov.au/metadata-gateway/metadata/record/gcat_60804
1:5Million - Offshore and Sand Ridge layers have been derived from 1:5M scale mapping by scanning stable base photographic film positives of the various layers of the original map production material. The remaining layers were sourced from the GEODATA TOPO 2.5M 2003 product.
Full Metadata - http://www.ga.gov.au/metadata-gateway/metadata/record/gcat_61114
1:10Million - The key source for production of the Builtup Areas, Drainage, Framework, Localities, Rail Transport, Road Transport and Waterbodies layers was the GEODATA TOPO 250K Series 1 product. Some revision of the Builtup Areas, Road Transport, Rail Transport and Waterbodies layers was carried out using the latest available satelite imagery. The primary source for the Spot Heights, Contours and Offshore layers was the GEODATA TOPO 10M Version 1 product. A further element to the production of GEODATA TOPO 10M 2002 has been the datum shift from the Australian Geodetic Datum 1966 (AGD66) to the Geocentric Datum of Australia 1994 (GDA94).
Full Metadata - http://www.ga.gov.au/metadata-gateway/metadata/record/gcat_60803
Geoscience Australia (2001) Geoscience Australia GEODATA TOPO series - 1:1 Million to 1:10 Million scale. Bioregional Assessment Source Dataset. Viewed 13 March 2019, http://data.bioregionalassessments.gov.au/dataset/310c5d07-5a56-4cf7-a5c8-63bdb001cd1a.
Spider lines depict Euclidean distance-based routes that connect each pair of points. They are a useful tool for visualization. In landscape genetics this represents the isolation-by-distance hypothesis. Previously there were other 3rd party tools that achieved this on the Arcscripts website. Currently it appears that this functionality is only available with a Business Analyst license of ArcGIS. This tool make a few assumptions: 1. You wish to connect all pairs of points.2. You have a point shapefile.3. The point shapefile is in a projected coordinate system.4. The point shapefile has fields called "Easting" and "Northing" that represent the X and Y coordinates respectively. If these fields are not named this excatly then the tool will fail.5. You have a field that describes the name of the pairs of the site (point). Please do not use a geodatabase feature class.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This Python script (Shape2DJI_Pilot_KML.py) will scan a directory, find all the ESRI shapefiles (.shp), reproject to EPSG 4326 (geographic coordinate system WGS84 ellipsoid), create an output directory and make a new Keyhole Markup Language (.kml) file for every line or polygon found in the files. These new *.kml files are compatible with DJI Pilot 2 on the Smart Controller (e.g., for M300 RTK). The *.kml files created directly by ArcGIS or QGIS are not currently compatible with DJI Pilot.
Parcels and property data maintained and provided by Lee County Property Appraiser are converted to points. Property attribute data joined to parcel GIS layer by Lee County Government GIS. This dataset is generally used in spatial analysis.Process description: Parcel polygons, condominium points and property data provided by the Lee County Property Appraiser are processed by Lee County's GIS Department using the following steps:Join property data to parcel polygons Join property data to condo pointsConvert parcel polygons to points using ESRI's ArcGIS tool "Feature to Point" and designate the "Source" field "P".Load Condominium points into this layer and designate the "Source" field "C". Add X/Y coordinates in Florida State Plane West, NAD 83, feet using the "Add X/Y" tool.Projected coordinate system name: NAD_1983_StatePlane_Florida_West_FIPS_0902_FeetGeographic coordinate system name: GCS_North_American_1983
Name
Type
Length
Description
STRAP
String
25
17-digit Property ID (Section, Township, Range, Area, Block, Lot)
BLOCK
String
10
5-digit portion of STRAP (positions 9-13)
LOT
String
8
Last 4-digits of STRAP
FOLIOID
Double
8
Unique Property ID
MAINTDATE
Date
8
Date LeePA staff updated record
MAINTWHO
String
20
LeePA staff who updated record
UPDATED
Date
8
Data compilation date
HIDE_STRAP
String
1
Confidential parcel ownership
TRSPARCEL
String
17
Parcel ID sorted by Township, Range & Section
DORCODE
String
2
Department of Revenue. See https://leepa.org/Docs/Codes/DOR_Code_List.pdf
CONDOTYPE
String
1
Type of condominium: C (commercial) or R (residential)
UNITOFMEAS
String
2
Type of Unit of Measure (ex: AC=acre, LT=lot, FF=frontage in feet)
NUMUNITS
Double
8
Number of Land Units (units defined in UNITOFMEAS)
FRONTAGE
Integer
4
Road Frontage in Feet
DEPTH
Integer
4
Property Depth in Feet
GISACRES
Double
8
Total Computed Acres from GIS
TAXINGDIST
String
3
Taxing District of Property
TAXDISTDES
String
60
Taxing District Description
FIREDIST
String
3
Fire District of Property
FIREDISTDE
String
60
Fire District Description
ZONING
String
10
Zoning of Property
ZONINGAREA
String
3
Governing Area for Zoning
LANDUSECOD
SmallInteger
2
Land Use Code
LANDUSEDES
String
60
Land Use Description
LANDISON
String
5
BAY,CANAL,CREEK,GULF,LAKE,RIVER & GOLF
SITEADDR
String
55
Lee County Addressing/E911
SITENUMBER
String
10
Property Location - Street Number
SITESTREET
String
40
Street Name
SITEUNIT
String
5
Unit Number
SITECITY
String
20
City
SITEZIP
String
5
Zip Code
JUST
Double
8
Market Value
ASSESSED
Double
8
Building Value + Land Value
TAXABLE
Double
8
Taxable Value
LAND
Double
8
Land Value
BUILDING
Double
8
Building Value
LXFV
Double
8
Land Extra Feature Value
BXFV
Double
8
Building Extra Feature value
NEWBUILT
Double
8
New Construction Value
AGAMOUNT
Double
8
Agriculture Exemption Value
DISAMOUNT
Double
8
Disability Exemption Value
HISTAMOUNT
Double
8
Historical Exemption Value
HSTDAMOUNT
Double
8
Homestead Exemption Value
SNRAMOUNT
Double
8
Senior Exemption Value
WHLYAMOUNT
Double
8
Wholly Exemption Value
WIDAMOUNT
Double
8
Widow Exemption Value
WIDRAMOUNT
Double
8
Widower Exemption Value
BLDGCOUNT
SmallInteger
2
Total Number of Buildings on Parcel
MINBUILTY
SmallInteger
2
Oldest Building Built
MAXBUILTY
SmallInteger
2
Newest Building Built
TOTALAREA
Double
8
Total Building Area
HEATEDAREA
Double
8
Total Heated Area
MAXSTORIES
Double
8
Tallest Building on Parcel
BEDROOMS
Integer
4
Total Number of Bedrooms
BATHROOMS
Double
8
Total Number of Bathrooms / Not For Comm
GARAGE
String
1
Garage on Property 'Y'
CARPORT
String
1
Carport on Property 'Y'
POOL
String
1
Pool on Property 'Y'
BOATDOCK
String
1
Boat Dock on Property 'Y'
SEAWALL
String
1
Sea Wall on Property 'Y'
NBLDGCOUNT
SmallInteger
2
Total Number of New Buildings on ParcelTotal Number of New Buildings on Parcel
NMINBUILTY
SmallInteger
2
Oldest New Building Built
NMAXBUILTY
SmallInteger
2
Newest New Building Built
NTOTALAREA
Double
8
Total New Building Area
NHEATEDARE
Double
8
Total New Heated Area
NMAXSTORIE
Double
8
Tallest New Building on Parcel
NBEDROOMS
Integer
4
Total Number of New Bedrooms
NBATHROOMS
Double
8
Total Number of New Bathrooms/Not For Comm
NGARAGE
String
1
New Garage on Property 'Y'
NCARPORT
String
1
New Carport on Property 'Y'
NPOOL
String
1
New Pool on Property 'Y'
NBOATDOCK
String
1
New Boat Dock on Property 'Y'
NSEAWALL
String
1
New Sea Wall on Property 'Y'
O_NAME
String
30
Owner Name
O_OTHERS
String
120
Other Owners
O_CAREOF
String
30
In Care Of Line
O_ADDR1
String
30
Owner Mailing Address Line 1
O_ADDR2
String
30
Owner Mailing Address Line 2
O_CITY
String
30
Owner Mailing City
O_STATE
String
2
Owner Mailing State
O_ZIP
String
9
Owner Mailing Zip
O_COUNTRY
String
30
Owner Mailing Country
S_1DATE
Date
8
Most Current Sale Date > $100.00
S_1AMOUNT
Double
8
Sale Amount
S_1VI
String
1
Sale Vacant or Improved
S_1TC
String
2
Sale Transaction Code
S_1TOC
String
2
Sale Transaction Override Code
S_1OR_NUM
String
13
Original Record (Lee County Clerk)
S_2DATE
Date
8
Previous Sale Date > $100.00
S_2AMOUNT
Double
8
Sale Amount
S_2VI
String
1
Sale Vacant or Improved
S_2TC
String
2
Sale Transaction Code
S_2TOC
String
2
Sale Transaction Override Code
S_2OR_NUM
String
13
Original Record (Lee County Clerk)
S_3DATE
Date
8
Next Previous Sale Date > $100.00
S_3AMOUNT
Double
8
Sale Amount
S_3VI
String
1
Sale Vacant or Improved
S_3TC
String
2
Sale Transaction Code
S_3TOC
String
2
Sale Transaction Override Code
S_3OR_NUM
String
13
Original Record (Lee County Clerk)
S_4DATE
Date
8
Next Previous Sale Date > $100.00
S_4AMOUNT
Double
8
Sale Amount
S_4VI
String
1
Sale Vacant or Improved
S_4TC
String
2
Sale Transaction Code
S_4TOC
String
2
Sale Transaction Override Code
S_4OR_NUM
String
13
This map package includes the official Tribal areas that NTIA recognizes for their grant programs. The map package includes the following layers. Alaska Native Villages - this layer represents Alaska Native Villages and is created by Census. The layer was downloaded on Jan. 28, 2025, from here: TIGER/Line® Shapefiles.Native Hawaiian Areas - this layer represents Native Hawaiian Areas and is created by Census. The layer was downloaded on Jan. 28, 2025, from here: TIGER/Line® Shapefiles and has been filtered to only include Native Hawaiian Areas. BIA AIAN National LAR - this layer represents American Indian Lands and is created by the BIA. The layer was accessed here: BIA Access Open Data and was exported on Jan. 28, 2025. The layer was filtered to only include lands across the continental U.S. BIA AIAN LAR Supplemental - this layer is a supplemental dataset to the LAR. The layer was accessed here: BIA Access Open Data and was exported on Jan. 28, 2025.BIA AIAN Tribal Statistical Areas - this layer represents Tribal Statistical Areas located in Oklahoma. The layer was accessed here: BIA Access Open Data and was exported on Jan. 28, 2025.This map package was created on Jan. 28, 2025 and was created using ArcGIS Pro 3.4.0. If you have any questions regarding the map package please e-mail NTIAanalytics@ntia.gov.ResourcesCensus DataBIA Open DataBIA Data DisclaimerBy using this product, the user agrees to the below terms and conditions:No warranty is made by the Bureau of Indian Affairs (BIA) for the use of the data for purposes not intended by the BIA. This GIS Dataset may contain errors. There is no impact on the legal status of the land areas depicted herein and no impact on land ownership. No legal inference can or should be made from the information in this GIS Dataset. The GIS Dataset is prepared strictly for illustrative and reference purposes only and should not be used, and is not intended for legal, survey, engineering or navigation purposes. These data have been developed from the best available sources. Although efforts have been made to ensure that the data are accurate and reliable, errors and variable conditions originating from source documents and/or the translation of information from source documents to the systems of record continue to exist. Users must be aware of these conditions and bear responsibility for the appropriate use of the information with respect to possible errors, scale, resolution, rectification, positional accuracy, development methodology, time period, environmental and climatic conditions and other circumstances specific to these data. The user is responsible for understanding the accuracy limitations of the data provided herein. The burden for determining fitness for use lies entirely with the user. The user should refer to the accompanying metadata notes for a description of the data and data development procedures.Census Use RestraintsThe TIGER/Line Shapefile products are not copyrighted however TIGER/Line and Census TIGER are registered trademarks of the U.S. Census Bureau. These products are free to use in a product or publication, however acknowledgement must be given to the U.S. Census Bureau as the source. The boundary information in the TIGER/Line Shapefiles are for statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes does not constitute a determination of jurisdictional authority or rights of ownership or entitlement and they are not legal land descriptions. Coordinates in the TIGER/Line shapefiles have six implied decimal places, but the positional accuracy of these coordinates is not as great as the six decimal places suggest.
Attribution-NonCommercial-ShareAlike 4.0 (CC BY-NC-SA 4.0)https://creativecommons.org/licenses/by-nc-sa/4.0/
License information was derived automatically
This file contains European countries in a shapefile format that can be used in python, R or matlab. The file has been created by Drin Marmullaku based on GADM version 4.1 (https://gadm.org/) and distributed according to their license (https://gadm.org/license.html).
Please cite as: Sevdari, Kristian; Marmullaku, Drin (2023). Shapefile of European countries. Technical University of Denmark. Dataset. https://doi.org/10.11583/DTU.23686383 This dataset is distributed under a CCBY-NC-SA 4.0 license
Using the data to create maps for publishing of academic research articles is allowed. Thus you can use the maps you made with GADM data for figures in articles published by PLoS, Springer Nature, Elsevier, MDPI, etc. You are allowed (but not required) to publish these articles (and the maps they contain) under an open license such as CC-BY as is the case with PLoS journals and may be the case with other open access articles. Data for the following countries is covered by a a different license Austria: Creative Commons Attribution-ShareAlike 2.0 (source: Government of Austria)
This dataset contains shapefile boundaries for CA State, counties and places from the US Census Bureau's 2023 MAF/TIGER database. Current geography in the 2023 TIGER/Line Shapefiles generally reflects the boundaries of governmental units in effect as of January 1, 2023.
ps-places-metadata-v1.01
This dataset comprises a pair of layers, (points and polys) which attempt to better locate "populated places" in NZ. Populated places are defined here as settled areas, either urban or rural where densitys of around 20 persons per hectare exist, and something is able to be seen from the air.
The only liberally licensed placename dataset is currently LINZ geographic placenames, which has the following drawbacks: - coordinates are not place centers but left most label on 260 series map - the attributes are outdated
This dataset necessarily involves cleaving the linz placenames set into two, those places that are poplulated, and those unpopulated. Work was carried out in four steps. First placenames were shortlisted according to the following criterion:
- all places that rated at least POPL in the linz geographic places layer, ie POPL, METR or TOWN or USAT were adopted.
- Then many additional points were added from a statnz meshblock density analysis.
- Finally remaining points were added from a check against linz residential polys, and zenbu poi clusters.
Spelling is broadly as per linz placenames, but there are differences for no particular reason. Instances of LINZ all upper case have been converted to sentance case. Some places not presently in the linz dataset are included in this set, usually new places, or those otherwise unnamed. They appear with no linz id, and are not authoritative, in some cases just wild guesses.
Density was derived from the 06 meshblock boundarys (level 2, geometry fixed), multipart conversion, merging in 06 usually resident MB population then using the formula pop/area*10000. An initial urban/rural threshold level of 0.6 persons per hectare was used.
Step two was to trace the approx extent of each populated place. The main purpose of this step was to determine the relative area of each place, and to create an intersection with meshblocks for population. Step 3 involved determining the political center of each place, broadly defined as the commercial center.
Tracing was carried out at 1:9000 for small places, and 1:18000 for large places using either bing or google satellite views. No attempt was made to relate to actual town 'boundarys'. For example large parks or raceways on the urban fringe were not generally included. Outlying industrial areas were included somewhat erratically depending on their connection to urban areas.
Step 3 involved determining the centers of each place. Points were overlaid over the following layers by way of a base reference:
a. original linz placenames b. OSM nz-locations points layer c. zenbu pois, latest set as of 5/4/11 d. zenbu AllSuburbsRegions dataset (a heavily hand modified) LINZ BDE extract derived dataset courtesy Zenbu. e. LINZ road-centerlines, sealed and highway f. LINZ residential areas, g. LINZ building-locations and building footprints h. Olivier and Co nz-urban-north and south
Therefore in practice, sources c and e, form the effective basis of the point coordinates in this dataset. Be aware that e, f and g are referenced to the LINZ topo data, while c and d are likely referenced to whatever roading dataset google possesses. As such minor discrepencys may occur when moving from one to the other.
Regardless of the above, this place centers dataset was created using the following criteria, in order of priority:
To be clear the coordinates are manually produced by eye without any kind of computation. As such the points are placed approximately perhaps plus or minus 10m, but given that the roads layers are not that flash, no attempt was made to actually snap the coordinates to the road junctions themselves.
The final step involved merging in population from SNZ meshblocks (merge+sum by location) of popl polys). Be aware that due to the inconsistent way that meshblocks are defined this will result in inaccurate populations, particular small places will collect population from their surrounding area. In any case the population will generally always overestimate by including meshblocks that just nicked the place poly. Also there are a couple of dozen cases of overlapping meshblocks between two place polys and these will double count. Which i have so far made no attempt to fix.
Merged in also tla and regions from SNZ shapes, a few of the original linz atrributes, and lastly grading the size of urban areas according to SNZ 'urban areas" criteria. Ie: class codes:
Note that while this terminology is shared with SNZ the actual places differ owing to different decisions being made about where one area ends an another starts, and what constiutes a suburb or satellite. I expect some discussion around this issue. For example i have included tinwald and washdyke as part of ashburton and timaru, but not richmond or waikawa as part of nelson and picton. Im open to discussion on these.
No attempt has or will likely ever be made to locate the entire LOC and SBRB data subsets. We will just have to wait for NZFS to release what is thought to be an authoritative set.
Shapefiles are all nztm. Orig data from SNZ and LINZ was all sourced in nztm, via koordinates, or SNZ. Satellite tracings were in spherical mercator/wgs84 and converted to nztm by Qgis. Zenbu POIS were also similarly converted.
Shapefile: Points id : integer unique to dataset name : name of popl place, string class : urban area size as above. integer tcode : SNZ tla code, integer rcode : SNZ region code, 1-16, integer area : area of poly place features, integer in square meters. pop : 2006 usually resident popluation, being the sum of meshblocks that intersect the place poly features. Integer lid : linz geog places id desc_code : linz geog places place type code
Shapefile: Polygons gid : integer unique to dataset, shared by points and polys name : name of popl place, string, where spelling conflicts occur points wins area : place poly area, m2 Integer
Clarification about the minorly derived nature of LINZ and google data needs to be sought. But pending these copyright complications, the actual points data is essentially an original work, released as public domain. I retain no copyright, nor any responsibility for data accuracy, either as is, or regardless of any changes that are subsequently made to it.
Peter Scott 16/6/2011
v1.01 minor spelling and grammar edits 17/6/11
U.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
USGS is assessing the feasibility of map projections and grid systems for lunar surface operations. We propose developing a new Lunar Transverse Mercator (LTM), the Lunar Polar Stereographic (LPS), and the Lunar Grid Reference Systems (LGRS). We have also designed additional grids designed to NASA requirements for astronaut navigation, referred to as LGRS in Artemis Condensed Coordinates (ACC), but this is not released here. LTM, LPS, and LGRS are similar in design and use to the Universal Transverse Mercator (UTM), Universal Polar Stereographic (LPS), and Military Grid Reference System (MGRS), but adhere to NASA requirements. LGRS ACC format is similar in design and structure to historic Army Mapping Service Apollo orthotopophoto charts for navigation. The Lunar Transverse Mercator (LTM) projection system is a globalized set of lunar map projections that divides the Moon into zones to provide a uniform coordinate system for accurate spatial representation. It uses a transverse Me ...