10

Travel Calculations need a complete reworking

The way travel is calculated in Arbiter hasn't changed in the 10 years I have been using it, and it needs a major update.

First of all, when you create a level under a sport, you specify:

--how far in advance of game time the officials should be there (good)

--a speed in miles per hour that the officials should be able to travel (bad)

The speed officials can travel varies greatly by time of day, day of week, and which direction they are going. Officials driving from downtown to the suburbs go a lot more slowly than people driving from out of the metro into the metro. It is time to, at a minimum, use the estimated travel times from Google Maps to calculate travel times. If you can incorporate estimated travel speeds based on time of day and day of week, so much the better. But it makes zero sense to have me input that all officials working U15 boys lacrosse games can travel at 45 mph at all times (or whatever).

Also, the zip-to-zip distance calculations need to change and use actual distances as calculated by Google Maps. They are not too bad in the city, but in out-of-metro areas the zip codes cover large regions, and I often get officials who live in the south of one zip code assigned to the north of another, and Arbiter thinks it's 12 miles and inside their travel limits but it is really 40 miles and well outside their travel limits.

This also affects our travel pay calculations, which are often wildly inaccurate because of these issues.

I know this is not an easy fix and that I am asking a lot, but taking advantage of Google Maps is really the way to go here. It would be a huge benefit to assigners and officials to make this upgrade happen.

 

12 comments

Please sign in to leave a comment.