kkumbada,
Graphserver is really just the brains behind the accessibility
measure. Its inputs are a pedestrian/cycle network and transit network
and schedule. Theoretically, these inputs could be derived from any
format, but Graphserver comes with tools that make it easy to import
Open Street Map data (for the pedestrian/cycle network), and Google
Transit Feed Spec data (for the transit network and schedule).
Graphserver's outputs are trip-plans in text format, just like you
might find on a transit agency's website. Graphserver can also output
text describing the travel time from a given point to all other points
in the network. I used the latter functionality as an input to the
accessibility map. So, graphserver has no built-in visualization
functionality.
I measured accessibility quite crudely. It's simply a measure of the
"usefulness" of each location, weighted by the travel time to access
each location. In other words, if a given point has quick access to
many useful locations, it receives a high accessibility score.
Usefulness was estimated (again, crudely) as the weighted sum of
population and employment available at a destination, with one job
being considered more useful than one resident.
I'm afraid that we're veering away from the intended subject matter
for this forum - please feel free to email me directly if you have any
further questions. I'd be interested to know more about your project!
Graeme