Driving Distance Widget: Converting Kilometers to meters when distance is less then 1 Km

  • rbroadfo
    Asked on February 16, 2016 at 10:51 AM

    Hello. The 'From' field in my Driving Distance Widget is read-only, it's my business address. The 'To' field is the customer's address.  The resulting distance is used in the Calculation Wizard to calculate travel fees over 30km.  

    I received a form submission with two errors:

    (1) The 'From' field and the "To' field were the same, and

    (2) The Calculation Wizard showed a travel fee, even though there was no distance.

    Please see the screen shot of that form submission. 

    Form: https://form.jotform.com/50274139754256

    Thanks,

    Ryan

    Jotform Thread 773368 Screenshot
  • Kevin Support Team Lead
    Replied on February 16, 2016 at 2:55 PM

    I checked your form and the widget, first I think there is an error with the "From" address, this is the address that the form has.

    Driving Distance Widget: Converting Kilometers to meters when distance is less then 1 Km Image 1 Screenshot 20

    I checked the widget and that is the address that it has. Could be possible to add the correct address again? 

    Then, once the address is corrected, we will make some tests to see how it's working and try to replicate your issue in our end.

  • rbroadfo
    Replied on February 16, 2016 at 3:26 PM

    The 'From' address is a Postal Code (used in Canada) and it's worked every other time. The 'From' address was the same as the 'To' address, so I'm quite certain it didn't have to do with the 'From' address only containing the postal code. 

     

  • Kevin Support Team Lead
    Replied on February 16, 2016 at 4:45 PM

    I checked it and now it's calculating the correct value, this is my result.

    Driving Distance Widget: Converting Kilometers to meters when distance is less then 1 Km Image 1 Screenshot 20

    You may show the calculation wizard, make some tests and check if it's taking the correct value. If you do not want that your users enter the same address that is in "From", then you may add a validation using conditions, if they are the same the result should be 0, then you may show a message indicating that the addresses can not be equal.

     

  • rbroadfo
    Replied on February 17, 2016 at 9:24 AM

    You've shown that you cannot replicate the error. I was not able to replicate the error either. But it happened as can be seen in the screen shot of the form submission. The 'From' address - which is read-only, populated with the 'To' address. I am not confident this will not happen again. If it happens again, the customers will think there is a travel fee when there is not. This will effect sales. 

     

     

  • Charlie
    Replied on February 17, 2016 at 12:21 PM

    I tried to replicate the problem in your end. I believe the problem is that the distance output is now showing meters if it is less than 1 Km. 

    Here's how I replicated it:

    I changed the event address exactly the same shown in your sample submission, I presume you have already updated it in your latest version.  You'll see that the distance is 61 meters. 

    Driving Distance Widget: Converting Kilometers to meters when distance is less then 1 Km Image 1 Screenshot 20

     

    Your condition states that if it is greater than 30 (or in your latest version of the form its 25), it should do a calculation. 61 is greater than 25/30 which is why the condition is still true. 

    Calculation will be:

    = ( (61 - 30 ) * 6.00 )

    = $186

     

    Now I am not sure how we can proceed on this. Technically, if it is less than 1 Km, it would be good to display the distance on meters. However, that is causing problems in your conditional logic. I'm thinking it should just stay on "Kilometers" because there's an option to have it in that units, it should strictly be like that and not change to meters. So the expected output should be like 0.61 Km. 

    Let us know us know if my observations are correct and if you agree on having it stayed on Km instead, I'll forward this issue to our widget team if that's the case. Apologies for the inconvenience.