If the stat that 20% of the world has access to the Internet is correct, then you can now share your GIS data with ~1.1 Billion people very quickly.
Yesterday, Google announced a number of amazing changes ranging from a new redesigned beta version of Google Earth to an updated version of the KML (2.1) language. So as not to repeat what many have already said, check out the recent posts at Ogleearth blog for great coverage. My intention here is to talk about just one aspect of the new changes, the ability to display KML files in Google Maps.
KML (Keyhole Markup Language) is an XML language that is used to encode geographic information (points, lines, polygons, images, models) for use with Google Earth. With the new changes in KML 2.1, this same information can be viewed in Google Maps. The interface between Google Maps and KML 2.1 could not be more simple! In the search bar of the maps.google.com window, simply type in the URL of the KML file you want to display and voila!
So you don’t have any KML files, but you want to publish your data in Google Maps. If you have ArcGIS, GIS data, and some sort of web space (I use Bluehost.com), it is fast and simple. By using one of two products, the KML Home Companion or Export to KML, both VB scripts for ArcGIS 8.X - 9.x, GIS data can be written to KML files in seconds. Later, I will discuss the limitations of this process.
Here is a quick example. First, I downloaded publicly available data from the Delaware State Historic Preservation office. The data set consisted of a point file for the National Register of Historic Places Listed Structures for all of Delaware and a Polygon file of National Register Listed Historic Districts. These data are in Delaware State Plane coordinate system, but both KML export routines will reproject on the fly as long as the data is attributed correctly. I took a subset of these files; Google Maps can only handle so much data, but I have not found what the threshold is yet.
By using the simple export tools (each does things slightly differently, you’ll see which works best for you) the KMLs are written and simply FTPed to my web server. The process honestly takes less than 30 seconds. From here, go to maps.google.com and cut/paste the URL of the file on your server and there you have it. Here is my quick example: http://www.gisarch.com/kml/NR_pnts1.kml and http://www.gisarch.com/kml/NR_dist2.kml (cut and paste links into search bar of Google Maps page, or use these links if you like skipping steps: points, polys). From here, you can also click the “link to this page” text and grab the URL that points directly to your new Google Maps (”Link to this page” example). Taking it a step further, take your new URL and stick it in www.tinyurl.com to shrink it and come back with http://www.tinyurl.com/fm8vl as your new Google Map URL. When exchanging data with those in the know, all you need to do is tell them to go to “fm8vl“. How cool is that? Maybe a small stretch, but hey, why not? (note: the Tinyurl trick worked most of the time, but failed here and there)
What if you want to see both data set? Hack the KML! Use a text editor (I like HTML-Kit) to cut and paste the geometry from one into the other and you can now see the NR points and Polygons in the same map (example: http://tinyurl.com/j2t2d). I had to trim the points to make the map load, but you get the point.
As you have seen, some of the features do not have the name attribute correct and the points symbols
differ. This is due to the differences between KML home companion and Export to KML. Export to KML plainly lets you set the field to have as the name for each feature, but for KML Home Companion, it is not as apparent. I will have to look a little further to find what I am missing. Also, Export to KML would changed some of the more complex and small polygons to points during the export, whereas KML home companion exported every poly with no complaints. The output text is not the same for each script, but they can be hacked together.
I know this is a pretty low tech and minor example of how this new feature can be used, but as far as I am concerned, it is an amazing step in opening the door to allowing more people to share geographic data. With a process as simple as this, open data, export, FTP, and view, we should see a whole new lot of Google Map creations coming through the door.
The experimentation continues!!!