This layer was developed by the Research & Analytics Division of the Atlanta Regional Commission as a 10-county dataset, which was recently expanded to its current extent. In many cases, the boundaries have been significantly changed by ARC's GIS Division using a variety of sources to improve their accuracy, including ESRI, GDT, the U.S. Postal Service (USPS), Aero Surveys, Inc., the U.S. Census Bureau, local government datasets and digital orthophotography. Please note, there are some inherent problems with ZIP codes which affect the use of this Layer. Since there are overlapping areas with some of the USPS ZIP code data, this Layer can only show the estimated general area for many ZIP codes. Also note that some ZIP codes refer to post office boxes which only represent point locations, thus are not part of this polygon Layer. Attributes:ZIP = ZIP code in string formatZIP_dbl = ZIP code in double formatShape.STArea() = Area in square feetSource: Atlanta Regional Commission (and various other sources)Date: 2006For additional information, please visit the Atlanta Regional Commission at www.atlantaregional.com

2010 US Census Block Groups for Hennepin County with subset of PL94-171 demographic data. The Hennepin County GIS Office downloaded US Census data from the following sites:Shapefiles:http://www.census.gov/cgi-bin/geo/shapefiles2010/main PL94-171:http://www.census.gov/rdo/data/2010_census_redistricting_data_pl_94-171_summary_files.html PL94-171 tabular data was post processed per instructions and stored in an Access database. Records and a subset of the 290 plus fields were extracted from the master tables using SQL statements. A copy of the statement has been included in the Lineage section of metadata. Tables were registered as a geodatabase and copied to a File Geodatabase. Shapefiles were imported into the File Geodatabase and projected to UTM Zone 15 N. The feature classes were joined to the tabular data and saved as the final US Census layer.The feature classes underwent visual inspection. The number of records were compared and checked. The attribute values were compared to existing Maptitude US Census data. Please contact the Hennepin GIS Office if you require additional PL94-171 fields. Hennepin County GIS Office A-705 Government Center Minneapolis, Minnesota 55487-075 GIS.Info@co.hennepin.mn.us Phone: 612-596-9484 FAX: 612-348-2837 The original metadata is contained below. 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. Block Groups (BGs) are defined before tabulation block delineation and numbering, but are clusters of blocks within the same census tract that have the same first digit of their 4-digit census block number from the same decennial census. For example, Census 2000 tabulation blocks 3001, 3002, 3003,.., 3999 within Census 2000 tract 1210.02 are also within BG 3 within that census tract. Census 2000 BGs generally contained between 600 and 3,000 people, with an optimum size of 1,500 people. Most BGs were delineated by local participants in the Census Bureau's Participant Statistical Areas Program (PSAP). The Census Bureau delineated BGs only where the PSAP participant declined to delineate BGs or where the Census Bureau could not identify any local PSAP participant. A BG usually covers a contiguous area. Each census tract contains at least one BG, and BGs are uniquely numbered within census tract. Within the standard census geographic hierarchy, BGs never cross county or census tract boundaries, but may cross the boundaries of other geographic entities like county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian / Alaska Native / Native Hawaiian areas. BGs have a valid code range of 0 through 9. BGs coded 0 were intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. For Census 2000, rather than extending a census tract boundary into the Great Lakes or out to the U.S. nautical three-mile limit, the Census Bureau delineated some census tract boundaries along the shoreline or just offshore. The Census Bureau assigned a default census tract number of 0 and BG of 0 to these offshore, water-only areas not included in regularly numbered census tract areas.

Link to Attribute Table Information: http://gis.hennepin.us/OpenData/Metadata/2010%20Census%20Block%20Groups.pdf

Use Limitations: This data (i) is furnished "AS IS" with no representation as to completeness or accuracy; (ii) is furnished with no warranty of any kind; and (iii) is not suitable for legal, engineering or surveying purposes. Hennepin County shall not be liable for any damage, injury or loss resulting from this data.

© US Census Bureau. See additional information in Abstract and Use Limitations. This data was modified by the Hennepin County GIS Office. This layer is a component of Datasets for Hennepin County AGOL and Hennepin County Open Data..

Building permit locations in Macon-Bibb County. Updated daily. Building permits are issued by Macon-Bibb County's Business Development Services Department. To look up a building permit visit http://www.co.bibb.ga.us/Permits/Permit_Lookup.asp. For more information about the Business Development Services Department visit http://www.maconbibb.us/business-development-services/.

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

The DC Main Streets commercial corridors were created for Department of Small and Local Business Development. The GIS layer represents the locations of neighborhood commercial districts comprised of specific streets designated by DSLBD as "Main Streets." DC Main Streets is a program through which the District government works with neighborhood organizations to revitalize the District's neighborhood business districts through a comprehensive and systemic strategy for business retention and attraction, commercial property improvements, and provision of coordinated corridor-wide services.

🇦🇺 Australia English Export Data Access APINSW Administrative Boundaries Theme multiCRSMultiCRS service - supporting requests in multiple Coordinate Reference Systems -Information SheetA new series of ‘multiCRS’ web services have been published to support GDA2020. These new ‘multiCRS’ services:· have a spatial reference of GDA2020· support alignment with GDA2020, GDA94 or [WGS 84-aligned-to-GDA2020] GIS environments, using built-in server-side transformations:o GDA94 < NTv2-CPD > GDA2020o GDA94 < NTv2-CPD > WGS 84 aligned to GDA2020o GDA2020 < NULL > WGS 84 aligned to GDA2020 Note: ESRI software will automatically align by transforming from the sourceSpatialReference (GDA94). Other software may need to set client-side transformations from the SpatialReference (GDA2020). Note: Client-side transformation(s) can be used to over-ride these default transformations.The original [WGS 84-aligned-to-GDA2020] is still available, without the ‘multiCRS’ suffix. In due course, and allowing time for user feedback and testing, it is intended that the original service name will adopt this new multiCRS functionally.Metadata Portal Metadata InformationContent TitleNSW Administrative Boundaries Theme multiCRSContent TypeOtherDescriptionThe Administrative Boundaries theme from NSW Foundation Spatial Data Framework (FSDF) is a collection of legislative, regulatory, political, maritime and general administrative boundaries sourced from local and state boundary datasets. They include: Parish County Suburb Local Government Area State Electoral District Federal Electoral Division Mines Subsidence District NSW Parks and Wildlife Service Reserve State Forest Domestic Water Front PrecinctThe Administrative Boundaries theme is used to show administrative areas that represent:Voting Districts Redistributions Zoning Socio-Economic analysis Regional Planning Service Distribution Local and State Government Boundaries In addition, Administrative Boundaries can also be used for analysis and to look at trends over time. Administrative boundary data in combination with geo-coded address data, demographic information and agency specific business information underpins the ability to perform high quality spatial analysis. The use of this data in combination with other data includes: Evidence-based development and assessment of government policy Providing the ability to undertake spatial accounting Regional analysis for government, health, education, business and a range of other purposes Support for emergency management Market catchment analysis, micromarketing, customer analysis and market segmentation Emergency management. Update frequencies vary for each dataset. Individual current status can be found under each spatial data profile.Initial Publication Date05/02/2020Data Currency01/01/3000Data Update FrequencyDailyContent SourceData provider filesFile TypeESRI File Geodatabase (*.gdb)Attribution© State of New South Wales (Spatial Services, a business unit of the Department of Customer Service NSW). For current information go to spatial.nsw.gov.auData Theme, Classification or Relationship to other DatasetsNSW Administrative Boundaries Theme of the Foundation Spatial Data Framework (FSDF)AccuracyThe dataset maintains a positional relationship to, and alignment with, the Lot and Property digital datasets. This dataset was captured by digitising the best available cadastral mapping at a variety of scales and accuracies, ranging from 1:500 to 1:250 000 according to the National Mapping Council of Australia, Standards of Map Accuracy (1975). Therefore, the position of the feature instance will be within 0.5mm at map scale for 90% of the well-defined points. That is, 1:500 = 0.25m, 1:2000 = 1m, 1:4000 = 2m, 1:25000 = 12.5m, 1:50000 = 25m and 1:100000 = 50m. A program to upgrade the spatial location and accuracy of data is ongoing.Spatial Reference System (dataset)GDA94Spatial Reference System (web service)OtherWGS84 Equivalent ToGDA2020Spatial ExtentFull stateContent LineageFor additional information, please contact us via the Spatial Services Customer HubData ClassificationUnclassifiedData Access PolicyOpenData QualityFor additional information, please contact us via the Spatial Services Customer HubTerms and ConditionsCreative CommonsStandard and SpecificationOpen Geospatial Consortium (OGC) implemented and compatible for consumption by common GIS platforms. Available as either cache or non-cache, depending on client use or requirement.Data CustodianDCS Spatial Services346 Panorama AveBathurst NSW 2795Point of ContactFor additional information, please contact us via the Spatial Services Customer HubData AggregatorDCS Spatial Services346 Panorama AveBathurst NSW 2795Data DistributorDCS Spatial Services346 Panorama AveBathurst NSW 2795Additional Supporting InformationData DictionariesTRIM Number

This file provides a rural-urban view of 2001 Lower Layer Super Output Areas (LSOA) in England and Wales. The ZIP file contains the Rural Urban Classification in XLSX and CSV format and includes a user guide. The files were originally from the NeSS website. Click on the Download button to download the ZIP file.The classification of rural and urban areas is the outcome of a project co-sponsored by:Office for National Statistics (ONS);Department for Environment, Food and Rural Affairs (Defra);Office of the Deputy Prime Minister (now Communities and Local Government);Countryside Agency (CA); andNational Assembly for Wales (NAW).The classification was developed in 2004 by a consortium co-ordinated by Prof. John Shepherd from Birkbeck College. The technical work was lead by Peter Bibby of University of Sheffield and the project also involved the University of Glamorgan and Geowise. The rural and urban classification of Output Areas, Super Output Areas (this dataset) and Wards has been provided to enable datasets to be analysed according to the classification. This provides a powerful tool for the development and monitoring of rural and urban policies.Please Note: Super Output Areas do not have all the same codes as the OA level Dataset. For SOAs and Wards the classifications for ‘Villages, Hamlets and Isolated Dwellings’ have been combined.Similar procedures to those used to classify Output Areas apply to the classification for the 34,378 Lower Layer Super Output Areas in the dataset. However the morphological classification differs in the number of categories as very few LSOAs can be classified as predominantly dispersed settlements. LSOAs are categorised into just three domains: urban 10k, town and fringe and villages, hamlets and isolated dwellings, using the key below:2005 Rural and Urban morphology indicator1 - denotes predominantly urban >10k2 - denotes predominantly town and fringe3 - denotes other rural (including village, hamlet and isolated dwellings)2005 Rural and Urban context indicator0 - denotes less sparsely populated areas1 - denotes sparsely populated areas