Refactor code to merge in driving distance properly

[abd1tus]

• [ ] Build_souce function in model_data.py need to be updated to handle lat/lon as two columns.
• [ ] Include an warning if all driving distances are not immediately available
  • [ ] Include other functions/ features that approximate distances when they are not available
  • [ ] flag when approximations are used.

[abd1tus]

Daphne: Driving distances working. Can run, but won't run merge to main until it fits better with locations of files and not accessing tables of distances multiple times. Code needs to be refactored. But can do runs before merge if needed - already been tested with Gwinnett. Discovered the issues with lat/lon in some cases.

Susama: Depending on what Juanma says, would like to rerun for counties we have. Try to figure out a way for middle ground - get driving distances up and running and call it a beta until we get QC in place.

Chad: can do some open street maps to google comparisons as QC. - millions of addresses so can't do them all.

[abd1tus]

Next step: incorporate a feature to handle edge cases where lat/lon that cannot be routed to in OSR. Include columns to indicate that an approximation was made and information about how the approximation was made - location that we manually snap to.

(Tom might have a solution on this and possibly paper?)