Google Maps vs Mapquest - google-maps

I figure I'd drop this question here.
I wrote a curl script that gets the longitude and latitude for an address using the google maps API.
Works great!
The problem I have is that when I check the coordinates that my script generated.... on Google Maps and Mapquest the maps show different locations on the same coordinates.
In this case the coordinates are : 41.461754, -74.443577
Give it a shot. You'll see what I mean.
has anyone else experienced this problem? any solutions?

I don't rely on mapquest. They have my home 1 block from it's correct location. They show my home in what is a vacant house 1 street west. Need contact info so can advise them of their error.

I compaired it with openstreetview the result is the same as in google maps. It seems that just mapquest does not know the streets near to your position. If you scroll out the streets seems to be the same, but I live on another continent so far I don't know that environment.

Related

Google Maps API returns zoomed out repeated view of the globe - possible incorrect coordinates?

I'm working on a project where I am showing 8,000+ lat/long coordinates on a Google Map. Works great.
Today I uploaded another 3,000+, and now the Google Map shows a world view of the globe, repeated horizontally, with a lot of gray space on top.
I've looked through the 3,000+ entries, and do not see any where alpha characters, missing lat/long values, etc - something obvious.
The only thing that I can think of is that a lat/long entry is incorrect, and thus the Google Map zoom breaks? Reviewing questions on SO show hacks such as setting minZoom or zoom levels - but I feel that isn't the right path to go across to solve this, since it was working before and something is happening with my new records. I've checked that no pins are on the map outside USA which may cause the entire world view to show.
I'm reaching out to the community to see if anyone smarter than me has a tip or suggestion to help edge case occurrences like this, and/or if my assumption of a wrong lat/long is breaking the Map?
One of your lat/long is incorrect. Instead of Google Maps API failing and alerting, it just breaks the map. I'd advise you to run your locations to confirm decimals exists per each record.

Why is google streetview not displaying image for some coordinates?

I am having an issue where some coordinates are providing correct streetview image while others are off by several lots. For example, the coordinates for 42.4025192834409,-83.1636018491871 in streetview bring me to the intersection nearby. If I enter those coordinates into google maps the pin location is correct but then I can't drag the streetview icon in that section. Is there anything we can do differently with our coordinates so that they go to correct location for streetview?
When I search for the address it works as you are seeking. I think this is the discrepancy you are experiencing:
https://developers.google.com/maps/documentation/streetview/intro
The Google Street View Image API will snap to the panorama photographed closest to this location. When an address text string is provided, the API may use a different camera location to better display the specified location. When a lat/lng is provided, the API searches a 50 meter radius for a photograph closest to this location.
You may want to try reverse geocoding.
Try again now.
https://maps.googleapis.com/maps/api/streetview?size=640x480&location=42.4025192834409,-83.16360184918&fov=90
When I read your question two days ago, it was actually getting the wrong panorama. I tried again today and it finally got the closest panorama to those coordinates. I guess it was an issue on Google's end.

Google autocomplete place API not suggesting few popular places

I am using https://maps.googleapis.com/maps/api/place/autocompete?key=MyKey&input=MySearchText api for auto place suggestion , but I am not getting few popular cities in response and the same place I can easily search on google map application. Can anyone please help me on this what I am doing wrong and what can be the reason google place api is not suggesting this location? I am searching for below location :
4 horner square london e1 6ew
Thanks,
When I search the '4 horner square london e1 6ew' with Geocoding API I can get this address.
https://maps.googleapis.com/maps/api/geocode/json?address=4%20horner%20square%20london%20e1%206ew&key=YOUR_API_KEY
The place ID is ChIJs2foBLQcdkgRHljoVNXS89g
The fact that this place doesn't appear in Place autocomplete is really weird. I also have ZERO_RESULTS:
https://maps.googleapis.com/maps/api/place/autocomplete/json?input=4%20horner%20square%20london%20e1%206ew&key=YOUR_API_KEY
I think you have to file an issue in the public issue tracker.

Mapbox or Google Maps. Is this possible?

I have a custom map from a client. They want to either use Mapbox or google maps to add markers to it. The problem is they've customized how the world map actually looks. It doesn't show on the map image attached, but they cut off Alaska, and want to show it directly under Texas as a floating state. They also want to show so other states in an odd order. To the right of Alaska they want Hawaii, Puerto Rico, US Virgin Islands.
Two issues here:
1) Can this be done? I can't find any information about cutting pieces of a map up by moving states around.
2) If I CAN do this, will the geocoding still work for the map? Cause now Alaska is way the heck down there.
As far as I know, yes to both of your issues.
Now, to answer your issues:
1) Can this be done? I can't find any information about cutting pieces of a map up by moving states around.
As discussed in Translate your project from Google to Mapbox, you have options to customize maps and features. Then, any customized project created in the Mapbox Editor or uploaded from Mapbox Studio Classic will have a Map ID. Use the Map ID when initializing the map to add it as the active layer.
2) If I CAN do this, will the geocoding still work for the map? Cause now Alaska is way the heck down there.
Yes, geocoding will still work. With Mapbox, L.mapbox.geocoder() will gladly geocode your addresses.
Please try going through the given documentation for more information and for sample codes. Hope that helps!

Google Maps Embed displaying incorrect address on directions

I have just added a very simple code snippet to a client's website using the Google Maps Embed API. This displays all of the correct details, but when you click on the "Directions" link, a different address is displayed. You can see the problem on the web page here, http://www.picturesbyrob.co.uk/contact-us/
Anyone seen a problem like this before? I'm not sure if there's an underlying issue with the data or with the application.
Any pointers gratefully received. Thanks.
It is because the coordinates that are passed in your direction request are https://maps.google.com/maps?ll=54.033922,-0.589114&z=7&t=m&hl=en-US&gl=US&mapclient=embed&daddr=Photographer%20in%20York%20118%20Middlecroft%20Drive%20Strensall%20York%2C%20North%20Yorkshire%20YO32%205YQ%2C%20United%20Kingdom#54.033922,-1.045047
Latitude : 54.033922
Longitude : -1.045047
Which is the address you are getting on the Google Maps when you click on the direction link.
THe coordinates for the address you are looking which is 118 Middlecroft Drive, Strensall, York, York YO32 5YQ, UK are
Latitude : 54.0338228
Longitude : -1.0447040000000243
Try putting this explicitly in your request instead of geocoding it!