The coordinates aren't always included. If they where they would be in the ll= parameter. Alought that is just where the view is centered and the user may of dragged the map, not the coordinates of the searched location.
Don't know what your goal is so can't suggest alternatives ...
Correct,
taken to extreme, the link could look like
http://maps.google.com/?q=London
Even using 'Link' to get the generated on link, gives:
http://maps.google.com/?q=London&ie=UTF8&hq=&hnear=Westminster,+London,+United+Kingdom&t=h&z=10
which still doesn't contain any coordinates.
>
> our use case is that:
> Users can enter google map links and our app shows them on a map.
You could get perhaps close, by geocoding the 'q' param, to lookup the
location via the geocode, (but taking into account, sll, hnear, hq
too)
But links can also be like
http://maps.google.com/maps?q=pizza+express,+Crawley
which the geocoder will not help with. The old local search API might,
but Terms prevent you using that.
(I have stripped these links down, to show the actual salient info.
But the APIs do not allow you to completely reconstruct the map
totally)
> let's say user #1 enters 3 google map links
> user #2 enters 5 google map links
> now i'd like to see them all on a map.
Alas I fear that may not be totally (legally) possible. It might be
possible, by straying into 'gray' areas of the terms. But dont really
want to discuss that here.