Quick question about the Google Maps API

Hi,

Not really a WA product question, but more one about the Google Maps API.

I have a map that is dynamically populated with up to 10 UK addresses.

I am finding that results can vary - from just 1 pin appearing, to the full 10. The postcodes that are missing are found if I go to the Google Maps site directly.

I am asking the API to find the address only by postcode, so I guess my first question is does the API need the full address, or should the post code be sufficient for a rough marker. As the data is input by many different users sometimes it can leave a bit to be desired, but I know that the post code field will always be populated.

Secondly, is the API the same data as Google Maps itself? If not this might explain why some addresses aren't showing.

Cheers
Ian

The MAP API and maps.google.com use separate geocoding services. The Geocoding service that is used by the MAP API is notorious for having difficulties with European post codes.

because of this, our code will first try to resolve the address using the full address provided. if that fails, it will try again using the address without the post code.

you will get much better results using a full address than using only the post code. especially with European addresses.

Thanks Jason, that does help quiet a lot!

Cheers
Ian

you're welcome.

Hi

It appears that Google has updated it's api and how you get a key.
After being issued a key I step thru the process.
I'm getting an error that the key won't work with my version.

Will you be offering an update?

in the google api console, you need to enable the Google Maps API V2

see this page for details:
introduction.html#Obtaining_Key

"Click the Services link from the left-hand menu, then activate the Google Maps API v2 service."

The Pro maps for google extension will not be updated to the newer V3 API. We will no longer be updating the stand alone extension except to fix bugs.

The Pro Maps extension is now part of the Design Extender

in Design extender the PRo maps have been upgraded to use the V3 api. The V2 api in the stand alone extension will continue to work as long as you enable it in the API console.

If I understand the previous post, ProMaps for Google, a $40 extension, is no longer a stand alone and that it no longer provides functionality for the latest V3 Google? However, it will work with V2 which is available but no longer supported by Google. On the other hand, for $400, ProMaps will integrate the latest Google maps. I have no problem upgrading my purchases, but $40 to $400 seems a tad excessive. What am I missing here, I mean, besides the $40 I paid for the stand alone ProMaps for Google?

Since ProMaps is still for sale as a stand alone but does not allow user to take advantage of current Google API, may I suggest a name change that will more clearly reflect what the stand alone version does:
from ProMaps for Google to one of the following
BushLeagueMaps for Google
ProMaps for Google's Red-Headed-Step-Child Version
WebAsswipe NoMoMaps for Google.
Thanks,
Greg

yes, the stand alone version of Pro Maps for Google uses the V2 API.

"and that it no longer provides functionality for the latest V3 Google"

It never did provide the functionality for the latest V3 Google, that was never a feature of the Pro Maps for Google Extension.

Google Still offers the V2 API, and it still functions. By "no longer supported by Google" this means that google will not answer questions or offer assistance with problems in implementing the API. but then again, we've done that part for you.

You can continue to use the stand alone version of pro maps, it will just use the V2 API code.

In the pages that are created, you can force it to connect to the v3 api by changing the script tag:

<script type="text/javascript" src="http://maps.google.com/maps?file=api&v=2&key=ABQIAAAAvZMU4-DFRYtw1UlTj_zc6hT2yXp_ZAY8_ufC3CFXhHIE1NvwkxQcT1h-VA8wQL5JBdsM5JWeJpukvw">/*wagmp*/</script>

and editing the v attribute to v=3:

<script type="text/javascript" src="http://maps.google.com/maps?file=api&v=3&key=ABQIAAAAvZMU4-DFRYtw1UlTj_zc6hT2yXp_ZAY8_ufC3CFXhHIE1NvwkxQcT1h-VA8wQL5JBdsM5JWeJpukvw">/*wagmp*/</script>

I'm pretty sure you can also remove the key as it is now optional:

<script type="text/javascript" src="http://maps.google.com/maps?file=api&v=3">/*wagmp*/</script>

Using the older API does not mean that maps no longer function, it doesn't mean that maps created with the Stand Alone version or obsolete.


The upgrade to Design Extender gives much more than just upgrading the API that is used in pro maps, it also gives you 8 other tools.