Bug: Address with slash (/) in driving directions are converted differently by API and by "Link to MapQuest"

4 posts / 0 new
Last post
anthony.benites...
Bug: Address with slash (/) in driving directions are converted differently by API and by "Link to MapQuest"

There seems to be a bug when Mapquest converts addressess that have slash(/) in the address line. For example, see the below two addresses:

          start address: 500 1/2 E DONALD ST, WATERLOO, IA 50703
          end address: 937 1/2 E DONALD ST, WATERLOO, IA 50703
       

1. Using the directions API: (https://developer.mapquest.com/documentation/mapquest-js/v1.3/examples/b...)

L.mapquest.directions().route({

          start: '500 1/2 E DONALD ST, WATERLOO, IA 50703',
          end: '937 1/2 E DONALD ST, WATERLOO, IA 50703'
        });

Renders: 

500 E Donald St, #1/2

937 E Donald St, #1/2

 

2. When using the "Link to Mapquest" the "1/2" gets rendered as 12.

http://www.mapquest.com/directions?saddr=500 1/2 E DONALD ST, WATERLOO, IA 50703&daddr=937 1/2 E DONALD ST, WATERLOO, IA 50703&maptype=map

Renders the addresses as:

500 E Donald St, 12

937 E Donald St, 12

 

So, the directions API and the "Link to Mapquest" seemed to be converting the two addresses differently. Neither converted the addressed correctly, but "Link to Mapquest" seems to be doing it the worst. Is there any workaround to at least make it show as the directions API does it?

 

Thanks!


MQBrianCoakley
Nope. Both are interpreting 1

Nope. Both are interpreting 1/2 as a unit rather than part of the address. There is no workaround to force MapQuest.com to handle the input identical to the MapQuest.JS handling.

 

Handling of fractional addresses is an edge case that the team is aware of and it is part of their backlog.


hugcetlz
good

good


hugcetlz
good

good