(No comment was entered for this change.)

Is there any estimates on if and when this will be available. This is an important 
feature for a new possible big web system in Norway. We want to use GoogleMap, but 
without this we might be forced to use another product.

Hi -- I've shared your request with the team, but I can't comment on upcoming
features or plans. General advice is to build systems based on what you know already
exists, and  not what you hope will exist soon. Just curious, is there a map provider
that allows for defining road blocks in driving directions requests? 

We have several local Norwegian providers that can do this, but the costs are 
defined in another way and we feel that general look and feel (and usage) is very 
good with GoogleMap. Yahoo and Microsoft also miss this functionality in their 
product. It's odd, because it's a common adjustment you might want to make in a map. 
If you know about a roadblock, you want to eliminate that road, not define what 
other route it should choose (that's for the travel engine to define). We also 
deliver GIS client solutions based on our own developed system, so we might move 
parts of that system to web, but it would be a shame not to be able to use a system 
that's already out there.

Thanks for the info. It's a valid feature request, but is non-trivial to implement in
a flexible/scalable manner. I'd suggest working on your own system instead for now.
You're welcome to use other people's data on top of Google Maps via tile layer
overlays, polys, or custom maps.

It should be trivial enough to have scalable. It all depends on how the node tree is 
defined. There are two standard implementation, one will only need you to mark this 
road vector as "finished" before starting the search, giving no penalty at all. The 
other would need you to increase the road vector structure with a boolean value, and 
check for this in the inner loop of the search algorithm. In it's cleanest form, 
this will give you a penalty, but if there is any other checks there this might be 
merged into one of those.

If the crossroads are the nodes in their algorithm (usually are), they can still 
have a static tree structure. They only need to add a disabled roadsection pointer 
of 4 or 8 bytes (pointing to a small linked list structure) to the dynamic list of 
generated info (finished, last_section etc.). It can be separated enough that people 
not using road blocks will have no impact at all, the static data will still be the 
same size, and the scalability will also be good for those that use roadblocks (you 
could set a limit on the amount of roadblocks if that's a problem, still there have 
to be millions to give any kind of noticeable impact).

Would you like to apply for a job here and make that your first task? 
http://www.google.com/intl/en/jobs/index.html
(Sounds like you know what you're talking about).

Anyway, I've shared your ideas with the team.

Thanks for sharing it.

(I already got a complex development job doing many things. Algorithms like this are 
some of it, and I guess your team works from within USA and I'm from Norway :) )

(No comment was entered for this change.)

This would be useful for us, too. Our clients are almost exclusively heavy traffic 
operators, and they're subject to all sorts of noise and weight restriction zones. 
It'd be nice if we could exclude roads by polygon as well as by point, but any kind 
of progress in this direction would be a great selling point for us.

In this post http://groups.google.com/group/Google-Maps-API/msg/2e40c6ac1b759b77 I
suggested using {avoid:} in order to compensate for mapping errors where banned turns
are not honoured in the directions. Perhaps avoid: could take a GLatLng or GPolygon
as an argument?

While taking a route-vector out for the purposes of route planning may be reasonably
possible as the OP outlines, I agree that it may not be trivial to match a point or
polygon to avoid into the sort of route-vector marking suggested. A point would need
to be expanded into a polygon of reasonable size (to ensure that it covered the width
of the road) and then the vector would need to be analysed to see if it passed
through the polygon and should be discounted.

Creating a polygon will only complicate matters. What they should do is wrap the
point to the nearest road vector line. And that line would then define what road
should be excluded. You just have to make sure your point is positioned so that it
wraps to the right road.

Add my vote here.  My constituency is the zero-budget public safety world, and while
they do take to heart my admonitions re life-threatening situations, the larger shops
use proprietary mapping solutions have some kind of mechanisms they employ to
identify obstruction.

Part of their daily task is to drive/patrol common highways and note obstructions.

Some general solution would be MOST attractive.  Not easy to implement, but an
important feature.

Our university campus closes roads and bridges for construction and we'd like to be
able to specify this so that the Google driving directions route around the problem,
as though the road or bridge does not exist. How can this be done?

-Ken 

I am developing an application in which I would need to avoid some points, so I'm
also interested in this issue. I need to provide users the possibility of going "from
point A to point B and avoid a point C, or a list of points". It'd be something like
this, similar to loadFromWayPoints:

loadAvoidingPoints(wayPointsToAvoid, queryOpts?)

or even:

loadFromWaypoints(waypointsToVisit, waypointToAvoid, queryOpts?)

I know you can't comment on upcoming features or plans, but I'd like to know if you
are working on this feature, because the first message about this issue is from
almost one year ago.

Thank you very much!

I would like to vote in favour of this change as well; this would really increase the
potential of GoogleMaps in some of the solutions we are developing at Sqills
(www.sqills.com). I am very curious if and when such "avoid" features are available
as an additional parameter to the GDirections.load or loadFromWaypoints functions.

With kind regards,
Johan Nieuwerth

Added my vote!
Are there any news about this feature?

Best regards,
Igor V.

Changing status of "Accepted" issues to "Acknowledged", to clarify their 
state.

We may not be able to resolve all bugs or fulfill all feature requests, but 
we do thank you for filing them, and we will continually revisit all 
acknowledged issues and evaluate their feasibility. Thanks!

Added my vote!

Added my vote! 

I would prefer:
"from:Hope avoid:37.897253,-97.789705,10 to:Heaven"
Avoid streets 10 Meter around 37.897253,-97.789705.

Is somebody working on this feature?

Added my vote!

(No comment was entered for this change.)

(No comment was entered for this change.)

(No comment was entered for this change.)

(No comment was entered for this change.)

That was really a pitty. I challenge the team to give a good description of why this wont fix. I see no reason why this should be such a problem to make.

We have lots of construction around our area in Fort Worth, Tx, and the state is sending out text email to show us where. It is very clumsy because most people do not know street names, especially for named access roads on high speed highways.  A way for them to map these, and display them' or, add a layer to an existing map with blockages and dates would be very useful.

Would be really useful to avoid crime hotspots (where criminal gangs target periodically) in South Africa....

We are building a system that allows to calculate the routes for heavy load running on normal road. We have a database of the bridges with the weight limit (and tunnels with height limits). It would be really good to identify where the load cannot go and to have a route calculated around them!

Re-opening. I think this was mistakenly closed.

Also updated the description.

it has been 2 years since the team acknowledged the feature request.. any updates on this? I really need this feature on my project.. or maybe you can share us tips on how to do it in an unofficial way (if there is any).. thank you!

any updates??? badly needed feature..

One of the optimizations that the current routing engine relies on to ensure it is fast enough to support features like draggable directions is that the route graph is precomputed. Although we can modify the graph globally, for example to support a bridge closure that affects everybody, we can not support one off modifications to the graph at query time.

We've left this feature request open because our routing algorithms are constantly evolving, and there is always the possibility that at some point in the future they will change in such a way that we can support this request. However right now there are no near term plans to do so.

Any updates on this? We're also interested in this feature..

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.

(No comment was entered for this change.)

Would love this feature.

This would definitely be helpful!!!

(No comment was entered for this change.)

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)

 Issue 3273  has been merged into this issue.

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!

(No comment was entered for this change.)

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!!!

pls sir 

if you interested to sell this property 

i have a developer 

pls reply as possible as 

my email id 

[email protected] 

i will reply fast only

it about you

pls sir 

if you interested to sell this property 

i have a developer 

pls reply as possible as 

my email id 

[email protected] 

i will reply fast only

it about you

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.