Skip to main content

What’s Next for the Google Maps API?

  • Chapter

Abstract

As this book goes to press, the Google Maps API is still very much in development; its feature set continues to change and improve. As the API increases in popularity and new methods are added, it’s often necessary to alter the way things work to enable new capabilities or provide more consistency throughout the API as a whole. Version 2, for example, split the GPoint class into separate GPoint and GLatLng classes, each with enhanced capabilities corresponding to their respective roles in handling pixel coordinates and geographical locations. In reversing the zoom levels, which may have been an annoyance to developers, Google allowed the maps to support as many detail levels as the satellite photography (or your custom overlay) warrants.

This is a preview of subscription content, log in via an institution.

Buying options

eBook
USD   24.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Rights and permissions

Reprints and permissions

Copyright information

© 2006 Michael Purvis, Jeffrey Sambells, and Cameron Turner

About this chapter

Cite this chapter

(2006). What’s Next for the Google Maps API?. In: Beginning Google Maps Applications with PHP and Ajax. Apress. https://doi.org/10.1007/978-1-4302-0224-0_8

Download citation

Publish with us

Policies and ethics