The Geocoded National Address File (referred to as G-NAF) is Australia’s authoritative, geocoded address file. This has been made available as Open Data on data.gov.au as a series of PSV files.
Bruce Harold has provided some tools to help convert this raw data into an Esri Address Locator. I realised I had little experience building an Address Locator from scratch, so have been running through the process to better understand how they work. As a result, I have put together this wiki to help others who might want to build their own address locator from G-NAF.
Here is a link to the compiled Locator, but be aware that I will not be keeping this up to date with the quarterly updates made to the G-NAF dataset and also please read the disclaimer below.
LOCATOR LINK INCLUDING DATE CREATED
This has been a self-learning experience to better understand the G-NAF data along with building an Esri Address. I have not spent hours checking through the quality of the output. At the time of writing, this is just looking at G-NAF data, and does not incorporate other data sources such as placenames, business names, other PSMA admin boundaries, etc.
Therefore, use at your own risk, especially if you are thinking about using this within an enterprise workflow. Getting an address wrong can be huge mistake for some workflows.
If you want an Australian geocoder that has had significantly more effort and testing put against it, along with more regular updates, I would highly encourage you to look into the following:
- Map Data Services - provide an Esri Address Locator
- NAVIGATE - Provide an Esri Address Locator
- Esri Street Map Premium for Asia Pacific - Esri Address Locator based upon HERE data
Also worth pointing out that the ArcGIS Online World GeoCode Service includes G-NAF data, but will only get updates around once every year or so.
If others find these tools useful, I am hoping that we can make improvements to this project and build on it over time.
- Please fork and recontribute any improvements you make!
- Please feel free to raise issues and enhancements or areas in the Wiki that needed more explanation.
Longer term some goals I want to look at accomplishing include:
- Automating the process of downloading updates from data.gov.au and updating the address locator (and a geocode service published from the locator)
- Investigating using python instead of a reliance on the Data Interop extension.
- Including other open data layers to build a more robust composite locator (e.g. PSMA boundaries, Geonames, etc.)
-
Download Bruce's tools from ArcGIS Online
-
Download the latest PSMA GNAF PSV files
-
Make sure you have the Data Interop for ArcGIS Pro installed and licensed.
This initially caught me out as it is a different installer to the ArcGIS Desktop Data Interop installer)
- Create a new ArcGIS Pro Project, add a folder connection to where you downloaded the tools from #1
- Open the toolbox, and for each tool, right click and properties, and update the workspace path to match the FMW folder that is included in the download
- Save Project
- Open the ImportPSV2 tool
WARNING: This tool took around 10hrs to run for all of Australia. Overnight job.
- Enter path to the GNAF ZIP file containing the PSV files
- Create an output folder and point the Destination UnZIP folder to this output folder location
- Point the tool to a destination file Geodatabase. You can use the default geodatabase for your ArcGIS Pro project.
Did you encounter 'A fatal error has occurred' / 'Translation Failed'?
Do you have ArcGIS Server/Enterprise installed on your machine?
There appears to be a bug when trying to run some of the Data Interop tools on a machine that has ArcGIS Server installed. An issue with multiple versions of python clashing.
One Workaround is to either unintall ArcGIS Server or run all of the tools from a machine that does not have ArcGIS Server installed
Another Workaround is to open the tools from their workbench and running them from there. Steps outlined below.
This same process will apply for all of the Spatial ETL tools supplied in the tools provided by Bruce
- Right click the ImportPSV2 tool and hit Edit
- Run the tool from workbench (hit the execute button)
I found this was also a better approach to understand the progress of how the tools are running and get a better understanding of the data manipulation the tools are performning.
If you are running the tools in workbench, ensure you update the published parameters before clicking run.
Either way, running from either the tool within ArcGIS Pro, or from the Workbench - check that the tool runs succesfuly and you should end up with the following output in your destination geodatabase:
