I suppose there is some sort of Google event going on this week and what do you know, we’ve got some GoogleGeo news:
Google Maps API v3 – The new Google Maps API v3 enables support on mobile browsers (such as Mobile Safari), dropping the need for keys (hurray!), now MVC-based architecture (about time), default UI automatically supported (so you never have to worry about updating the UI), cleaned up namespaces (everything is now google.maps.* rather than gmap). So what does this mean? Take a look at the old v2 example.
And now v3.
I like the new look and for me it is much more logical than before (plus mobile browser support FTW!). Check out the documentationand the reference. This coupled with the Google Maps Data API really pushes the Google Maps WAY in front of Microsoft and others.
OpenGeo has released their OpenGeo Suite to the public. Most people already know about the part of OpenGeo Suite, so take a look at the Version Matrix with pricing and features and the big reason why you’d look at this suite.
The video from our Where 2.0 presentation is available. If you haven’t been following what the GNOCDC is doing down in New Orleans, this is a great introduction. You can download the presentation here.
Just like CSS for styling web pages, GSS is a specification for designing maps. Adapted for dynamic data sources, GSS can define changing geographic elements, display multiple datasets, and even respond to contextual tags like “condition:poor”.
Very tasty! Just look at this simple GSS and how you can render maps on the client.
If you’d like to have some beers, feel free to connect with me using the networking dashboard. I’m already planning on meeting a ton of folks who normally don’t roam in my “professional” GIS conference circuit. See you guys there!
One of the best new features of ArcGIS 9.3.1 is the Map Service Publishing toolbar in ArcMap. This tool helps you analyze your maps to see what is slowing the map down. No longer are you having to look for the needle in the haystack. You just activate the toolbar and hit analyze. Then ArcMap returns all the errors and warnings associated with your mxd.
The new Map Service Publishing toolbar in action.
If you double click on any of the “issues” it will take you to documentation explaining the problem and how to fix it.
ArcGIS Server documentation helps figure out how to fix problems.
One other feature about the toolbar which is a big help is the preview. You can preview any map on how it would be served in ArcGIS Server, from right inside ArcMap. You also get a timer to show how long it took to generate that request. This is of course helpful for the ArcGIS Server services, but can even be used to speed up ArcMap documents that are only going to be consumed on the desktop. If you’ve been working with a mxd that seems to be loading slowly, now you have the tools you need to debug why the map isn’t performing quickly enough.
The Preview ArcGIS Server window allows users to determine the speed at which their maps are rendering.
The toolbar also allows you to generate the Map Service Definition (.msd) files and even publish directly to ArcGIS Server from ArcMap (bypassing the need to go to ArcCatalog or the web manager).
The Map Service Publishing toolbar is really a great addition to the ESRI workflows, both Desktop and Server. Looking back at some of our existing map services we had authored with ArcGIS Server, I was amazed at how easy it was to discover the problems and then address them. Coupled with the new MSD files, ArcGIS Server is really a speed demon these days.
Remember TOPO! Pro for ArcGIS? Don’t bother using the Google if you don’t recall, because it is gone.
If you’ve invested tons of money in the state series then you’ll be happy to know that there is a tool that allows you to convert the TPQ files to JPEG with a world file. TPQ Converter allows you to use the USGS data on the State Series CDs by converting individual or all TPQs located in a directory to jpgs with a world file. Then you’ll be able to use the output with any GIS application you wish.
At my old company, we did have a most TOPO! states, but since I’ve moved to RSP, we’ve just used web services.