-
Notifications
You must be signed in to change notification settings - Fork 1
Limitations
These are some limitations to the program which we hope to improve upon sometime in the future.
This is because the program relies on a static set of intersections which are close enough to campus buildings. A path which detours away from campus, or a path whose destination is far enough away from an intersection recorded in the program (for example, VC to EH), may not be recognized by the program as quicker than the path generated through its algorithms.
One example is from Brennan Hall to Northrop Frye - it takes you in a circle. This is a worse case of the above and is because the quickest path has no intersection at all. Our implementation requires that all paths generated have at least one intersection. We plan on modifying the program to handle such cases in the future.
In addition, there may be quicker paths which involve the usage of alleyways or shortcuts (for example, paths which pass through Philosopher's Walk). These are not included in our program for the same reason.
The program is set up so that stopovers for specific amenities are marked on Folium with a unique corresponding icon (for example, coffee stopovers have a coffee icon). These are external icons from Font Awesome. However, only one icon can be displayed per point - so a stopover which has multiple desired amenities may not display all of its corresponding icons.
Our implementation of the program does not support this, unfortunately. One workaround is to find a University building closest to the intersection of interest. (However, we recognize that this may not necessarily be the best workaround, especially if you are away from the center of campus - for example, close to the Dentistry building or Chestnut Residence).
The program is unable to detect or handle unexpected detours (such as a blocked intersection). This is partly due to its offline nature as the program does not require an Internet connection to run.