Spatially analyze healthcare data and extract fresh insights by transforming readable addresses to geographic coordinates with Spatialitics HIPAA-Compliant Health Geocoder._Communities around the world are taking strides in mitigating the threat that COVID-19 (coronavirus) poses. Geography and location analysis have a crucial role in better understanding this evolving pandemic.When you need help quickly, Esri can provide data, software, configurable applications, and technical support for your emergency GIS operations. Use GIS to rapidly access and visualize mission-critical information. Get the information you need quickly, in a way that’s easy to understand, to make better decisions during a crisis.Esri’s Disaster Response Program (DRP) assists with disasters worldwide as part of our corporate citizenship. We support response and relief efforts with GIS technology and expertise.More information...

Geoscape G-NAF is the geocoded address database for Australian businesses and governments. It’s the trusted source of geocoded address data for Australia with over 50 million contributed addresses distilled into 15.4 million G-NAF addresses. It is built and maintained by Geoscape Australia using independently examined and validated government data.

From 22 August 2022, Geoscape Australia is making G-NAF available in an additional simplified table format. G-NAF Core makes accessing geocoded addresses easier by utilising less technical effort.

G-NAF Core will be updated on a quarterly basis along with G-NAF.

Further information about contributors to G-NAF is available here.

With more than 15 million Australian physical address record, G-NAF is one of the most ubiquitous and powerful spatial datasets. The records include geocodes, which are latitude and longitude map coordinates. G-NAF does not contain personal information or details relating to individuals.

Updated versions of G-NAF are published on a quarterly basis. Previous versions are available here

Users have the option to download datasets with feature coordinates referencing either GDA94 or GDA2020 datums.

Changes in the February 2025 release

• Nationally, the February 2025 update of G-NAF shows an overall increase of 47,284 addresses (0.30%). The total number of addresses in G-NAF now stands at 15,706,733 of which 14,867,032 or 94.65% are principal.

• In the February 2025 release of G-NAF, over 300 addresses in Morra, Western Australia have been updated. About 150 addresses have changed locations and 160 properties now have street numbers instead of lot numbers. Some properties are still using lot-numbers, resulting in two addressees. This issue will be resolved in the May 2025 update of G-NAF.

• In the February release, Geoscape has re-classified geocode types of ‘Property Access Point Setback’ (PAPS) to be ‘Property Access Point’ (PAP) in South Australia where the geocode falls within a road casement as the geocode is not set back into a land parcel. This update has changed approximately 57,000 geocodes to PAP from their previous classification of PAPS, while there are some 14,000 PAPS geocodes that remain unchanged.

• Geoscape has moved product descriptions, guides and reports online to https://docs.geoscape.com.au.

Further information on G-NAF, including FAQs on the data, is available here or through Geoscape Australia’s network of partners. They provide a range of commercial products based on G-NAF, including software solutions, consultancy and support.

Additional information: On 1 October 2020, PSMA Australia Limited began trading as Geoscape Australia.

License Information

Use of the G-NAF downloaded from data.gov.au is subject to the End User Licence Agreement (EULA)

The EULA terms are based on the Creative Commons Attribution 4.0 International license (CC BY 4.0). However, an important restriction relating to the use of the open G-NAF for the sending of mail has been added.

The open G-NAF data must not be used for the generation of an address or the compilation of an address for the sending of mail unless the user has verified that each address to be used for the sending of mail is capable of receiving mail by reference to a secondary source of information. Further information on this use restriction is available here.

End users must only use the data in ways that are consistent with the Australian Privacy Principles issued under the Privacy Act 1988 (Cth).

Users must also note the following attribution requirements:

Preferred attribution for the Licensed Material:

_G-NAF © Geoscape Australia licensed by the Commonwealth of Australia under the _Open Geo-coded National Address File (G-NAF) End User Licence Agreement.

Preferred attribution for Adapted Material:

Incorporates or developed using G-NAF © Geoscape Australia licensed by the Commonwealth of Australia under the Open Geo-coded National Address File (G-NAF) End User Licence Agreement.

What to Expect When You Download G-NAF

G-NAF is a complex and large dataset (approximately 5GB unpacked), consisting of multiple tables that will need to be joined prior to use. The dataset is primarily designed for application developers and large-scale spatial integration. Users are advised to read the technical documentation, including product change notices and the individual product descriptions before downloading and using the product. A quick reference guide on unpacking the G-NAF is also available.

The new Oregon Address Geocoder is used to find the location coordinates for street addresses in the State of Oregon. This service is:

• Free
  
• Public
• Updated regularly
• Outputs location coordinates in Oregon Lambert, feet (SRID 2992)
• Uses over 2 million address points and 288,000 streets for reference

It is an ArcGIS multirole locator with two roles:

1. Point Address - Generally more accurate results from rooftop location points. Includes a Subaddress if a unit number is located.
   
2. Street Address - Less accurate results from an estimated distance along a street centerline address range if a Point Address was not found.

Instructions for using the Geocoder via ArcGIS Pro, ArcGIS Online, and REST Services are below:

ArcGIS Pro
Web Services
ArcGIS Online

Street centerline network for the City of Portland, Multnomah County, Clackamas County and Washington County developed for geocoding purposes. This dataset has a character (textual) street number field to better allow for locating addresses that have leading zeros (e.g., 0680 SW Bancroft St.). This dataset does not yet include the data fields and structure necessary for performing routing operations.-- Additional Information: Category: Transportation - Streets Purpose: Provides a dataset including all address segments to be used for geocoding (locating) addresses in the Portland Region. Includes the capability to search those addresses whose street number begins with a zero. Update Frequency: Weekly-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=52062

The dataset contains locations and attributes of above ground permits applied for and approved by the District Department of Transportation. They are newly occupied constructions and events. Examples include: moving truck, roll off debris container, moving storage container, construction staging area, mobile crane work zone, other reserved parking. The public space permit process is described on the DDOT website ddot.dc.gov.These data are shared via an automated process where addresses are batch matched (geocoded) to the District's Master Address Repository. Users may find that some data points will contain 0,0 for X,Y coordinates resulting in inconsistent spatial locations. Addresses for these data points could not be automatically geocoded and will need to be manually geocoded to 'best fit' locations in DC. Use the MAR Geocoder to help complete this.

The Postal Code Conversion File (PCCF) is a digital file which provides a correspondence between the Canada Post Corporation (CPC) six-character postal code and Statistics Canada's standard geographic areas for which census data and other statistics are produced. Through the link between postal codes and standard geographic areas, the PCCF permits the integration of data from various sources. The Single Link Indicator provides one best link for every postal code, as there are multiple records for many postal codes. To obtain the postal code conversion file or for questions, consult the DLI contact at your educational institution. The geographic coordinates attached to each postal code on the PCCF are commonly used to map the distribution of data for spatial analysis (e.g., clients, activities). The location information is a powerful tool for planning, or research purposes. In April 1983, the Geography Division released the first version of the PCCF, which linked postal codes to 1981 Census geographic areas and included geographic coordinates. Since then, the file has been updated on a regular basis to reflect changes. For this release of the PCCF, the vast majority of the postal codes are directly geocoded to 2006 Census geography. This improves precision of the file over the previous conversion process used to align postal code linkages to new geographic areas after each census. About 94% of the postal codes were linked to geographic areas using the new automated process. A quality indicator for the confidence of this linkage is available in the PCCF.

The dataset contains locations and attributes for above ground permits applied for and approved by the District Department of Transportation. They are existing occupied constructions and events. Examples include: moving trucks, roll off debris container, moving storage container, construction staging area, mobile crane work zone, other reserved parking. The public space permit process is described on the DDOT website https://ddot.dc.gov.These data are shared via an automated process where addresses are batch matched (geocoded) to the District's Master Address Repository. Users may find that some data points will contain 0,0 for X,Y coordinates resulting in inconsistent spatial locations. Addresses for these data points could not be automatically geocoded and will need to be manually geocoded to 'best fit' locations in DC. Use the MAR Geocoder to help complete this.

The Postal Code Conversion File (PCCF) is a digital file which provides a correspondence between the Canada Post Corporation (CPC) six-character postal code and Statistics Canada's standard geographic areas for which census data and other statistics are produced. Through the link between postal codes and standard geographic areas, the PCCF permits the integration of data from various sources. The Single Link Indicator provides one best link for every postal code, as there are multiple records for many postal codes. To obtain the postal code conversion file or for questions, consult the DLI contact at your educational institution. The geographic coordinates attached to each postal code on the PCCF are commonly used to map the distribution of data for spatial analysis (e.g., clients, activities). The location information is a powerful tool for planning, or research purposes. The geographic coordinates, which represent the standard geostatistical areas linked to each postal codeOM on the PCCF, are commonly used to map the distribution of data for spatial analysis (e.g., clients, activities). The location information is a powerful tool for marketing, planning, or research purposes. In April 1983, the Statistical Registers and Geography Division released the first version of the PCCF, which linked postal codesOM to 1981 Census geographic areas and included geographic coordinates. Since then, the file has been updated on a regular basis to reflect changes. For this release of the PCCF, the vast majority of the postal codesOM are directly geocoded to 2016 Census geography while others are linked via various conversion processes. A quality indicator for the confidence of this linkage is available in the PCCF.

The Address Points dataset shows Utah address points for all twenty-nine Utah counties. An address point represents a geographic location that has been assigned a US Postal Service (USPS) address by the local address authority (i.e., county or municipality) but does not necessarily receive mail. Address points may include several pieces of information about the structure or location that’s being mapped, such as:the full address (i.e., the USPS mailing address, if the address is for a physical location [rather than a PO box]);the landmark name; whether the location is a building;the type of unit;the city and ZIP code; unique code identifiers of the specific geographic location, including the Federal Information Processing Standard Publication (FIPS) county code and the US National Grid (USNG) spatial address;the address source; andthe date that the address point was loaded into the map layer.This dataset is mapping grade; it is a framework layer that receives regular updates. As with all our datasets, the Utah Geospatial Resource Center (UGRC) works to ensure the quality and accuracy of our data to the best of our abilities. Maintaining the dataset is now an ongoing effort between UGRC, counties, and municipalities. Specifically, UGRC works with each county or municipality’s Master Address List (MAL) authority to continually improve the address point data. Counties have been placed on an update schedule depending on the rate of new development and change within them. Populous counties, such as Weber, Davis, Salt Lake, Utah, and Washington, are more complete and are updated monthly, while rural or less populous counties may be updated quarterly or every six months.The information in the Address Points dataset was originally compiled by Utah counties and municipalities and was aggregated by UGRC for the MAL grant initiative in 2012. The purpose of this initiative was to make sure that all state entities were using the same verified, accurate county and municipal address information. Since 2012, more data has been added to the Address Points GIS data and is used for geocoding, 911 response, and analysis and planning purposes. The Address Point data is also used as reference data for the api.mapserv.utah.gov geocoding endpoint, and you can find the address points in many web mapping applications. This dataset is updated monthly and can also be found at: https://gis.utah.gov/data/location/address-data/.

The dataset contains locations and attributes of above ground permits applied for and approved by the District Department of Transportation. They are newly occupied constructions and events. Examples include: moving truck, roll off debris container, moving storage container, construction staging area, mobile crane work zone, other reserved parking. The public space permit process is described on the DDOT website ddot.dc.gov.These data are shared via an automated process where addresses are batch matched (geocoded) to the District's Master Address Repository. Users may find that some data points will contain 0,0 for X,Y coordinates resulting in inconsistent spatial locations. Addresses for these data points could not be automatically geocoded and will need to be manually geocoded to 'best fit' locations in DC. Use the MAR Geocoder to help complete this.

The dataset contains locations and attributes for above ground permits applied for and approved by the District Department of Transportation. They are existing occupied constructions and events. Examples include: moving trucks, roll off debris container, moving storage container, construction staging area, mobile crane work zone, other reserved parking. The public space permit process is described on the DDOT website https://ddot.dc.gov.These data are shared via an automated process where addresses are batch matched (geocoded) to the District's Master Address Repository. Users may find that some data points will contain 0,0 for X,Y coordinates resulting in inconsistent spatial locations. Addresses for these data points could not be automatically geocoded and will need to be manually geocoded to 'best fit' locations in DC. Use the MAR Geocoder to help complete this.

SummaryThis data set shows building permits for the Baltimore metropolitan region. The data goes back to 2000 and is updated approximately once every two months. Expanded building permit data can be found at https://www.baltometro.org/community/data-maps/building-permit-data.DescriptionThe permits include any permit that is use code 40-48 (most new residential), 60-65 (mixed use), or is greater than or equal to $50,000. Historically, BMC receives the permits from participating jurisdictions and geocodes them. In recent years, some jurisdictions have started geocoding their own permits. When this is the case, BMC incorporates the geocoded points as given, and does not include them in its own geocoding process.Expanded building permit data can be found at https://www.baltometro.org/community/data-maps/building-permit-data.Layers:BPDS_Residential_New_ConstructionBPDS_Residential_AlterationsBPDS_Non_Residential_New_ConstructionBPDS_ Non_Residential _AlterationsBPDS_Mixed_Use_New_ConstructionThere is no layer for Mixed Use alterations; alterations to Mixed Use always get classified as Residential or Non-Residential.Field NamesField Name (alias)Descriptionpermit_no (County Permit ID)Original permit ID provided by the jurisdictionissue_dt (Date Permit Was Issued)Date the permit was issuedxcoord (X Coordinate)Longitude, in NAD 1983 decimal degreesycoord (Y Coordinate)Latitude, in NAD 1983 decimal degreessite_addr (Site Address)Address of the constructionzipcode (Site Zipcode)Zipcode of the constructionoffice (Office Number)This number corresponds to a jurisdiction and is used for BMC administrative recordspmt_use (Permit Use)Permit use code. A list of the values can be found at https://gis.baltometro.org/Application/BPDS/docs/BPDS_Permit_Use_Codes.pdfpmt_type (Permit Type)Permit type code. A list of the values can be found at https://gis.baltometro.org/Application/BPDS/docs/BPDS_Permit_Use_Codes.pdfdevelopment_name (Development Name / Subdivision)Subdivision name, if providedunit_count (Number of Units)Number of units, if provided. Only found in residential recordstenure (Tenure)If provided, indicates whether building is expected to be for rent or for sale after construction is complete. 1=For Rent, 2=For Saleamount (Amount)Estimated cost of constructionpmt_cat (Permit Category)Simplified classification of the pmt_use and pmt_type fieldsdescrip (Description)Description of construction, if providedJurisdiction (Jurisdiction)Jurisdiction (a county or city)Update CycleThe data is updated approximately once every three months.User NoteOver the years, building permit points were geocoded using a variety of software and reference data. The Baltimore Metropolitan Council made every effort to ensure accurate geocoding however there may be inaccuracies or inconsistencies in how the points were placed. For best results, the Baltimore Metropolitan Council recommends aggregating the building permit points to a larger geography (ex. Census tract, zip code) when analyzing the data.Data Access InstructionsTo download the data or access it via API, visit https://gisdata.baltometro.org/.Technical ContactFor questions or comments, contact Erin Bolton, GIS Coordinator, at ebolton@baltometro.org or 410-732-0500.

description: This database contains locations of day care centers for 39 states which include the states of AZ, CA, , NV, NY, HI. This is a work in progress and data for remaining states will be added as they become available. The dataset only includes center based day care locations (including schools and religious institutes) and does not include home and family based day cares. All the data was acquired from respective states departments or their open source websites and then geocoded and converted into a spatial database, data for Washington D.C., Puerto Rico, Delaware and Louisiana was obtained in a GIS format. Information on the source of data for each state is available in the database itself. After geocoding the exact spatial location of each point is being verified using high resolution imagery and ancillary dataset and points are being moved to rooftops wherever possible, this is an ongoing work and points which have been physically verified have been labeled "Geocode", "Imagery", "Imagery with other" and "Unverified" depending on the methodology used to move the points. "Unverified" data points have still not being physically examined even though each of the points has been street geocoded as mentioned above. "Unverified" points for Puerto Rico, Washington DC and the states of Louisiana and Delaware may have better positional accuracy as data for these was obtained in GIS format. The "TYPE" attribute has not been populated yet, this will be populated once a common classification of day care for all states has been decided. The "O_TYPE" attribute contains the classification provided by individual states.; abstract: This database contains locations of day care centers for 39 states which include the states of AZ, CA, , NV, NY, HI. This is a work in progress and data for remaining states will be added as they become available. The dataset only includes center based day care locations (including schools and religious institutes) and does not include home and family based day cares. All the data was acquired from respective states departments or their open source websites and then geocoded and converted into a spatial database, data for Washington D.C., Puerto Rico, Delaware and Louisiana was obtained in a GIS format. Information on the source of data for each state is available in the database itself. After geocoding the exact spatial location of each point is being verified using high resolution imagery and ancillary dataset and points are being moved to rooftops wherever possible, this is an ongoing work and points which have been physically verified have been labeled "Geocode", "Imagery", "Imagery with other" and "Unverified" depending on the methodology used to move the points. "Unverified" data points have still not being physically examined even though each of the points has been street geocoded as mentioned above. "Unverified" points for Puerto Rico, Washington DC and the states of Louisiana and Delaware may have better positional accuracy as data for these was obtained in GIS format. The "TYPE" attribute has not been populated yet, this will be populated once a common classification of day care for all states has been decided. The "O_TYPE" attribute contains the classification provided by individual states.

The Property Location Service Plus- Public version (PLSplus-Public) is available to anyone and used to validate Queensland addresses and property descriptions. The service can also supply location data from a geocode. The service does not offer interstate (non Queensland) address validation information. The service is free of charge and requires authentication. The service versions available are Soap and REST. To use the PLSplus-Public soap service an application utilising a file called a "WSDL" (Web Service Description Language) is required. The WSDL is an XML-based language that is used for describing the functionality offered by a web service.The WSDL description provides a machine-readable description of how the service can be called, what parameters it expects, and what data structures it returns. The wsdl is available (with service guidelines) at the online resources link of this record. The wsdl contains the required endpoint for the service. PLSplus-Public now requires authentication to use it but the wsdl can be viewed at https://information.qld.gov.au/service/Addressing/ValidationService/PLSplusPublic/soap?wsdl

REST uri's and json examples for each function are available in the online resources zip file.

Support is only available to authenticated users. Instructions to apply for username and password are contained in the Information document found at the online resources link.PLSplus-Public provides the following operations:- ValidateAddress- ValidateLotPlan- ValidateCoordinates- ParseAddress and AutoCompleteAddressA successful validation of any of the first four operations (for Queensland locations) will also return other information, such as address, lot on plan, coordinates, address type and a matching confidence level for each request.The ValidateAddress operation validates the existence of a requested address. The address elements are in a rigid structure based around Australian Addressing Standards. If an identical address is found it returns all information about the address with a matching confidence. If no exact match is found it returns possible candidate addresses (up to 500) that best match the search criteria. A global confidence is given for all candidates. The requested elements of the address is parsed by the application.The ValidateAddress operation also geocodes the address and returns the geocoded coordinates.- The only field that is mandatory in the request is the street name or property name- Street Name can consist of a "street name" or "street name" and "street type",or "street name" and "street type" and "street suffix".- McCaul- McCaul Street- McCaul Street NorthThe ValidateLotPlan operation validates the existence of a Queensland "Lot on Plan" description and also returns the addresses and geocodes (if the parcel has them) for valid parcels. The requested Lot on Plan elements must be in a rigid structure to be parsed by the application. It should be noted that not all valid property descriptions have addresses and some parcels may have multiple addresses.The ValidateCoordinates operation provides a service to validate entered Latitude/Longitude coordinates within Queensland and return the closest addresses for the requested location. Search logic begins with a radius of of up to 250 metres. If no result is found the service locates the parcel or the coordinates and returns all addresses on that parcel. The coordinates elements is a rigid structure to be parsed by the application. Coordinates (in Degree.Decmial format ) with search box limited to - North Latitude: -9.0 West Longitude: 138.0- South Latitude: -29.5 East Longitude:155.0 - Coordinates will always be a negative Latitude and a positive Longitude.The AutoCompleteAddress operation returns up to 50 valid addresses based on the input of a text string. The longer the string typed the shorter the list of candidate addresses. Any address from returned candidates can be used as input to ParseAddress operation to return further information about the address. The ParseAddress operation provides a service to parse (into address components) and validate any single line Queensland address and return any associated addresses, lot on plans, geocode and confidence for a requested address. eg. Unit 1 25B Smith Street East Earlsville Qld

The dataset contains locations and attributes for above ground permits applied for and approved by the District Department of Transportation. They are existing occupied constructions and events. Examples include: moving trucks, roll off debris container, moving storage container, construction staging area, mobile crane work zone, other reserved parking. The public space permit process is described on the DDOT website https://ddot.dc.gov.These data are shared via an automated process where addresses are batch matched (geocoded) to the District's Master Address Repository. Users may find that some data points will contain 0,0 for X,Y coordinates resulting in inconsistent spatial locations. Addresses for these data points could not be automatically geocoded and will need to be manually geocoded to 'best fit' locations in DC. Use the MAR Geocoder to help complete this.

The Property Location Service Plus- Public version (PLSplus-Public) is available to anyone and used to validate Queensland addresses and property descriptions. The service can also supply location data from a geocode. The service does not offer interstate (non Queensland) address validation information. The service is free of charge and requires authentication. The service versions available are Soap and REST. To use the PLSplus-Public soap service an application utilising a file called a "WSDL" (Web Service Description Language) is required. The WSDL is an XML-based language that is used for describing the functionality offered by a web service.The WSDL description provides a machine-readable description of how the service can be called, what parameters it expects, and what data structures it returns. The wsdl is available (with service guidelines) at the online resources link of this record. The wsdl contains the required endpoint for the service. PLSplus-Public now requires authentication to use it but the wsdl can be viewed at https://information.qld.gov.au/service/Addressing/ValidationService/PLSplusPublic/soap?wsdl\r \r REST uri's and json examples for each function are available in the online resources zip file.\r \r Support is only available to authenticated users. Instructions to apply for username and password are contained in the Information document found at the online resources link.PLSplus-Public provides the following operations:- ValidateAddress- ValidateLotPlan- ValidateCoordinates- ParseAddress and AutoCompleteAddressA successful validation of any of the first four operations (for Queensland locations) will also return other information, such as address, lot on plan, coordinates, address type and a matching confidence level for each request.The ValidateAddress operation validates the existence of a requested address. The address elements are in a rigid structure based around Australian Addressing Standards. If an identical address is found it returns all information about the address with a matching confidence. If no exact match is found it returns possible candidate addresses (up to 500) that best match the search criteria. A global confidence is given for all candidates. The requested elements of the address is parsed by the application.The ValidateAddress operation also geocodes the address and returns the geocoded coordinates.- The only field that is mandatory in the request is the street name or property name- Street Name can consist of a "street name" or "street name" and "street type",or "street name" and "street type" and "street suffix".- McCaul- McCaul Street- McCaul Street NorthThe ValidateLotPlan operation validates the existence of a Queensland "Lot on Plan" description and also returns the addresses and geocodes (if the parcel has them) for valid parcels. The requested Lot on Plan elements must be in a rigid structure to be parsed by the application. It should be noted that not all valid property descriptions have addresses and some parcels may have multiple addresses.The ValidateCoordinates operation provides a service to validate entered Latitude/Longitude coordinates within Queensland and return the closest addresses for the requested location. Search logic begins with a radius of of up to 250 metres. If no result is found the service locates the parcel or the coordinates and returns all addresses on that parcel. The coordinates elements is a rigid structure to be parsed by the application. Coordinates (in Degree.Decmial format ) with search box limited to - North Latitude: -9.0 West Longitude: 138.0- South Latitude: -29.5 East Longitude:155.0 - Coordinates will always be a negative Latitude and a positive Longitude.The AutoCompleteAddress operation returns up to 50 valid addresses based on the input of a text string. The longer the string typed the shorter the list of candidate addresses. Any address from returned candidates can be used as input to ParseAddress operation to return further information about the address. The ParseAddress operation provides a service to parse (into address components) and validate any single line Queensland address and return any associated addresses, lot on plans, geocode and confidence for a requested address. eg. Unit 1 25B Smith Street East Earlsville Qld