What?
ABS has developed Google Maps prototypes to demonstrate Data Visualisation using Google Maps for Flash.
Why?
The concept of data visualisation is a natural fit with the ABS. By using a map to transform ABS data, one can quickly visualise a set of data as information which tells a story about a particular region. The aim is to enhance information dissemination in creative and profound ways for the future.
When?
Work is being done on the standardisation of data using SDMX and we are also finding ways to automate KML production. If you would like to work with us on this project, please contact us!
#1: Andrew
KML files are restricted by size and complexity ({ Link } ) and have scalability issues as shown in Prototype Two.
Why not use Oracle Spatial and use a Google Map as your Base Map ({ Link })
Or use GeoServer to serve your data on top of a Google Map, similar to this example ({ Link })
Or create an application using GeoExt that allows users to analyse the data on top of a Google Map
Or use the Open Geo Suite to provide multiple ways for users to view their data.
All of these methods avoid the need to produce KML files and will result in faster Google Maps.
#2: Raymond
I noticed that SLAs are being loaded by State and is quite slow despite the native vector graphic support provided by google maps for flash. Are performance hits seen going to be a expected when using large ABS data sets or multiple data sources on the same map? And is this issue one that can easily be resolved?
#3: Brendan
I think this is a great idea, but will be interested to know how you go with the KML component of this project.
After Building a similar thing as part of a DEEWR project we had to use a Mapserver to manage the theming and points etc. As KML was not scaleable enough for CD data. But you may have alternative solutions or use FME server???
#4: Michelle
Thank you for your thoughts and comments.
The roll-over information box is dependent on when the mouse pointer enters the polygon and which polygon it is in.
In Prototype One, the aim was to distinguish quick information by using a hover box. Upon clicking a polygon, an info window box (speech bubble) is displayed with more detailed information.
Instead we could use the info window box for the quick info in place of the hover boxes, or a custom window icon that distinguishes each polygon on mouse-over.
The hand was made unavailable as a result of the overlays and coding the mouse to change to a finger icon when hovering over the polygons. I am currently looking to reinstate the hand icon for panning.
The Google Maps prototype has been designed as a map template and uses KML files to overlay the polygons and other info (ie ABS data). It is possible to include other data sets on these maps.
#5: Craig
I've been interested in integrating CSP data into similar map-based views, out of our Facts and Figures publication and based on the electorate data we release publicly ({ Link }).
Will the ABS maps support the integration of additional non-ABS data sets such as these?
#6: Marcus
I have a number of thoughts...
1. I know this hasn't been considered yet but we have to be careful with the cartographic design (colours, line weights, fonts) so that there is a consistent ABS design for these visualisations
2. Control of where the roll-over information boxes could be an issue. It seems to be dependant on where the mouse pointer enters the polygon. Sometimes it is difficult to associated the box with the polygon.
3. It seems odd that the mouse pointer doesn't change to the hand when panning. This is probably because of the polygon object on top of the map. It might be worth seeing if using centroids can adjust this behaviour.