Sean Barnett

This post forms part of the ongoing #TagJob project.

For reasons discussed in this post, I have tentatively decided to roll my own minimal geospatial types and calculations.

This post forms part of the ongoing #TagJob project.

In the previous post I introduced two Geoscape datasets that have been made available on the Australian Government's data.gov.au website: National Roads and Administrative Boundaries. The datasets are distributed in two different formats, neither of which is optimal for my intended spatial processing model. A first task is then to transform the data to a common format, and one that has the right performance characteristics for the project.

This post forms part of the ongoing #TagJob project.

The project uses as reference data Geoscape Datasets for Australian roads and administrative boundaries. Over the years, I have worked with these datasets under commercial licence, but happily they are now available for public use under The Australian Government's Data and Digital Government Strategy. Let's take a look at them.

Over the past few months I have been doing some technical reading. Well, actually a lot of technical reading, perhaps compensating for having not focused on multiprocessing and performance for some years. And, guess what? The technical world has changed.