This Africa Geocoding locator is a view of the World Geocoding Service constrained to search for places in the countries of Africa. The World Geocoding Service finds addresses and places in all supported countries around the world in a single geocoding service. The service can find point locations of addresses, cities, landmarks, business names, and other places. The output points can be visualized on a map, inserted as stops for a route, or loaded as input for a spatial analysis.The service is available as both a geosearch and geocoding service:Geosearch Services – The primary purpose of geosearch services is to locate a feature or point of interest and then have the map zoom to that location. The result might be displayed on the map, but the result is not stored in any way for later use. Requests of this type do not require a subscription or a credit fee. Geocoding Services – The primary purpose of geocoding services is to convert an address to an x,y coordinate and append the result to an existing record in a database. Mapping is not always involved, but placing the results on a map may be part of a workflow. Batch geocoding falls into this category. Geocoding requires a subscription. An ArcGIS Online subscription will provide you access to the World Geocoding service for batch geocoding.The service can be used to find address and places for many countries around the world. For detailed information on this service, including a data coverage map, visit the World Geocoding service documentation.

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. \r \r 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.\r \r G-NAF Core will be updated on a quarterly basis along with G-NAF.\r \r Further information about contributors to G-NAF is available here.\r \r 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.\r \r Updated versions of G-NAF are published on a quarterly basis. Previous versions are available here\r \r Users have the option to download datasets with feature coordinates referencing either GDA94 or GDA2020 datums.\r \r Changes in the February 2025 release\r \r * 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.\r \r * 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.\r \r * 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.\r \r \r * Geoscape has moved product descriptions, guides and reports online to https://docs.geoscape.com.au.\r \r 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.\r \r Additional information: On 1 October 2020, PSMA Australia Limited began trading as Geoscape Australia.\r \r

License Information\r

\r Use of the G-NAF downloaded from data.gov.au is subject to the End User Licence Agreement (EULA)\r \r 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. \r \r 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.\r \r End users must only use the data in ways that are consistent with the Australian Privacy Principles issued under the Privacy Act 1988 (Cth).\r \r Users must also note the following attribution requirements:\r \r Preferred attribution for the Licensed Material:\r \r

_G-NAF © Geoscape Australia licensed by the Commonwealth of Australia under the _Open Geo-coded National Address File (G-NAF) End User Licence Agreement.\r \r Preferred attribution for Adapted Material:\r \r 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.\r \r

What to Expect When You Download G-NAF\r

\r 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.\r \r

The address-matching process derives spatial data points from input tabular address data. This geocoding package is constructed using road centerline and address point data published by the NJ Office of Information Technology, Office of GIS (NJOGIS.) The geocoder is refreshed monthly using updates of those datasets.For additional support or to download a copy of the geocoding package please visit https://njgin.nj.gov/njgin/edata/geocoding.The geocoder includes a multirole locator that references comprehensive statewide address point and road centerline datasets. These datasets are maintained and published by NJOGIS in cooperation with county and municipal GIS agencies. The data have been reprocessed from the published releases to accommodate optimization of the locators. The published source data can be found here: Address Points - https://njgin.nj.gov/njgin/edata/addresses; Road Centerlines - https://njgin.nj.gov/njgin/edata/roads

The new Oregon Address Geocoder is used to find the location coordinates for street addresses in the State of Oregon. This service is:FreePublicUpdated regularlyOutputs location coordinates in Oregon Lambert, feet (SRID 2992)Uses over 2 million address points and 288,000 streets for referenceIt is an ArcGIS multirole locator with two roles:Point Address - Generally more accurate results from rooftop location points. Includes a Subaddress if a unit number is located.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 ProWeb ServicesArcGIS Online

This service allows direct geocoding (conversion of a postal address or place name into geographical coordinates) and reverse geocoding (conversion of geographical coordinates into postal address or place name). It is powered by the free Photon tool (see https://github.com/komoot/photon), powered by OpenStreetMap data relating to the former Rhône-Alpes region (see https://download.geofabrik.de/europe/france/rhone-alpes.html). The official documentation of Photon's search API is provided on GitHub, https://github.com/komoot/photon#search-api. The link to perform a query is as follows (replace the .. by the place to geocode): https://download.data.grandlyon.com/geocoding/photon/api?q=... Examples: https://download.data.grandlyon.com/geocoding/photon/api?q=lyon https://download.data.grandlyon.com/geocoding/photon/api?q=%22Rue%20garibaldi%22

This dataset serves as a lookup table to determine if environmental records exist in a Chicago Department of Public Health (CDPH) environmental dataset for a given address. Data fields requiring description are detailed below. MAPPED LOCATION: Contains the address, city, state and latitude/longitude coordinates of the facility. In instances where the facility address is a range, the lower number (the value in the “Street Number From” column) is used. For example, for the range address 1000-1005 S Wabash Ave, the Mapped Location would be 1000 S Wabash Ave. The latitude/longitude coordinate is determined through the Chicago Open Data Portal’s geocoding process. Addresses that fail to geocode are assigned the coordinates 41.88415000022252°, -87.63241000012124°.This coordinate is located approximately just south of the intersection of W Randolph and N LaSalle. COMPLAINTS: A ‘Y’ indicates that one or more records exist in the CDPH Environmental Complaints dataset. NESHAPS & DEMOLITON NOTICES: A ‘Y’ indicates that one or more records exist in the CDPH Asbestos and Demolition Notification dataset. ENFORCEMENT: A ‘Y’ indicates that one or more records exist in the CDPH Environmental Enforcement dataset. INSPECTIONS: A ‘Y’ indicates that one or more records exist in the CDPH Environmental Inspections dataset. PERMITS: A ‘Y’ indicates that one or more records exist in the CDPH Environmental Permits dataset. TANKS: A ‘Y’ indicates that one or more records exist in the CDPH Storage Tanks dataset. Each 'Y' is a clickable link that will download the corresponding records in CSV format.

Big “p” policy changes at the state and federal level are certainly important to health equity, such as eligibility for and generosity of Medicaid benefits. Medicaid expansion has significantly expanded the number of people who are eligible for Medicaid and the creation of the health insurance exchanges (Marketplace) under the Affordable Care Act created a very visible avenue through which people can learn that they are eligible. Although many applications are now submitted online, physical access to state, county, and tribal government Medicaid offices still plays a critical role in understanding eligibility, getting help in applying, and navigating required documentation for both initial enrollment and redetermination of eligibility. However, as more government functions have moved online, in-person office locations and/or staff may have been cut to reduce costs, and gentrification has shifted where minoritized, marginalized, and/or low-income populations live, it is unclear if this key local connection point between residents and Medicaid has been maintained. Our objective was to identify and geocode all Medicaid offices in the United States for pairing with other spatial data (e.g., demographics, Medicaid participation, health care use, health outcomes) to investigate policy-relevant research questions. Three coders identified Medicaid office addresses in all 50 states and the District of Columbia by searching state government websites (e.g., Department of Health and Human Services or analogous state agency) during late 2021 and early 2022 for the appropriate Medicaid agency and its office locations, which were then reviewed for accuracy by a fourth coder. Our corpus of Medicaid office addresses was then geocoded using the Census Geocoder from the US Census Bureau (https://geocoding.geo.census.gov/geocoder/) with unresolved addresses investigated and/or manually geocoded using Google Maps. The corpus was updated in August through December 2023 following the end of the COVID-19 public health emergency by a fifth coder as several states closed and/or combined offices during the pandemic. After deduplication (e.g., where multiple counties share a single office) and removal of mailing addresses (e.g., PO Boxes), our dataset includes 3,027 Medicaid office locations. 1 (December 19, 2023) – original version 2 (January 25, 2024) – added related publication (Data in Brief), corrected two records that were missing negative signs in longitude 3 (February 6, 2024) – corrected latitude and longitude for one office (1340 State Route 9, Lake George, NY 12845) 4 (March 4, 2024) – added one office for Vermont after contacting relevant state agency (280 State Road, Waterbury, VT 05671)

This dataset is an enrichment of the INSEE dataset (SIRENE database of enterprises and their establishments (SIREN, SIRET)) (https://www.data.gouv.fr/en/datasets/base-sirene-des-entreprises-et-de-leurs-etablissements-siren-siret/). This enriches the original base as follows: - Breakdown of the StockEstablishment file by geographical grid: departments and municipalities. Addition of a number of columns relating to the geolocation of establishments based on the most relevant proximity score between the address indicated in the SIRENE database and the National Address Database or the Points of Interest of Openstreetmap. Longitude field: longitude of the establishment Field "latitude": Latitude of establishment Field geo_score: Trust score returned by the addok geocoder (between 0 and 1, the higher the score, the more relevant the geocoding seems) Field geo_type: type of address found Field geo_address: wording of the address found Field geo_id: identifier of this address in the source database where it was found (BAN or POI) Field geo_line: which address line of the SIRENE database could be geocoded (G=geographical, D=declared, N=normalized) Field geo_l4: line 4 to standard AFNOR address Field geo_l5: line 5 to standard AFNOR address The processing allowing the production of this dataset is carried out by Etalab. It is largely inspired by the previous work of Christian Quest available here. This processing is based on the geocoder Addok. This dataset is used in the search engine of the business directory and in its API (https://api.gouv.fr/les-api/api-recherche-entreprises).

A Lightning talk on Geocoding overview and options.

The ArcGIS World Geocoding Service finds addresses and places in all supported countries around the world in a single geocoding service. The service can find point locations of addresses, cities, landmarks, business names, and other places. The output points can be visualized on a map, inserted as stops for a route, or loaded as input for a spatial analysis.The service is available as both a geosearch and geocoding service:Geosearch Services – The primary purpose of geosearch services is to locate a feature or point of interest and then have the map zoom to that location. The result might be displayed on the map, but the result is not stored in any way for later use. Requests of this type do not require a subscription or a credit fee. Geocoding Services – The primary purpose of geocoding services is to convert an address to an x,y coordinate and append the result to an existing record in a database. Mapping is not always involved, but placing the results on a map may be part of a workflow. Batch geocoding falls into this category. Geocoding requires a subscription. An ArcGIS Online Subscription, or ArcGIS Location Platform Subscription, will provide you access to the ArcGIS World Geocoding service for batch geocoding.The service can be used to find address and places for many countries around the world. For detailed information on this service, including a data coverage map, visit the ArcGIS World Geocoding service documentation.

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

This dataset contains intersections of named traffic lanes. It is intended to power a geocoder to facilitate the search for crossings, crossroads. It was extracted from OpenStreetMap data by a postgis query available at https://gist.github.com/cquest/c0a84e6757d15e66e6ae429e91a74a9e This data has been added to the addok geocoding instance available on demo.addok.xyz

Open Postcode Geo is a postcode dataset and API optimised for geocoding applications. You can use Open Postcode Geo to geocode a dataset, geocode user input, and therefore build a proximity search.

Data is derived from the ONS (Office for National Statistics) postcode database and is free to use, subject to including attributions to ONS, OS (Ordinance Survey) and Royal Mail.

Information is also provided on a range of topics, including education, health, crime, business, etc.

Postcodes can be entered at area, district, sector, and unit level - see Postcode map for the geographical relationship between these.

Postal codes are part of nearly every administrative and research data set, and postal code conversion using PCCF or PCCF+ and related tools is now the usual way of exploiting their rather impressive potential. The resulting small area geography and/or latitude-longitude coordinates have a wide variety of possible uses, even where individual measures of SES are also available on a data set. Familiarity with the methods (tools and techniques), as well as the strengths and limitations of dealing with postal coded data, will allow data service providers to help users to more meaningfully exploit their potential.

The Geocoded Disasters (GDIS) Dataset is a geocoded extension of a selection of natural disasters from the Centre for Research on the Epidemiology of Disasters' (CRED) Emergency Events Database (EM-DAT). The data set encompasses 39,953 locations for 9,924 disasters that occurred worldwide in the years 1960 to 2018. All floods, storms (typhoons, monsoons etc.), earthquakes, landslides, droughts, volcanic activity and extreme temperatures that were recorded in EM-DAT during these 58 years and could be geocoded are included in the data set. The highest spatial resolution in the data set corresponds to administrative level 3 (usually district/commune/village) in the Global Administrative Areas database (GADM, 2018). The vast majority of the locations are administrative level 1 (typically state/province/region).

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

Find UK addresses instantly online and be confident you're getting the most up-to-date information with our address API. Perform accurate geocoding and reverse geocoding with our secure, scalable, and resilient address look-up web service. Search by postcode, UPRN, full or partial address and ensure you get the right address first time. Keep your records accurate to provide effective citizen services. Our secure, scalable, and resilient address look-up web service, OS Places API lets you search the UK's most comprehensive online address database. With OS Places API, managing customer data is a breeze. Lightning-quick postcode and address search means your records are accurate and customer deliveries should always get to the right front door. When an incident happens, control room staff need to know which properties are closest. OS Places' GeoSearch tools give instant answers. This helps create the common operating picture that's vital for the emergency services.

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. Getting started guide To obtain the postal code conversion file or for questions, consult the DLI contact at your educational institution. New to the June 2022 version, a separate data file is available for retired postal codes. The retired file uses the same record layout as the PCCF file. The same syntax file can be used for both the PCCF data file and the retired data file. 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.

Updated July 2nd 2020 to adopt Pro 2.6 release and create Pro locators.This sample contains an ArcGIS Pro 2.6 Toolbox file containing five Spatial ETL Tools:ImportPSV2 - imports pipe separated source text files into a new (or existing, optionally to be overwritten) File Geodatabase.ImportStatePSV2 - the same as ImportPSV2 except includes a filter for a target state.MakeAllLocalityAliases - makes a city or locality alias table used in locator creation.MakeAddress2 - makes a point feature class ADDRESS with the schema similar to the ADDRESS_VIEW example in the PSMA documentation.MakeReferenceAddress - creates a point feature class REFERENCEADDRESS from the ADDRESS features, having expanded house number ranges and house number and subaddress details in suitable fields. This is the primary role data for the locator.The download also includes FME workbench FMW files (2020) for use in that product and ArcGIS Pro.You must re-source the Spatial ETL tools in the download toolbox to point to the FMW files in the download and you must re-path the data sources in each Spatial ETL tool to suit your project workspace.A model CreateGNAFLocator is in the download toolbox, use this to create your locator. A sample locator for the ACT is included.The sample locator and ones you create will support subaddress inputs, like flats and units.ImportPSV2 takes 19 hours to process 104M features on my machine. You might like to process a state at a time.If you add intermediate data to a map or leave an output geodatabase expanded in the Catalog pane you may get an error when writing output because of file locking. It is recommended you do not open an output workspace in Pro until app processing is complete.MakeAddress2 and MakeReferenceAddress take 4 hours to run for all Australia.The schema expected is as per February 2021, it may change each release, read the source documentation for change notices, this sample may not be maintained. The primary and foreign key fields according to PSMA's data model are indexed.G-NAF download site is: https://data.gov.au/dataset/geocoded-national-address-file-g-naf

QDGC tables delivered in geopackage file - - - - - - - - - - - - - - - - - - - - - - QDGC represents a way of making (almost) equal area squares covering a specific area to represent specific qualities of the area covered. The squares themselves are based on the degree squares covering earth. Around the equator we have 360 longitudinal lines , and from the north to the south pole we have 180 latitudinal lines. Together this gives us 64800 segments or tiles covering earth. Within each geopackage file you will find a number of tables with these names: -tbl_qdgc_01 -tbl_qdgc_02 -tbl_qdgc_03 -tbl_qdgc_04 -tbl_qdgc_05 -etc The attributes for each table are: qdgc Unique Quarter Degree Grid Cell reference string area_reference Country level_qdgc QDGC level cellsize degrees decimal degree for the longitudal and latitudal length of the cell lon_center Longitude center of the cell lat_center Latitudal center of the cell area_km2 Calculated area for the cell geom Geometry Metadata -------- Geodata GCS_WGS_1984 Datum: D_WGS_1984 Prime Meridian: 0 Areas are calculated with different versions of Albers Equal Area Conic using the PostGIS function st_area. For the African continent I have used Africa Albers Equal Area Conic which will look like this: - st_area(st_transform(geom, 102022))/1000000) Conditions ---------- Delivered to the user as-is. No guarantees. If you find errors, please tell me and I will try to fix it. Suggestions for improvements can be addressed to the github repository: https://github.com/ragnvald/qdgc Thankyou -------- The work has over the years been supported and received advice and moral support from many organisations and stakeholders. Here are some of them: - Tanzania Wildlife Research Institute - Dept of Biology, NTNU, Norway - Norwegian Environment Agency - Eivin Røskaft, Steven Prager, Howard Frederick, Julian Blanc, Honori Maliti, Paul Ramsey References ---------- * http://en.wikipedia.org/wiki/QDGC * http://www.mindland.com/wp/projects/quarter-degree-grid-cells/about-qdgc/ * http://en.wikipedia.org/wiki/Lambert_azimuthal_equal-area_projection * http://www.safe.com The decompressed file is around 11.8 GB.