PELAGIOS Graph Explorer
Welcome to the home of the PELAGIOS Graph Explorer! The PELAGIOS Graph Explorer is an interactive visualization for exploring how the data contributed by the [PELAGIOS project partners] (http://pelagios-project.blogspot.com/) is related through place. Screencasts explaining the basic usage are available on the PELAGIOS blog:
[The PELAGIOS Graph Explorer: A First Look] (http://pelagios-project.blogspot.com/2011/08/pelagios-graph-explorer-first-look.html)
A hands-on demo you can play with online is available at http://pelagios.dme.ait.ac.at/graph-explorer.
The PELAGIOS Graph Explorer is licensed under the [GNU General Public License v3.0] (http://www.gnu.org/licenses/gpl.html).
The PELAGIOS Graph Explorer is built with [Gradle] (http://www.gradle.org). (Download and installation instructions for Gradle are [here] (http://www.gradle.org/installation.html)). To test and compile the project, run
To generate the Web application archive (.war) file, run
To generate an Eclipse project, run
(Note: dependency download may take a while the first time you are building the project.)
A note to developers: the project comes with an included starter class that will launch the application demo in an embedded Jetty Web server. Please ensure that your IDE compiles the application classes to the /src/main/webapp/WEB-INF/classes directory (if you use Eclipse, the gradle script will handle this for you). Locate the class
in the /src/main/test folder, and launch it as a Java application. Per default, Jetty will launch on port 8080. The PELAGIOS Data Visualization Demo will be available at
Modify the settings in the starter class if you want a different port or application root path.
In order to run the unit tests you need a set of CSV dump files of the [Pleiades] (http://pleiades.stoa.org) gazetteer. These files are not included in this project to save repository space.
Please obtain recent versions of the pleiades-locations-YYYYMMDD.csv.gz and pleiades-names-YYYMMDD.csv.gz CSV dumps from
Unzip them and place them in the /src/test/resources folder. Note: presently you also need to update the file names in the unit test source code. This is only a temporary issue, though.