IssueTracker

that way will be cool and user friendly.

"Add the ability to scroll using the mouse wheel, add it to default UI, and
let developers disable it."

that way will help user for zoom in & zoom out easier..

I need mouse wheel to operate zooming in and out.
I have wait for several weeks already.
                                develop from Beijing China

Mousewheel zooming please! :)

When an issue in this tracker changes status (like from Acknowledged->Fixed), you'll
receive an email saying so. We generally don't reveal timelines for feature requests.

Pamela, for being fair: this is not feature request. This is backward compatibility
issue.
I think this is the only one blocking issue for migrating from GMap API v2 to v3.

Is it ready yet?  This is a great feature you must include it!

Nianwei created an open-source scroll wheel zoom implementation, you may want to try it
out:
http://groups.google.com/group/google-maps-utility-library-
v3/browse_thread/thread/f421e075eb63d2ba

Really want to see this feature added onto V3 asap please....

Add it already :) Can't live without it.

It appears someone made a hack for it already. Seems to work fine for me.. but I'll
probably wait for the official release.

http://google-maps-utility-library-v3.googlecode.com/svn/trunk/scrollwheelzoom/examples/scrollwheelzoom.html

Please include this feature, it's an essential part of the UI.

Oh good! That is convenient.

However, if the whole page scrolls, it both zooms the map and scrolls the whole page at
the same time; it's a little distracting. On older versions of the API, it would only
zoom the map.

Or am I missing something?

Thanks Pamela! I'm having the same problem as Matthew though - in Chrome 2 and Firefox
3 the document scrolls when you zoom a map with the mouse wheel. It seems to work ok in
Internet Explorer 8 though.

Hey, my maps magically got scroll wheel support -- I didn't even touch my code. Talk
about convenient!

Well if you want scroll wheel support off, set "scrollwheel: false" in your map options.

This is the absolute worst user interface "feature" I've ever seen (with the possible
exception of blinking text... no, it's worse than blinking text!)

Now that it got included in the v3 api, and enabled by default, can someone please
come up with a way to DISABLE this monstrosity on ALL google map implementations at
all times (i.e. I DO NOT want the "Developer" to have ANY say in whether the SCROLL
wheel ZOOMS the map).

I'd rather not have to create my own map implementation for every website that embeds
google maps just to disable this horrid "option". Is there any way to disable it by
default?

Not that you deserve much help with that kind of attitude jaotto, but yes, you can
disable it.  If you would have bothered to read the thread or even glance up at the
comment just above yours you would see that "scrollwheel: false" in the map options
disables.

[Comment deleted]

or, jaotto, you could write a userscript to make gmaps behave just as you wish on any
page and share the link here instead of giving an attitude.

Love the troll.

It's not a _scroll_ wheel, it's _mouse_ wheel. Even though it's typically used for
scrolling the page, there is not much reason why NOT use it for more appropriate
actions, e.g. zooming the full-page map.

When there are reasons — it's messing up with the page navigation too much, or
something — the designer can decide whether it's worth enabling/disabling this
feature.

But I guess the more general issue here is that it's too hard and ugly to zoom the
map _without_ using the wheel at all.

Great shopping websites list:

http://www.handbagshopping.org   handbags on sale  
http://www.sunglassesshopping.org   carrera sunglasses  
http://www.mbtshoesshopping.com   cheap mbt shoes  
http://www.christianlouboutinonline.net   christian louboutin  
http://www.ghdstraightenerssale.com   ghd straighteners cheap  
http://www.tiffanyjewelleryshop.org   cheap tiffany  
http://www.shoppinglouisvuitton.org   cheap louis vuitton  
http://www.chanelbagonline.net   chanel bag  
http://www.maccosmeticsshop.org   mac cosmetics
http://www.christianlouboutinshopping.org   christian louboutin boots
http://www.guccigucci.org                    gucci outlet  

UPDATE: rollout is about 70% complete globally, we expect it to be 100% within the hour.

Out of curiosity, why couldn't you guys roll-back to a working-snapshot in these past 4-days?  Also when can we expect Reference ID to be fully removed/deprecated?  Using Reference did not run into this issue.

I'm wondering if this is the same issue we have started seeing in the last couple days where a business has verified and was showing up using the Places API but now we get ZERO RESULTS when searching for them.  For example this business detail exists:  https://maps.googleapis.com/maps/api/place/details/json?placeid=ChIJrdr_tigG3IARYRXNiLaZb5k

But that business cannot be found using the near by search with keyword equal to the business name after the weekend:

https://maps.googleapis.com/maps/api/place/nearbysearch/

Is this fixed as well?

Many of our users have stored (in our database) the Place IDs of certain locations. I assume the broken Place IDs will never be rerouted to the corrected Place IDs? Is there any way to cross-reference / convert them?

#37 please file a new bug, this one was never related to Nearby Search.

#38 Yes. No. I'm afraid those Place IDs will have to be discarded, users would have to repeat their searches to find the new Place IDs. These are expected to remain valid in the long term.

This changed several place ids for Cities being returned by google.maps.places.AutocompleteService();. However, google.maps.places.Autocomplete() still returns the short ids.

For instance Paris, France is now ChIJD7fiBh9u5kcRYJSMaMOCCwSaBg1QYXJpcywgRnJhbmNl instead of ChIJD7fiBh9u5kcRYJSMaMOCCwQ. Other google maps APIs still return the short id. Why was this changed and which should we be using?

#43 There's a difference because the long-ish place ids are only returned by Place Autocomplete.

google.maps.places.AutocompleteService directly returns results from Place Autocomplete.

google.maps.places.Autocomplete.getPlace returns the result of a Place Details lookup on the currently selected input, so it doesn't return the long-ish place id.

You should be able to use either place id with all the Maps APIs that accept place ids. However, if the place was affected by the original issue, only Place Details will be able to resolve the place [for now].

This is killing my taxi business!

Just wanted to let you know there were issues with UBER and LYFT not able to select an address because of your place-id implementation.  Awesome, great job guys!

[Comment deleted]

It seems all the `place_id`s being returned by the `Autocomplete` service can now be used in the `Geocoder` service in addition to `Place Details` service. I would really appreciate a response from Google whether we can continue to rely on `Geocoder`, or if we do need to switch to using `Place Details`. Thanks.

Was this issue addressed only wiht US addresses, or was this addressed Globally? I've been testing with an address, "34 Aldershot Road, Guildford, GU2 8AF, United Kingdom", and this API is still dropping the street number aspect of the address.

I feel that might be another issue tracked elsewhere or reportable through some other forum. The issue I believe this is tracking is when the `place_id` returned from the `autocomplete` service:

https://maps.googleapis.com/maps/api/place/autocomplete/json?input=34%20Aldershot%20Road,%20Guildford,%20GU2%208AF,%20United%20Kingdom&types=geocode&key=

Does not return ANY results, but your place_id (ChIJ-wrkCsbQdUgR8--nRmOq34A) does return ONE (bad) response with both Geocode and Place Details:

https://maps.googleapis.com/maps/api/geocode/json?place_id=ChIJ-wrkCsbQdUgR8--nRmOq34A&key=

https://maps.googleapis.com/maps/api/place/details/json?placeid=ChIJ-wrkCsbQdUgR8--nRmOq34A&key=

Excellent sounds good. I'll log this as a separate issue.

The placeId received from a place on Google Maps' `onPOIClick` event (PointOfInterest.placeId) is not the same as the one received from the Google Places API for the same place. Not sure what the intention with the inconsistent placeid implementation was but I'm really looking forward to a fix. Thanks google.

Here's a link to the report on stackoverflow - https://stackoverflow.com/questions/46139697/googlemaps-placeid-of-pointofinterest-not-the-same-as-one-from-api

This is still an issue for us.

There are placeId's that are returned from the autocomplete service, but when you put them in the /place/details/json, it says NOT_FOUND.

This is causing production issues for our environment...

For example: "Burnham, United Kingdom" returns placeId: ChIJI-k54YZkdkgRG4nprrZVv64 from the autocomplete service.
However, when looking this up in place/details: "NOT_FOUND" is returned

Same issue with "Salerno, SA, Italia" today.

placeId  from the autocomplete service is "ChIJiTC9NFfCOxMRoHQD2hOXpBU"

PlaceService.GetPlaceDetails returns "NOT_FOUND"

Confirming that this is still a bug. I am unable to see place details for "313 West 29th Street, New York, NY" on the Place Autocomplete page:

https://developers.google.com/maps/documentation/javascript/examples/places-autocomplete

(It throws an error dialog).

Still perists error also with ChIJCU1G2eriOBMRJbK1tMPe5zA (Potenza, PZ, Italy)

Having the same problem also:

##### Test 1 FAILED #####
Autocomplete place_id for "1098 Waters Avenue, Aspen, CO, USA": EiIxMDk4IFdhdGVycyBBdmVudWUsIEFzcGVuLCBDTywgVVNB

[MISMATCHED] Place Details returned "1098 Aspen Way, Broomfield, CO 80020, USA" place_id: EikxMDk4IEFzcGVuIFdheSwgQnJvb21maWVsZCwgQ08gODAwMjAsIFVTQQ

##### Test 2 FAILED #####
Autocomplete place_id for "Waters Avenue, Aspen, CO, USA": Eh1XYXRlcnMgQXZlbnVlLCBBc3BlbiwgQ08sIFVTQQ

[MISMATCHED] Place Details returned "Aspen Ave, Colorado Springs, CO 80905, USA" place_id: ChIJTwEyDoxEE4cRSZhhKVOjkKo

##### Test 3 FAILED #####
Autocomplete place_id for "1025 Waters Avenue, Aspen, CO, USA": EiIxMDI1IFdhdGVycyBBdmVudWUsIEFzcGVuLCBDTywgVVNB

[MISMATCHED] Place Details returned "1025 Aspen Way, Broomfield, CO 80020, USA" place_id: ChIJxcuZ6O2Ka4cRRVe_O2kBcDA

##### Test 4 OK #####
Autocomplete place_id for "1102 Waters Avenue, Aspen, CO, USA": ChIJqeOOq947QIcRYF9ZL4GtRjg
[MATCH] Place Details returned "1102 Waters Ave, Aspen, CO 81611, USA" place_id: ChIJqeOOq947QIcRYF9ZL4GtRjg

##### Test 5 FAILED #####
Autocomplete place_id for "1104 Waters Avenue, Aspen, CO, USA": EiIxMTA0IFdhdGVycyBBdmVudWUsIEFzcGVuLCBDTywgVVNB

[MISMATCHED] Place Details returned "1104 Aspen Dr, Evergreen, CO 80439, USA" place_id: ChIJY5647Hqia4cR3xe6TfgTrRc

Having major issues this morning.  our customers in and around chicago are having problems
EiMxODk4IFdpbmNoZXN0ZXIgQ3QsIE9zd2VnbywgSUwsIFVTQQ
- 1898 Winchester Ct, Oswego, IL

I have observed this issue as well today. First, I made a request to the Nearby Search API to obtain a place ID. Then, I made a request to the Place Details API using this place ID. The Place Details request returned a status of NOT_FOUND.

Reporting the same sort of problem but with the "Unknown_Error" response from geocoder. I've used the autcomplete service to search for the address and once user selects one, the place_id is not being found .. if I use the direct url then it reports the 'place_id is invalid'.

Observing this on the following Ids (and more). These were returned by autocomplete requests:

ChIJyygUO3TjjTkR8QP6yqDJykU
ChIJx4LCUpoEDTkRpDT3uvi1aPo
ChIJ_ZjPpfTz9DkR6cR7e_J7GM8
ChIJC8CDrrqUcjkRirqa0HO6_00

The detail request returns NOT_FOUND for most requests

I used place id from the autocomplete api response, in the /place/details api and got:
   {
       "html_attributions" : [],
       "status" : "NOT_FOUND"
    }

It happened to me in several addresses.
In some addresses i got a regular response  after i waited  2 minutes between autocomplete call and the
place details call.

Happening on 44 Latitude Boulevard, Thomastown VIC, Australia: EjA0NCBMYXRpdHVkZSBCb3VsZXZhcmQsIFRob21hc3Rvd24gVklDLCBBdXN0cmFsaWEiMBIuChQKEgnpMzCybU_WahHttzaUe6up6hAsKhQKEgkbqLQObU_WahHfpARI3kfqGg
This address worked previously.

Flow goes: Autocomplete -> place_id -> GetPlaceDetails with fields=address_component,place_id

i also have same issue ..
https://maps.googleapis.com/maps/api/place/details/json?key=xxxxxxxxxxxxxxxxxx&placeid=EiVTasO2dsOkZ2VuIDIxMSwgQXNraW0sIEhvdsOlcywgU3dlZGVu
{
   "html_attributions" : [],
   "status" : "NOT_FOUND"
}

#67 is actually https://issuetracker.google.com/35823492

#68 i think this is not related this.
 discription of this (" https://issuetracker.google.com/issues/35823492") is :
"Details for Place Autocomplete prediction is missing street number, or located a different locality"  
but in my case nothing is come in response.

Most of the times the result matches that description, but the very same issue (root cause) occasionally results in NOT_FOUND responses as well.

Trying to find : Jalan Safir Raya No.21, RT.8/RW.3, Srengseng, Kota Jakarta Barat, Daerah Khusus Ibukota Jakarta, Indonesia
with place_id : EmpKYWxhbiBTYWZpciBSYXlhIE5vLjIxLCBSVC44L1JXLjMsIFNyZW5nc2VuZywgS290YSBKYWthcnRhIEJhcmF0LCBEYWVyYWggS2h1c3VzIElidWtvdGEgSmFrYXJ0YSwgSW5kb25lc2lh
result :
{
    "html_attributions": [],
    "status": "NOT_FOUND"
}

ALSO

find : Jalan Safir Raya No.21, RT.13/RW.3, Bintara Jaya, Kota Bekasi, Jawa Barat, Indonesia
place_id : ElRKYWxhbiBTYWZpciBSYXlhIE5vLjIxLCBSVC4xMy9SVy4zLCBCaW50YXJhIEpheWEsIEtvdGEgQmVrYXNpLCBKYXdhIEJhcmF0LCBJbmRvbmVzaWE
result :
{
    "html_attributions": [],
    "status": "NOT_FOUND"
}

my client is going mad

I have the same issue. When I make a place details request for a place id that I have just get from an auto complete response, I get "NOT_FOUND" in the result.
Auto Complete Request : https://maps.googleapis.com/maps/api/place/autocomplete/json?input=Esentepe%20Mahallesi,%20%C5%9Ei%C5%9Fli/%C4%B0stanbul,%20T%C3%BCrkiye&key=*************&language=tr&components=country:tr
Place id: ChIJdSWkflu2yhQRBw4n2CqXwfg
Details Request: https://maps.googleapis.com/maps/api/place/details/json?placeid=ChIJdSWkflu2yhQRBw4n2CqXwfg&fields=name,geometry&key=**************
Result:
{
   "html_attributions" : [],
   "status" : "NOT_FOUND"
}

Happened to me today! Very frustrating! Lost a ton of money!!

Same issue for me.
Steps:
1. Use Autocomplete API to get a list of places.
2. Select Hong Kong (place_id: ChIJD5gyo-3iAzQRfMnq27qzivA) from results
3. Query Places API (details end point with above place_id)
4. Get NOT_FOUND

Full response:
{
   "html_attributions" : [],
   "status" : "NOT_FOUND"
}

Works fine for other places

Same problem with "München, Germany"

https://developers-dot-devsite-v2-prod.appspot.com/maps/documentation/javascript/examples/places-autocomplete-addressform

There is an on-going incident: https://issuetracker.google.com/145144256

Please refrain from posting comments on issues that have been Fixed a long time ago (file a new one instead).