AbstractLocal Government Areas is a spatial representation of the administrative divisions that local governments are responsible for across the country. A Local Government Area (LGA) will typically have an elected council as well as a council leader (e.g. mayor, shire president). Local Government Areas aggregates the representations unique to each jurisdiction into a consistent, seamless representation of the LGA boundaries across Australia.Local Government Areas is designed to meet the needs of organisations that require a geospatial representation of LGA boundaries at both a local and national scale. The attribution provided within Local Government Areas allows for the application of the data across a wide range of commercial, government and research uses. Geoscape Australia welcomes your feedback on our Local Government Areas product. We also publish regular updates on the development of our products on the Geoscape website.CurrencyDate Modified: November 2025Modification Frequency: QuarterlyData ExtentCoordinate Reference:Geocentric Datum of Australia 2020 | GDA2020Spatial ExtentNorth: -8°South: -45°East: 160°West: 112°Source InformationThe data was obtained from data.gov.au, is also accessible through Geoscape Administrative Boundaries - Geoscapeas of August 2025. The Australian Government has negotiated the release of Administrative Boundaries to the whole economy under an open CCBY 4.0 licence.Users must only use the data in ways that are consistent with the Australian Privacy Principles issued under the Privacy Act 1988 (Cth).Lineage StatementLocal Government Areas is created through processing LGA data sourced from Australia’s States and Territories. Source attributes are mapped and standardised to provide a coherent definition across the jurisdiction supplies, with associated geometry being cleaned and processed to output a topologically consistent layer of Australia’s LGA boundaries at a national scale. Additional attributes have been generated and integrated by Geoscape to support the jurisdictional information as well as to provide convenience in the use and representation of the dataset. Local Government Areas is updated and released regularly and has integrated relationships with other Geoscape Products.This product is integrated with the following Geoscape products:LocalitiesWardsAddressing ServiceGeoscape Administrative Boundaries (comprised of Localities, Local Government Areas (LGAs), Wards, ABS Boundaries, Electoral Boundaries, State Boundaries, and Town Points) are created using a range of source data which is highlighted within their Data Copyright and Disclaimer.The Digital Atlas of Australia team have published a Feature Service for Local Government Areas using the Geographic Coordinate System: Geocentric Datum of Australia 2020 (GDA2020). Local Government Areas are aggregated from State and Territory data to cover the National extent of Australia.Data DictionaryAttribute nameDescriptionLGA Polygon (PID)Unique persistent identifier for the LGA polygon.LGA (PID)Persistent identifier for the LGA.Date CreatedDate this record was created.LGA NameThe name of the LGA.LGA Abbreviated NameThe abbreviated LGA name.StateThe abbreviated name of the State or Territory that the LGA spatially resides within.Geometry: Shape Area and LengthThe geometry of the polygon.State - Description TableDomain nameDescriptionNSWThe data is located within the state of New South Wales.NTThe data is located within the Northern Territory.OTThe data is located within the Other Territories classification. Other Territories covers the external Australian territories of Cocos (Keeling) Islands and Christmas Island.QLDThe data is located within the state of Queensland.SAThe data is located within the state of South Australia.TASThe data is located within the state of Tasmania.VICThe data is located within the state of Victoria.WAThe data is located within the state of Western Australia.ContactDepartment of Industry, Science and Resources (DISR),data@industry.gov.auFor technical support contact DigitalAtlas@ga.gov.au

The Metropolitan Council routinely compiles individual land use plans and plan amendments from communities within the seven-county Twin Cities metropolitan area into a single regional data layer. A principal goal of the Regional Planned Land Use dataset is to allow users to view, analyze and display planned land use data for anywhere in the seven county metropolitan area with a consistent land use classification scheme. The Metropolitan Council uses the Regional Planned Land Use (PLU) data to help monitor growth and plan for regional services such as regional parks, transit service, and wastewater collection and treatment.

Although the planned land use data is based on the locally adopted land use plans and designations for each community, it represent only data that has been submitted to the Metropolitan Council for review per the Metropolitan Land Planning Act of 1995 (Minn. Stat 473.864, Subd 2 and 473.175, Subd 1). See Data Quality Information (Section 2 of this metadata) for specifics about the Metropolitan Land Planning Act of 1995 under Completeness information.

Since there is no official State or Regional land use coding scheme that communities must conform with, the variability of content and codes between communities' land use plans is nearly as vast as the number of communities themselves (187). Differences among communities can range from the implementation of different land use categories to conflicting definitions of similar categories. The PLU dataset attempts to effectively level out the variability among communities by translating communities land use categories and descriptions into a common classification scheme developed and endorsed by MetroGIS (a regional GIS data sharing consortium) participants while retaining each communities' original categories. Although the comparability of land use plans between communities has greatly improved as a result of this translation or "regionalization" of communities' land use codes, it is possible that not all community land use definitions have been precisely translated into the most appropriate regional land use category.

In conjunction with other regional information (i.e., land use trend data, households and jobs forecasts), the PLU data can help communities more easily understand regional and sub-regional planning goals and Council staff, working with individual local units of government, can better plan for the future needs and financing of regional services.

- Contact individual communities for more information on their locally adopted planned land use categories.

- See Data Quality Information (Section 2 of this metadata) for specifics about the development of the regional dataset and its accuracy.

- See Entities and Attributes Information (Section 5 of this metadata) for specifics about the regional land use codes and categories.

This dataset is the definitive version of the annually released regional council boundaries for 2020 as defined by the regional councils and/or Local Government Commission, and maintained by Stats NZ (the custodian). This version contains 17 categories.

The regional council is the top tier of local government in New Zealand. There are 16 regional councils in New Zealand (defined by Part 1 of Schedule 2 of the Local Government Act 2002). Eleven are governed by an elected regional council, while five are governed by territorial authorities (the second tier of local government), who also perform the functions of a regional council and are known as unitary authorities.

Auckland Council unitary authority was formed in 2010, under the Local Government (Tamaki Makarau Reorganisation) Act 2009, replacing the Auckland Regional Council and seven territorial authorities.The seaward boundary of any coastal regional council is the twelve-mile New Zealand territorial limit. Regional councils are defined at meshblock and statistical area 2

Names are provided with and without tohutō/macrons. The name field without macrons is suffixed ‘ascii’.

This generalised version has been simplified for rapid drawing and is designed for thematic or web mapping purposes.

Digital boundary data became freely available on 1 July 2007.

Since its inception in 1991, the Data Access & Support Center (DASC) has served as the State of Kansas Geographic Information System (GIS) data clearinghouse. Created as a center for the archiving and distribution of geospatial data, DASC has worked to expand its service portfolio over the years. While data archiving and distribution are still at the core of DASC's mission, DASC also provides various geospatial services, including web-based application development and hosting, database development and integration, state and local coordination, technical support, and local GIS data backup. These services support the Kansas GIS Initiative and complement state and local GIS activities. During FY2023, DASC developed, maintained, and hosted GIS applications for numerous state agencies, including the Kansas 911 Coordinating Council, Kansas Department of Agriculture, Kansas Division of Emergency Management, Kansas Department of Revenue, Kansas State Department of Education, Kansas State Historical Society, Kansas Department of Transportation, Kansas Water Office, and the Kansas Department of Wildlife & Parks. The full Kansas geospatial catalog is administered by the Kansas Data Access & Support Center (DASC) and can be found at the following URL: https://hub.kansasgis.org/

Delaware Council on Farm and Food Policy's VisionIn 2018, Council members recognized that to effectively carry out the group’s function – to help facilitate market access for Delaware farmers and access to nutritious food for community members – using data to drive what we know and how we understand our local food system would be critical. The Council’s first project was mapping the geospatial locations of food retailers and other food access-related resources throughout Delaware. This map was planned as a baseline of existing capacities for members to build qualitative and quantitative analyses. Geographic Information Systems (GIS) tools are central to data analysis and project development, and allow Council members and partners to visualize and dissect vulnerabilities and areas of opportunity around our local food environment. Building a food data infrastructure is crucial to developing and conveying narratives that are clear and actionable, leading to tangible solutions and evidence-based policy decisions.University of Delaware Institute for Public Administration (IPA)IPA has been working with local governments for over 45 years. The partnerships of state, county, and local governments and affiliated organizations have allowed them to work on impactful projects, sponsor research, and host many training programs. IPA has been at the forefront of GIS technology since the early 1970s, providing the highest quality mapping, data, and analysis to an ever-expanding scope has remained consistent. From helping our older population age in place, providing assistance to local governments, to addressing the needs of school-age children, GIS technology has allowed us to learn how best to serve our communities.

This dataset is the definitive set of annually released territorial authority boundaries for 2020 as defined the territorial authorities and/or Local Government Commission and maintained by Stats NZ (the custodian). This version contains 68 categories.

A territorial authority is defined under the Local Government Act 2002 as a city or a district council. There are 67 territorial authorities in New Zealand. Some territorial authority boundaries are coterminous with regional council boundaries but there are several exceptions. An example is Taupo District, which is split between four regions, although most of its area falls within the Waikato Region. Territorial authorities are defined at meshblock, statistical area 1 (SA1) and statistical area 2 (SA2) levels.

Names are provided with and without tohutō/macrons. The name field without macrons is suffixed ‘ascii’.

This generalised version has been simplified for rapid drawing and is designed for thematic or web mapping purposes.

Digital boundary data became freely available on 1 July 2007.

This dataset is the definitive version of the annually released regional council boundaries as at 1 January 2023 as defined by regional councils and/or Local Government Commission, and maintained by Stats NZ (the custodian). This version contains 16 regional councils and area outside region (Chatham Islands Territory).

​

This dataset is the definitive version of the annually released regional council boundaries as at 1 January 2023 as defined by regional councils and/or Local Government Commission, and maintained by Stats NZ (the custodian). This version contains 16 regional councils and area outside region (Chatham Islands Territory). The annual boundaries are used for the full calendar year from 1 January. The annual update may have no changes from the previous release.

​

The regional council is the top tier of local government in New Zealand. Regional councils are defined under schedule 2, part 1 of the Local Government Act 2002. They were established in November 1989 after the abolition of the 22 local government regions. Regional council boundaries must coincide with meshblock boundaries under schedule 3, clause 17 of the Local Government Act 2002.

​

Regional council boundaries are based largely on water catchments, such as rivers, lakes, and harbours. The seaward boundary of the regions is the 12 mile (19.3km) New Zealand territorial limit. In determining regions, consideration was also given to regional communities of interest, natural resource management, land use planning, and environmental matters.

​

There are 16 regions which cover every territorial authority in New Zealand, with the exception of the Chatham Islands Territory (included in 99 Area Outside Region). Five regions are administered as unitary authorities, which function as both regional council and territorial authority. These unitary authorities are Auckland Council, Nelson City Council, and Gisborne, Tasman, and Marlborough District Councils. The Chatham Islands Council also performs some of the functions of a regional council but is not strictly a unitary authority. Unitary authorities act as regional councils for legislative purposes. Regional councils are responsible for administrating many environmental and transport matters, such as land transport planning and harbour navigation and safety.

​

Some regional council boundaries are coterminous with territorial authority boundaries, but there are several exceptions. An example is Taupo District, which is geographically split between four regions, although most of its area falls within the Waikato Region. Where territorial authorities straddle regional council boundaries, the affected area is statistically defined by complete regional councils. In general, however, regional councils contain complete territorial authorities.

​

Auckland Council unitary authority was formed in 2010, under the Local Government (Tamaki Makarau Reorganisation) Act 2009, replacing the Auckland Regional Council and seven territorial authorities.

​

Regional councils are defined at meshblock level. Statistical area 1 and statistical area 2 geographies nest within regional council boundaries.

​

Numbering

The standard classification of regional council is a flat classification and contains 17 categories (including ‘99 Area Outside Region’).

​

Generalised version

This generalised version has been simplified for rapid drawing and is designed for thematic or web mapping purposes.

​

Macrons

Names are provided with and without tohutō/macrons. The column name for those without macrons is suffixed ‘ascii’.

​

Digital data

Digital boundary data became freely available on 1 July 2007.

​

To download geographic classifications in table formats such as CSV please use Ariā

Export DataAccess APIAdministrative Boundaries Theme – Local Government AreaPlease Note WGS 84 service aligned to GDA94 This dataset has spatial reference [WGS 84 ≈ GDA94] which may result in misalignments when viewed in GDA2020 environments. A similar service with a ‘multiCRS’ suffix is available which can support GDA2020, GDA94 and WGS 84 ≈ GDA2020 environments. In due course, and allowing time for user feedback and testing, it is intended that the original service name will adopt the new multiCRS functionality.Metadata Portal Metadata InformationContent TitleNSW Administrative Boundaries Theme - Local Government AreaContent TypeHosted Feature LayerDescriptionNSW Local Government Area is a dataset within the Administrative Boundaries Theme (FSDF). It depicts polygons of gazetted boundaries defining the Local Government Area. It contains all of the cadastral line data or topographic features which are used to define the boundaries between adjoining shires, municipalities, cities (Local Government Act) and the unincorporated areas of NSW.The dataset also contains Council Names, ABS Codes, Ito Codes, Vg Codes, and Wb Codes. Any changes that occur to the dataset should have a reference in the authority of reference feature class in the Land Parcel and Property.Features are positioned in topological alignment within the extents of the land parcel and property polygons for each Local Government Area and are held in alignment, including changes resulting cadastral maintenance and upgrades.Initial Publication Date05/05/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)EPSG:4326WGS84 Equivalent ToGDA94Spatial 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.Information about the Feature Class and Domain Name descriptions for the NSW Administrative Boundaries Theme can be found in the NSW Cadastral Data Dictionary.Some of Spatial Services Datasets are designed to work together for example NSW Address Point and NSW Address String (table), NSW Property (Polygon) and NSW Property Lot (table) and NSW Lot (polygons). To do this you need to add a Spatial Join.A Spatial Join is a GIS operation that affixes data from one feature layer’s attribute table to another from a spatial perspective.To see how NSW Address, Property, Lot Geometry data and tables can be spatially joined, download the Data Model Document. Data CustodianDCS Spatial Services346 Panorama AveBathurst NSW 2795Point of ContactPlease contact us via the Spatial Services Customer HubData AggregatorDCS Spatial Services346 Panorama AveBathurst NSW 2795Data DistributorDCS Spatial Services346 Panorama AveBathurst NSW 2795Additional Supporting InformationData DictionariesData Model Document. TRIM Number

This theme delineates Urban Growth Boundaries (UGBs) in the state of Oregon. Oregon land use laws limit development outside of urban growth boundaries. The line work was created by various sources including the Oregon Department of Land Conservation and Development (DLCD), the Oregon Department of Transportation (ODOT), Metro Regional Council of Governments (Metro), county and city GIS departments, and the Oregon Department of Administrative Services - Geospatial Enterprise Office (DAS-GEO).

This data layer is an element of the Oregon GIS Framework. This theme delineates urban growth boundaries (UGBs) in the state of Oregon. The line work was created by various sources including the Oregon Department of Land Conservation and Development (DLCD), the Oregon Department of Transportation (ODOT), Metro Regional Council of Governments (Metro), county and city GIS departments, and the Oregon Department of Administrative Services - Geospatial Enterprise Office (DAS-GEO). UGB areas consist of unincorporated lands surrounding a city that show where the city plans to grow over the next 20 years. When a city needs to develop more residential, commercial, industrial, or public land, it annexes the needed area from its UGB. If a city runs out of needed land within the UGB, it can expand its UGB. Original UGBs were established under the Oregon Statewide Planning Goals in 1973 by the Oregon State Legislature (Senate Bill 100). Goal 14 of the statewide planning program is, "To provide for an orderly and efficient transition from rural to urban land use, to accommodate urban population and urban employment inside urban growth boundaries, to ensure efficient use of land, and to provide for livable communities." The process and requirements for designating and amending UGBs are in Oregon Administrative Rules, Chapter 660, Division 24 (OAR 660-024). Designating or amending a UGB requires a public process, as required by Planning Goal 1, followed by approval by both the city and county elected officials and acknowledgement by the DLCD. This process includes the city submitting a Post Acknowledgement Plan Amendment (PAPA) to DLCD to review for consistency with Goal 14. The PAPA submittal includes GIS files that delineate the changes to the UGB. DLCD aggregates the local GIS layers into the statewide UGB layer. UGB line work and attributes are verified with the city PAPA submittals entered in DLCD’s tabular database to ensure that all UGB updates reported to DLCD have been included in this dataset. UGBs that are currently in the appeal process at the time of publication of this layer are not included. The effDate attribute indicates the year in which the UGB amendment was acknowledged by DLCD. In 2022, DLCD acknowledged amendments to the following UGBs: Central Point, Dayton, Phoenix, and Turner. Corrections were also made to the Astoria and Condon UGBs to reflect the current acknowledged boundary.

Polygon features that represent the political boundaries of Metropolitan Planning Organizations (MPO) that exist in Maryland and for which the Maryland Department of Transportation (MDOT) is a member. In several instances, these MPO boundaries extend beyond Maryland’s borders into neighboring states as well as the District of Columbia. MPO Boundaries’ data includes information on each boundary's name, geographic location, and the total size / extent of each area. MPO Boundaries data was intended to be used for planning purposes within governments at the National and State level. Maryland's MPO Boundaries data is a sub-set of the U.S. Department of Transportation (USDOT) Office of the Assistant Secretary for Research and Technology's Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). A metropolitan planning organization (MPO) is a federally-mandated and federally-funded transportation policy-making organization that is made up of representatives from local governments and governmental transportation authorities. Federal law requires the formation of an MPO for any urbanized area (UZA) with a population greater than 50,000. Federal funding for transportation projects and programs are channeled through this planning process. Congress created MPOs to ensure that existing and future expenditures of federal funds for transportation projects and programs are based on a continuing, cooperative, and comprehensive (“3‑C”) planning process. MPOs are charged with developing a 20-year long-range transportation plan (LRTP) and a short-term (usually 2-6 years) program called the transportation improvement program (TIP) for each of their respective regions. The seven MPOs of which Maryland jurisdictions and agencies are members are listed below. The Maryland member jurisdictions are listed under each MPO (note that some MPOs cover multi-State regions). The Maryland Department of Transportation is a member of each of the MPOs listed. Maryland's MPOs are as follows: National Capital Region Transportation Planning Board (TPB), Baltimore Regional Transportation Board (BRTB), Cumberland Area Metropolitan Planning Organization (CAMPO), Hagerstown/Eastern Panhandle Metropolitan Planning Organization (HEPMPO), Wilmington Area Planning Council (WILMAPCO), Salisbury/Wicomico Metropolitan Planning Organization (S/WMPO), and Calvert-St. Mary’s Metropolitan Planning Organization (C-SMMPO). Maryland's MPO Boundaries data is owned and maintained by the Transportation Secretary's Office (TSO) of the Maryland Department of Transportation (MDOT). Being a subset of the USDOT's NTAD, an annual update of Maryland's MPO Boundaries data is performed by TSO in close coordination with each MPO, the Maryland Department of Transportation State Highway Administration (MDOT SHA) and the Federal Highway Administration (FHWA). MPO Boundaries data is a strategic resource for the USDOT, FHWA, MDOT, as well as many other National, State, and local government agencies. Maryland's MPO Boundaries data is updated on an annual basis. For additional MPO information, contact MDOT's Office of Planning and Capital Programming (MDOTGIS@mdot.state.md.us) For additional data information, contact the MDOT SHA Geospatial Technologies Team (GIS@sha.state.md.us)

National Levee Database This feature layer, utilizing National Geospatial Data Asset (NGDA) data from the U.S. Army Corps of Engineers (USACE), displays levees within the United States. Per USACE, “The National Levee Database captures all known levees in the United States. It provides users with the ability to search for specific data about levees and serves as a national resource to support awareness and preparedness around flooding. The USACE is responsible for maintaining the National Levee Database and works in partnership with the Federal Emergency Management Agency (FEMA), and in close collaboration with other federal, state, and local governments and entities responsible for levees to obtain and share accurate and complete information.” Leveed area in Morrisville, PennsylvaniaData downloaded: 9/22/2025Data source: NLD/PublicNGDAID: 161 (National Levee Database)OGC API Features Link: (National Levee Database - OGC Features) copy this link to embed it in OGC Compliant viewersFor more information, please visit: National Levee DatabaseSupport documentation: NLD Data DictionaryFor feedback please contact: Esri_US_Federal_Data@esri.com NGDA Data Set This data set is part of the NGDA Water - Inland Theme Community. Per the Federal Geospatial Data Committee (FGDC), Water - Inland is defined as the “interior hydrologic features and characteristics, including classification, measurements, location, and extent. Includes aquifers, watersheds, wetlands, navigation, water quality, water quantity, and groundwater information.” For other NGDA Content: Esri Federal Datasets

A cooperative effort of the Governor’s Office of Administration and Pennsylvania State University Pennsylvania Spatial Data Access (PASDA) is Pennsylvania’s official public access open geospatial data portal. PASDA was developed in 1997 and has severed as the Commonwealth’s geospatial data portal for over 25 years; it is Pennsylvania’s node on the National Spatial Data Infrastructure and is integrated with the National State Geographic Information Council GIS Inventory. Data on PASDA is free to all users and is provided by federal, state local and regional governments, non-profit organizations and academic institutions.

Pursuant to Section 7-100l of the Connecticut General Statutes, each municipality is required to transmit a digital parcel file and an accompanying assessor’s database file (known as a CAMA report), to its respective regional council of governments (COG) by May 1 annually. The dataset has combined the Parcels and Computer-Assisted Mass Appraisal (CAMA) data for 2025 into a single dataset. This dataset is designed to make it easier for stakeholders and the GIS community to use and access the information as a geospatial dataset. Included in this dataset are geometries for all 169 municipalities and attribution from the CAMA data for all but one municipality. These data were gathered from the CT municipalities by the COGs and then submitted to CT OPM. This dataset was created on September 2025 from data collected in 2024-2025. Data was processed using Python scripts and ArcGIS Pro for standardization and integration of the data. To learn more about Parcel and CAMA in CT visit our Parcels Page in the Geodata Portal.Coordinate system: This dataset is provided in NAD 83 Connecticut State Plane (2011) (EPSG 2234) projection as it was for 2024. Prior versions were provided at WGS 1984 Web Mercator Auxiliary Sphere (EPSG 3857). Ownership Suppression: The updated dataset includes parcel data for all towns across the state, with some towns featuring fully suppressed ownership information. In these instances, the owner’s name was replaced with the label "Current Owner," the co-owner’s name will be listed as "Current Co-Owner," and the mailing address will appear as the property address itself. For towns with fully suppressed ownership data, please note that no "Suppression" field was included in the submission to confirm these details and this labeling approach was implemented as the solution.New Data Fields:The new dataset introduces the “Property Zip” and “Mailing Zip” fields, which will display the zip codes for the owner and property.Service URL:In 2024, we implemented a stable URL to maintain public access to the most up-to-date data layer. Users are strongly encouraged to transition to the new service as soon as possible to ensure uninterrupted workflows. This URL will remain persistent, providing long-term stability for your applications and integrations. Once you’ve transitioned to the new service, no further URL changes will be necessary.<span style='font-size:1

Notice - Replacement of the English and French Web services (WMS and ESRI REST) with a bilingual one. The NRN product is distributed in the form of thirteen provincial or territorial datasets and consists of two linear entities (Road Segment and Ferry Connection Segment) and three punctual entities (Junction, Blocked Passage, Toll Point) with which is associated a series of descriptive attributes such as, among others: First House Number, Last House Number, Street Name Body, Place Name, Functional Road Class, Pavement Status, Number Of Lanes, Structure Type, Route Number, Route Name, Exit Number. The development of the NRN was realized by means of individual meetings and national workshops with interested data providers from the federal, provincial, territorial and municipal governments. In 2005, the NRN edition 2.0 was alternately adopted by members from the Inter-Agency Committee on Geomatics (IACG) and the Canadian Council on Geomatics (CCOG). The NRN content largely conforms to the ISO 14825 from ISO/TC 204.

Coordinate system Update:Notably, this dataset will be provided in NAD 83 Connecticut State Plane (2011) (EPSG 2234) projection, instead of WGS 1984 Web Mercator Auxiliary Sphere (EPSG 3857) which is the coordinate system of the 2023 dataset and will remain in Connecticut State Plane moving forward.Ownership Suppression and Data Access:The updated dataset now includes parcel data for all towns across the state, with some towns featuring fully suppressed ownership information. In these instances, the owner’s name will be replaced with the label "Current Owner," the co-owner’s name will be listed as "Current Co-Owner," and the mailing address will appear as the property address itself. For towns with suppressed ownership data, users should be aware that there was no "Suppression" field in the submission to verify specific details. This measure was implemented this year to help verify compliance with Suppression.New Data Fields:The new dataset introduces the "Land Acres" field, which will display the total acreage for each parcel. This additional field allows for more detailed analysis and better supports planning, zoning, and property valuation tasks. An important new addition is the FIPS code field, which provides the Federal Information Processing Standards (FIPS) code for each parcel’s corresponding block. This allows users to easily identify which block the parcel is in.Updated Service URL:The new parcel service URL includes all the updates mentioned above, such as the improved coordinate system, new data fields, and additional geospatial information. Users are strongly encouraged to transition to the new service as soon as possible to ensure that their workflows remain uninterrupted. The URL for this service will remain persistent moving forward. Once you have transitioned to the new service, the URL will remain constant, ensuring long term stability.For a limited time, the old service will continue to be available, but it will eventually be retired. Users should plan to switch to the new service well before this cutoff to avoid any disruptions in data access.The dataset has combined the Parcels and Computer-Assisted Mass Appraisal (CAMA) data for 2024 into a single dataset. This dataset is designed to make it easier for stakeholders and the GIS community to use and access the information as a geospatial dataset. Included in this dataset are geometries for all 169 municipalities and attribution from the CAMA data for all but one municipality. Pursuant to Section 7-100l of the Connecticut General Statutes, each municipality is required to transmit a digital parcel file and an accompanying assessor’s database file (known as a CAMA report), to its respective regional council of governments (COG) by May 1 annually. These data were gathered from the CT municipalities by the COGs and then submitted to CT OPM. This dataset was created on 10/31/2024 from data collected in 2023-2024. Data was processed using Python scripts and ArcGIS Pro, ensuring standardization and integration of the data.CAMA Notes:The CAMA underwent several steps to standardize and consolidate the information. Python scripts were used to concatenate fields and create a unique identifier for each entry. The resulting dataset contains 1,353,595 entries and information on property assessments and other relevant attributes.CAMA was provided by the towns.Spatial Data Notes:Data processing involved merging the parcels from different municipalities using ArcGIS Pro and Python. The resulting dataset contains 1,290,196 parcels.No alteration has been made to the spatial geometry of the data.Fields that are associated with CAMA data were provided by towns.The data fields that have information from the CAMA were sourced from the towns’ CAMA data.If no field for the parcels was provided for linking back to the CAMA by the town a new field within the original data was selected if it had a match rate above 50%, that joined back to the CAMA.Linking fields were renamed to "Link".All linking fields had a census town code added to the beginning of the value to create a unique identifier per town.Any field that was not town name, Location, Editor, Edit Date, or a field associated back to the CAMA, was not used in the creation of this Dataset.Only the fields related to town name, location, editor, edit date, and link fields associated with the towns’ CAMA were included in the creation of this dataset. Any other field provided in the original data was deleted or not used.Field names for town (Muni, Municipality) were renamed to "Town Name".The attributes included in the data: Town Name OwnerCo-OwnerLinkEditorEdit DateCollection year – year the parcels were submittedLocationMailing AddressMailing CityMailing StateAssessed TotalAssessed LandAssessed BuildingPre-Year Assessed Total Appraised LandAppraised BuildingAppraised OutbuildingConditionModelValuationZoneState UseState Use DescriptionLand Acre Living AreaEffective AreaTotal roomsNumber of bedroomsNumber of BathsNumber of Half-BathsSale PriceSale DateQualifiedOccupancyPrior Sale PricePrior Sale DatePrior Book and PagePlanning RegionFIPS Code *Please note that not all parcels have a link to a CAMA entry.*If any discrepancies are discovered within the data, whether pertaining to geographical inaccuracies or attribute inaccuracy, please directly contact the respective municipalities to request any necessary amendmentsAdditional information about the specifics of data availability and compliance will be coming soon.If you need a WFS service for use in specific applications : Please Click Here

The USGS Hydrography Community Calls are a recurring series of virtual meetings designed to promote collaboration and engagement among stakeholders in the hydrography and geospatial communities. These calls provide an open platform for sharing updates on the 3D Hydrography Program (3DHP), discussing recent developments in elevation-derived hydrography (EDH), and exploring how the program aligns with the 3D National Topography Model (3DNTM). Each session includes presentations, technical discussions, and Q&A opportunities, allowing participants to exchange knowledge and ideas effectively.These calls attract a diverse audience, including federal agencies, state and local governments, academic researchers, and private sector partners. Topics typically include updates on hydrography standards, integration of 3DHP data with other geospatial frameworks, and strategies for improving data acquisition and usability. By fostering an inclusive dialogue, the community calls help to identify challenges, refine workflows, and align stakeholders on common goals, ultimately advancing the quality and application of hydrography data.In addition to sharing program updates, the Hydrography Community Calls are a venue for exploring future applications of 3DHP data, such as climate adaptation, disaster management, and infrastructure planning. They also highlight success stories and best practices, showcasing how hydrography data is being used to tackle real-world challenges. By connecting professionals and building a shared understanding of hydrography innovations, these calls play a vital role in shaping the future of water resource management and geospatial science.