The Google Maps Data API is a web service that allows client applications to view, store, and update  map data for Google Maps, using the Google Data API. Data is stored in the form of individual features and collections of features.

Full pricing information has yet to be released, but the service is currently free for publically-visible data.

This article was previously published on GeoChalkboard, and has been reproduced here with permission. GeoChalkboard is published by Geospatial Training Services who provide a range of geospatial web courses.

With the ArcGIS Server Query Task you can perform attribute and spatial queries against data layers in a map service that has been exposed. You can also combine these query types to perform a combination attribute and spatial query. Some examples would perhaps be illustrative at this point. An attribute query might search for all land parcels with a valuation of greater than $100,000. A spatial query could be used to find all land parcels that intersect a 100 year floodplain, and a combination query might search for all land parcels with a valuation of greater than $100,000 and whose geometry intersects the 100 year floodplain. In this article we’ll take a look at the mechanics of querying data from a map service using the ArcGIS Server JavaScript API.

With the success of my earlier series on global equal area map projections (starting with this overview), I received a number of requests to produce a similar how-to article for polar maps. The first part of this article (published here) provides an overview of a number of different map projections commonly used for polar maps. Next week, I shall provide a guide to producing a working map of the northern hemisphere centered on the North Pole, using the Stereographic Projection.

The results of these articles can be seen in the new Polar Projections section of the Equal Area Maps website. Note that only one of these polar projections actually has the equal area property.