06 Jun Google Maps Engine
The Google Maps Engine API was released yesterday (here, here and here) making it available to all Google Maps Engine customers. Arc2Earth has been developing against the API for some time and our new version has direct support for connecting to your Map Engine account. The API is fast, well designed, secure and makes excellent use of open standards (GeoJson)
Maps Engine supports open OGC standards for 3rd party connections to your account. However, Arc2Earth uses the new API directly for better performance and ability to update feature data using ArcMap’s native editing tools. We do this by building a client side cache of your online tables. This cache can be created all at once (full download) or by panning/zooming in ArcMap (OnDemand caching) while your Maps Engine datasources are visible in the map. The cache is a local File Geodatabase that once populated, will display very quickly in ArcMap since you don’t have to wait for data to be returned on potentially latent internet connections. Sync will keep the cache up to date by continually making requests in the background while making comparisons to local data to quickly find new, updated and deleted records.
For editing, ArcMap users update the local File Geodatabase as they would with any other local data using the vast array of editing tools available from the ArcMap Editor toolbar. The edits are tracked and then applied to Maps Engine automatically, making them immediately available to other Maps Engine users. Here’s a quick video showing live editing from ArcMap
Another huge benefit is Arc2Earth’s ability to display Google Global Street and Imagery base maps directly in ArcMap. Now you georeference and edit your Maps Engine data directly over the same imagery that will be used online and from mobile clients.
Connecting to Maps Engine
Editing in ArcMap