IssueTracker

See the bug on Github:

https://github.com/googlemaps/v3-utility-library/issues/395

Another bug report on Github:

https://github.com/googlemaps/google-maps-services-js/issues/151

FYI, I took the clustering example from the Google Maps API Guides page at...

https://developers.google.com/maps/documentation/javascript/marker-clustering

... and I changed the Google Maps version to v=3.exp

... and hosted the result at http://www.GaryLittle.ca/mc-bug.html

Load this address in your iOS browser (Safari) and try clicking any of the clusters. Nothing happens.

This code uses the old MarkerClusterer but I'm sure the behaviour will be identical if using MarkerClustererPlus.

I've just verified that this problem also affects Android devices (running Chrome).

See https://issuetracker.google.com/issues/73592536

Note: my examples are in "greedy" mode.

See https://issuetracker.google.com/issues/73730684

+1 on this bug, likewise it only appears to be an issue when gesture is set to ‘greedy’

Thanks for all the bug reports. I am sorry.
We are trying to work out the best solution.

An explanation:
In greedy mode, we need to prevent the page from scrolling, and to do this the maps API calls preventDefault() on the touchstart event. Unfortunately, this also prevents the browser from firing a click event.

A workaround / solution:
Listen for touchstart, and call stopPropagation(). This means the maps API will not have a chance to call preventDefault() and your click will be preserved. It also has the effect that clicks on the clusters won't fall through to the map, which is probably what you wanted.

div.addEventListener('touchstart', function(e) {
  e.stopPropagation();
});
div.addEventListener('click', function(e) {
  // should work as before.
});

Great, that workaround seems to solve the problem.

But greedy mode did work with MC before 3.32exp so what changed in 3.32exp to break it?

I'll update MarkerClustererPlus at GitHub once I've tried this fix out on a few other maps I have created.

Good afternoon! I updated the latest version of MarkerClustererPlus, but my problem is not solved! When clicks on the cluster, the click event occurs first on the map and I have a marker, then the cluster event is triggered and a zoom occurs

#11 Yes, I see what you mean. The #9 workaround results in a click event on the map when you click a cluster marker. This didn't happen before.

More ideas from Google on this subject would be welcome from Google!

More on my #12 comment...

Actually, it's not the #9 workaround that's causing the problem. It's just another side effect of using v3.32 exp instead of earlier stable releases.

In other words, with 3.32 exp only, an attempt to click a cluster marker results first in a click event on the map followed by a click event on the cluster marker. This doesn't happen when you click a regular marker.

Note: there is specific code in the click handler for the marker cluster DIV to stop event propagation, but it's of no use in 3.32 exp because the click reaches the map first.

Hint to Google: is this perhaps something to do with the fact that the cluster marker is in the overlayMouseTarget pane?

This is a very complex issue, and it's hurting my head a bit.

First, let's try and come up with a workaround that works:

1. If you stopPropagation the touchstart, then the browser generates a mousedown, mouseup, click as usual.

2. The Maps API listens to the mousedown and mouseup, and interprets this as a click.
  - So you should stopPropagation the mousedown as well. And pointerdown just to be safe.
  - This is actually a bug, and we have a fix in the pipeline. We intend to listen to click events instead of mousedown and mouseup. Then you can stopPropagation the click.

Second, there are actually a few different things you might want.
A. listen for clicks on the overlay
B. stop clicks on the overlay from bubbling up to the map.
C. enable/stop map panning/zooming on the overlay

So, initially we were discussing A, but then it turned out that we also needed B.
What about C... Do you want C?

OK, I've taken your suggestion and I call stopPropagation() on mousedown (and pointerdown). I was already calling stopPropagation() after a click. This change prevents the click from reaching the map, so that's the good news.

Now the problem is that I can't initiate a panning action that begins on a cluster marker (as you could before). I guess that's C... so, yes, I want C as well.

Oops, the touchstart stopPropagation workaround for v3.32exp prevents clicks from from being handled properly on the stable release of GM. Aargh. Any suggestions for how to detect the experimental version?

You can inspect google.maps.version, although you'll have to do a little string parsing.

I think v3.32 has two bugs.

1. v3.32 doesn't synthesize a "click" event for tap on a greedy map. This makes it hard to listen for *tap* on OverlayViews on a greedy map.

2. v3.32 doesn't respect mouse "click" stopPropagation(). This will be fixed shortly.
  (a) Note, however, that we never respected tap "click" stopPropagation(). Taps always led to map click events.
  So "click" events on the map are not a big deal for markerclustererplus, right?

The workarounds for 1 are:
- use cooperative instead of greedy
- stopPropagation on "touchstart" but then you can't pan the map by dragging a cluster
- detect tap by listening to "touchstart", "touchmove" and "touchend".

I'll keep this bug updated with our progress. We're working on it.

MarkerClustererPlus normally handles clicks on its own and does not want to pass them on to the map. So it does want to stop a tap "click" on iOS / Android from being reported to the map. (In fact, there is a bug filed on Github on that very subject.) At present there is already a stopPropagation call in the click handler that (I guess) works only on a desktop OS.

I can't use cooperative instead of greedy because that means 2-finger panning and that's not what users expect especially on a full-screen map such as the ones I typically create.

stopPropagation on touchstart fails on the current stable release of GM. I guess I could check google.maps.version but that's an ugly solution. Might be the easiest though.

Detecting a tap by tracking touchstart/touchmove/touchend -- not sure what's involved here but I suppose if I could detect a gesture that looked like a tap I could call the click handler after touchend. This is going to challenge my skill set! Would GM simply generate a map "click" anyway?

I'm leaning to version checking......

Now my head is hurting.

OK, I've now added the version checking so I now have functionality restored on older stable releases of GM.

I'm still stuck, on GM v3.32 exp, with tap clicks on clusters being passed through to the map and no map panning when the pan starts on a cluster.

At about 8 pm PST last night (March 5) -- 3 pm March 6 in Sydney -- a new version of the experimental API seems to have gone live.

This API breaks the marker clusterer badly. In particular, the clusterer code I call in response to a map idle event (which adjusts which markers are being managed and involves accessing a database and repaint()-ing the clusterer) seems to generate another idle event. The result is an infinite loop where the DB is repeatedly searched in response to idle events that never end.

I didn't touch anything at my end!

All works perfectly with Google Maps API v3 stable and has done so for many years.

What happened?

I've just checked and the very same problem now also occurs when using the old MarkerClusterer. (I'm using MarkerClustererPlus, of course.)

See https://issuetracker.google.com/issues/74233017 for a similar problem that happened yesterday/

... and see https://stackoverflow.com/questions/49136827/google-maps-data-layer-mouse-events-trigger-map-idle-event

This new issue is tracked under https://issuetracker.google.com/74214837

We are working on a fix for that.

I believe our most recent release fixes the issue. Let me know if there are still problems.

Works for me - many thanks!

We've got it working now. Great.
We're using MarkerClusterer by the way.

all good, thanks a lot!

I have verified that a tap on a cluster marker no longer results in a click event on the map. I can now also begin a pan from a cluster marker. So both those issues have been fixed. I've had to keep the version checking in #20 to stop propagation after touchstart on 3.32+ but that's ok.

To have the finished route graph static gives many other problems, and it get's pretty big. The penalties seems to be more with this than having a good smart cached priority queue. Also implementing the fact that you can compute all waypoints at the same time limiting the graph by a huge amount.

Would love this feature.

This would definitely be helpful!!!

We would love this feature for use in Christchurch, New Zealand. We have developed a system for the Christchurch City Council which contains all of the current and planned road closures and road works within the the city. (Due to the earthquakes there are huge amounts of roadworks and road closures planned over the next 5 years) We have been looking for a routing engine which can handle routing around the road closures.

Better still would be a way for us to provide our official data directly to GoogleMaps so that it can be used by all - that might be better discussed in a separate post.

This feature would be a great addition to V3 and very helpful to our business.

Essential addition, indeed!

I also am looking for this feature!  Being able to avoid certain bridges for weight limits would be incredibly useful for oversize  construction loads routing!

In Creede, Co hwy 160 on fire. google maps wont go around. Add button to say "Highway no longer exists - Do no to use - reroute" even if its 200 miles further. Thanks

Lets get this!!!

Excelente seria bueno que google maps agregar esa funcionalidad y permitiera por medio de la api por mandar los puntos o tramos que se desean bloquear al momento de generar una ruta. Estaré a la espera de esa actualización (Y)

I'm working on a project using GDirections. The feature to avoid some streets is exactly what i need. Is there still no way to get such a function? Will it be added to the API?

Thanks!

It's been 5.5 years since this was requested!

I cannot believe this feature does not exist. There has to be some type of hack to get around this.. Maybe provide several optional routes and set one that doesn't intersect the roadblock/accident as the default? I have not used routing enough to know if that is possible.

Strange, not available till now!

It should be a great feature for avoiding limited traffic areas..

Has anyone determined if there is a app/client-side hack to this?

Another vote for this.

another vote for this

I need it also - to avoid bridges with a too low weight rating for heavy trucks!

Unfortunately #57 has probably identified why this will never be implemented. It removes a revenue stream as truck-specific sat-navs/route planners command specialist prices.

Maybe it's possible to add 3rd party data into the web (Waze would be nice)

vote for this

We are a small developer team from Norway seeking a solution to this using Google Maps.

Another vote for this

I also vote for this

add my vote

Would love this feature!  Add my vote!

vote

That would be nice...

vote

This would be very nice

Would love this feature!  Add my vote!

Would be very very useful. Gets my vote.

It is super useful and it should also be available in the navigator (Waze-like reports), so that people can input temporary road interdiction, such as due to traffic accidents, floods, crimes etc). I definitely vote it up.

I've been hunting around the web since hours for a way to do this. Definitely gets my vote.

Would be very very useful. Gets my vote.

7 years later and still no change on this. To all of those wishing for this, it is obvious Google will NEVER add such a feature. I think it is just beyond their capabilities as developers to figure this out.

Please add this feature, need it for an important project, and there seems no alternative way of programming around it.

So we have access to Waypoints, but not Anti-Waypoints? :(

We're transitioning from Microsoft MapPoint (RIP) to Google Maps.

In 2006 (probably before) we had the 'AvoidAreas' feature. Seemed simple; a rectangle [center (lat,lon), width, height].

Routing results would only pass through an AvoidArea as a last resort, like if it was the only path, or a waypoint was inside the AvoidArea. I believe width and height were in generic map units, never had to worry about it. The properties of the drawn rectangle saved and loaded without needing modification.

Can't believe we'll have to give up this functionality.

I vote for this. A main thoroughfare near where I live flooded out last week.It will likely be closed for weeks or months to come. However, Maps keeps routing me there because guess what: It has no traffic! Surprise! Come on, this is a feature Street Atlas USA had 15 years ago!

This would be very useful for a mapping application for RVers. My RV is over 13 feet tall and I would like to know that my routing isn't going to take me to an overpass that is too short.

Many years of this request an no recent acknowledgement or comment by Google is disappointing.

I would vote and need something of this sort one road around my apartment is closed multiple times and i would like to avoid it.

Regards

You have my vote! This is required.

This seems like a natural feature to add, and it's very surprising that it's been an open issue since 2008.

Add my vote

Add my vote. The city of Rome, Italy has several zones of "limited traffic" where non residents cannot enter during some hours of the day. Considering this case it would also be nice to have an entire polygon area to be marked as "avoid" and if possible being activated/deactivated on a configured schedule (e.g.: only weekends from 6pm to 3am).

I want this as well.

Can we get any update on the process? This would be a really useful feature.

This feature would extensively be used in the organization I work for. We need a way to avoid certain roads.

this will be usefull for me on this momment :(

Please add this!!!

[Comment deleted]

[Comment deleted]

I also would like to have this feature implemented.
Yesterday I have found a roadblock while getting directions with Android Auto and I had hard time figuring out what could be an alternative route.

I also need this feature.

hope this will be implemented. I need this function, too

why has this not been added yet?

It looks like this has already been implemented on Google Maps but it is still not available for the API?!

Just found this while calculating a private route on Google Maps! (see attachment)

#98 i still cannot see any option to do this on google maps

how did you add it?

It seems like it has been added automatically - I have nothing to do with it!
Just recognized it while calculating a route...

Yeah it happens during road closures and things like that. Maps knows and will find a better valid route...

It will will be so usefull for my compagny too.

This would be a major attractive feature for Google maps.  Road / junction closures are sometimes just overnight for 2 or three days, and would not get into the "master map". And they happen frequently, so please add the feature for a user to add a 'personal' road block for a journey.  I've checked other navigation apps and they don't do it either.  The first one to do it will attract many customers.

+1 for this feature. Would be good for avoiding high crime areas.

also +1 for this option, any news Google?

[Comment deleted]

Would be great for a safety app! Avoiding high crime areas

Definitely a +1 for me.  There's a particular road that always comes up on my route home that I will not drive down, due to the condition of the road.  As I have an average 35-40 mile commute, I sometimes don't realize that this particular 3 mile stretch of road is included.  A dirt road would be a smoother ride, and present less risk to my tires.  

As a traveler, I get very frustrated being unable to avoid streets, roads or areas!  Garmin has provided this function for years, why can't Google?

This could be considered a safety/liability issue. We use the API to print directions on guest passes in gated communities where all streets are private. Many times, a small residential street not meant as a major thoroughfare is returned by Google. As a result, hundreds of vehicles are sent down this street each day instead of the main streets meant for larger traffic volume.

On Google Maps via a traditional computer and web browser, we can use our mouse and drag the route to a different road so it generates a slight route alternative. Why can't we do the same thing with our finger on a mobile device? I prefer routes that have fewer turns (another feature suggestion found on old school GPS software), especially if they don't increase the length of the trip very much. On a route to a restaurant I am going to tonight, I made my route change on my computer but cannot get the same thing on my phone. And sending to my phone doesn't bring in the exact route, only does just the start and end points.

Thanks.

We are looking into this, however there is no concrete plan yet.

In order to avoid specific points in a route, the Draggable Directions feature in the JavaScript API is currently the best solution.

Please report issues about "Send directions to your phone" on Google Maps in the Google Maps product forum at
https://productforums.google.com/forum/#!topic/maps

There seems to be no support for intermediate waypoints though:
1. if you add a waypoint in the LHS panel, the "Send directions to your phone" option is disabled
2. if you modify the route by dragging a point in it, the route sent to your phone will only have the original and destination:
https://productforums.google.com/forum/#!topic/maps/e730pTkYs3w;context-place=topicsearchin/maps/%22Send$20directions$20to$20your$20phone%22

+1 vote...
My problem is my direction software (using google map API) targets the trucking industry and I need to be able to exclude roads that are not permitted to trucks...

Google needs to either open-source this so we can start a bounty, or get someone on it.

This is SUPER important to our business. We are currently in the process of deciding between Google and ESRI for the foreseeable future, and this could be a tipping point to go to one or the other. Any information on when this will be implemented would be helpful.

Thanks.

Other vote.

My App is currently using Google Maps. I would like drivers to avoid certain roadways. Please help.

I Agree, I am working about this kind of feature.

Seriously needed feature!!!

Yes my business needs this feature too!

Apologies for the change in email subscriptions, we're looking into fixing this[1].

Meanwhile, you can tune your Notification settings under the Settings option from the gear icon in the top-right corner. Setting the preference for Starred issues to Minimal, you will only receive e-mail if you are added or removed from an issue or an issue is marked as fixed and you are the verifier.

Please see https://developers.google.com/issue-tracker/concepts/settings for the full details.

[1] The old issue tracker would not send you emails for every comment, once the issue has >100 stars.
You would then only get emails about comments from project owners. We're looking into doing the same here.

A very useful feature to have to be able to support directions for trucking also.

Is there any way possible in order for me to be able to add more details so that i am able to gain access accurate location to my devices?

This feature is very important and necessary for business!!

Without this feature, there is no other way to correct google mistakes after e.g. local road reconstruction starts.... sometimes public buses are allowed, but cars not. In similar situations, the directions google gives are simply completely wrong.

As in the city that I live in, certain roads are not accessible by certain type of vehicles (motorcycles / trucks / certain type of private car). This feature will be very helpful to accommodate such restrictions

+1 Vote. This feature would be incredibly useful if  - for example - a severe thunderstorm knocks a trees down throughout a city. Municipal emergency services will report the issue on local radio stations, but may take up to several hours to clear a road block (due to other, higher priority problems). Being able to select an intersection, or a stretch of route, and mark it as "temporarily un-trafficable" would be incredibly beneficial.

An added benefit would be that once a certain number of users report the same relative area as untrafficable, Google Maps can then recommend detours/alternative routes to other users for the remainder of the day.

123123">

+1 we need this for our business as well

+1 i need this for an app too. google can u give us a concrete plan now? the last status update is over a year ago.

+1 This would be useful to me too.

Anybody know of other tools that can do this? ArcGIS looks like a candidate (https://developers.arcgis.com/javascript/3/jssamples/routetask_multiple_stops.html), anything else?

+1 I-4 is a deathtrap. We don't go on that road for anything and it's very annoying to either have to choose no highways at all or have maps constantly try to redirect us back onto I-4.

+1 This would be a great addition to the API!

We have a ski club that is at the mid point of a road that is always inaccessible from the other side which is also a gated road- When there is snow, we are only accessible from the one side. However Google maps will take you over the inaccessible route from the other side. This feature is needed to prevent serious accident and injury that could ensue from google maps taking people down this inaccessible route. Please add this feature to prevent such issues

Want this feature for truck directions.

10y and still you cant add points what you want avoid.

I live in an area with lots of toll roads.  Some of these tolls may take you through the airport incurring massive charges.  I use the toll road filters but I would like to exclude airport roads from routes when I opt to take toll roads. A blacklist for this road would be very useful.  Also with frequent construction nearby, blacklisting those roads would be very helpful.

Come on Google... so many years and this request still isn't available.
I need this feature ASAP....please guys, take this request into consideration next time.

Frankly can't believe this hasn't been implemented yet

I think that an alternative (while google continues thinking about this issue a lot of years) is iterate routes between two points returned by directions api and parse legs point text content, if that text contains the blocked road (for example "A-5" or "A5") the route is rejected. I think the max number of routes returned by directions api is 3 but I am not sure...

how to upvote for this issue?

Hello google!?

For all the people who are watching this:
If you need that feature mainly for road constructions and other incidents, that impact all public drivers on that road, just add them in "Waze". They provide a neat editor and a good community, that will help you adding the closures and incidents.
The closed roads will then synced in the background and will appear in Google Maps, too! It will take a few days but it works, I just tested it. And it will also affect your routing as well.

Be safe out there!

+1 StackOverflow:
https://stackoverflow.com/questions/53063287/googlemaps-api-dont-drive-through-certain-streets-or-regions

???

That is very useful if google add this feature to their API

Wow it’s a DECADE later and the one biggest tech companies in the world cannot add a feature, simple or not, that many other’s have. Astounding!

I am currently working on a web/app that will do this feature for walkways. ArcGIS is good and will work, but would be easier to implement if google maps had it. Will link the website if it gets finished.

There is a road on my commute that I always skip. I drove down it once and never again.
It would be great if I could manually block this road from any directions that I request.

We could really use this feature in Denmark, because our wise government have littered the roads with orwellian surveillance. Hope the feature will be available in the next 11 years (!)

Please add this feature soon.

It's been 15 years. I don't think this is happening 😆.

Ok only 11 years, but I still don't think it's happening

It's EXTREMELY important! Please add this feature as soon as possible!

After 9 years I'm beginning to loose hope...

Hello.. Is anyone there?

yeah hey what's good

I have the same issue. It's a pity this seems abandoned.

This must be a joke.... this feature should have been part of the maps API from the very beginning.

Recently many communities here added zones ( including entire cities ) in which you are not allowed to drive unless you have a special permit - if you drive a diesel engine powered car more than 3 years old

for those affected by this, google maps becomes completely unusable, it keeps routing back through the forbidden zones

Upvoting

I have the same issue. It's a pity this seems abandoned.

Will this ever happen??

Hi, ist somebody there?

Z

This would be very useful for avoiding regions with a lot of crimes here in Brazil, it's a shame that after almost 12 year after the suggestion this feature still doesn't exists.

Google maps keeps sending me through streets that are not possible to go through. 2 examples are:
1. A section of a street that was made one-way a few months ago but is still shown as the fastest route.*
2. A road through a university that only allows employee cars to go through (I'm not an employee).

The app should have a feature to mark a section of the street as "don't use" even if other people are using it.

*Regarding the one-way street, I did report it months ago, but some idiots keep using it, possibly blindly following Google maps. So far, I haven't seen any accidents there, but that's another issue.

#167 You can report streets being wrongly utilised for Directions (or any other issue with the map data) with the "Send feedback" functionality in Google Maps.

To everyone: Thank you a lot for sharing your interest and use cases for this feature request. We understand how useful it would be, and please be assured that popular feature requests are regularly discussed internally.
This being said, please understand that unless we state otherwise, we do not commit to implementing any particular feature request, nor to any timeline. As mentioned in #3, we strongly suggest you base your implementations and choices on the features that are currently available.

I live in a town that has some extremely bad roads. I would very much like to be able to blacklist the bad ones which cause physical damage to my suspension.  America's roads aren't in great shape. Thanks.

Completely off topic, but this "issue" has been around for 13 years. My then 3 year old son is now driving.

I'm getting nostalgic as I think about why I originally wanted this feature back in college: To build a flood disaster street level routing app.

Ahhhh, memories.

Make that 14yrs :)

Lol, wow.  Just got notified about the post here and I barely remember being a part of this thread.  So much nostalgia for when I believed Google had their sh** together.

#170 same. Wanted to make an app in college that would gather data and route people around bad roads and such. Memories of long past projects.

Worked on a cool project and wanted to reroute company trucks from closed
bridges and roads on flood events. Great memories when young me thought I
could do it easily.

On Mon, May 2, 2022 at 6:43 PM <buganizer-system@google.com> wrote:

There are cities, like Athens Greece that forbid traffic in a specific zone in the center of the city.
Being able to avoid specific streets or areas would be really helpful with that.