inria-UFF / VRPSolverEasy

A simple Python interface for VRPSolver, a state-of-the-art Branch-Cut-and-Price exact solver for vehicle routing problems
https://vrpsolvereasy.readthedocs.io/en/latest/
MIT License
115 stars 11 forks source link

Latitude and Longitude - issue when it has to be entered in as a integer , can I multiple it by 10 (each lat and each long) to get decimal? #26

Open mventura00 opened 4 days ago

mventura00 commented 4 days ago

Hi developers,

I have a situation, where I am using the VRPsolvereasy, and entering in the 'latitude' and longitude for different counties in Pennsylvania that are closest to Pittsburg airport. I'm running into an issue, and wanted to give a proposed solution, and see what you thought of it? So , to give you an example , there are 2 counties (of the 26 counties designatied to Harrisburg airport), where they have this latitude and longitude:

'Indiana' county, latitude = 40.68 , longitude = -79.1 , demand = 20 'Clearfield' county, latitude = 40.95 , longitude = -78.56 , demand = 25

However, because VRPsolvereasy requires you to enter in the 'latitude' and 'longitude' as an integer, then they both have the same latitude and longitude (since you cant use decimals) so it looks like they're identical counties, which they're not, so I would have to enter it as (when I round it)

Indiana' county, latitude = 41 , longitude = -79 , demand = 20 'Clearfield' county, latitude = 41 , longitude = -79 , demand = 25

My question is: Can I multiple the latitude and longitude, each by 10 respectively (to capture the first digit after the decimal) and then later when I get the cost (lower bound), I will divide it by 10? Does that work? Does it make sense? So I could potentially enter it into the input text file as:

Indiana' county, latitude = 406 , longitude = -791 , demand = 20 'Clearfield' county, latitude = 409 , longitude = -786 , demand = 25

In that way, I would be able to differentiate between the counties, and later,when I get the solution for cost, I'd divide by 10. What do you think?