Whenever I put in a get request for an optimized route involving this point, it either takes a really long time to calculate, or I get a 504 Gateway Timeout error. If it actually does finish calculating, the return is a condensed version and I can't work with it in certain ways (like using addRoute to draw a line between points).

Here is an example url with our key removed to illustrate the wonky return:

This return is robust and is as expected, and the processing time is a fraction of the problem url.

Then I was able to get a visual look see at the street numbers from Here maps, and found that the point that is causing problems might be in a unique situation where it does not necessarily touch the street that it is supposed to be on. The address of the problem point is 1635 N George Mason Dr, Arlington, VA 22205. The address next door that works great is 1625. Here is a url that shows 1635 being off on an island a bit: https://wego.here.com/directions/mix//1635-N-George-Mason-Dr,-Arlington,...

Can someone explain to me what is happening here? Is this a bug, known bug? Thanks in advance.

The switch seems to be working well. Thank you. Is there a link somewhere that explains the difference between the two? And do both services use the same amount of transactions in the request? I can't seem to find these answers.

Both the licensed and open versions count transactions the same way. The difference is that the open service uses OSM data while the licensed service uses OSM as a backup for licensed data. So the licensed version is more likely to have the correct data.

Nope. This has not been put into a development cycle yet.
In the meantime, the locations can be checked for duplicates before using in the optimized route request. Also, a non-optimized route works great with the duplicate location.

About MapQuest for Business

MapQuest for Business powers thousands of businesses with
location-enabled Geospatial solutions. Our platform provides companies of any size
with the means to increase efficiency and streamline processes, connect with
customers, and ultimately deliver the all-important exceptional user experience.
And, as usual, the MapQuest for Business experience is backed by the customer
service and technical support that we're known for.