Plans
Some parts of the application are not yet complete. This is a very brief
outline of what we still plan to do. (This will all probably get done between
the end of Summer Session I and the beginning of Fall 2005.) Crossed-off items
have been completed.
Complete path data. The current path data is for
demonstration only and is in no way complete. Now that we have obtained
a vector version of the base map we wish to use, we can create our base
images and enter full path and location data. A detailed data
set has been entered. What remains is to tweak the data, and connect a
few remaining locations.A better base map. The current map is the visitor map
PDF. (It even still has the key in the upper right-hand corner!) We
would like to use the colored visitor map, such as the one that is used by maps.ucsd.edu.Complete building codes. The application supports
associating a building code with each location (i.e., "PCYNH"
with "Pepper Canyon Hall"), and many, but not all, have been
entered.Google Maps-style scrolling. Who can resist?
Extensibility
These features are not specifically planned, but they are listed to
give an idea of how this project could expand:
- Building maps. Click on an individual building name to open
a sub-map (complete with all the features of the existing map --
locations, path finding, etc) of the inside of that building.
- Maps of other locations. For instance, an individual college
could have more detailed path information covering just their area of
campus. The map application is flexible, however, and the editor makes
it easy to add path data to any map, not just one of UCSD.
- Integration with other applications. Each location may have
an associated building code, so it is easy for external applications
that know building codes to build URLs for the map. As an example, to
show the path between CENTR and PCYNH, you simply access
map.cgi?from=CENTR&to=PCYNH.