This is a fork of the AODN Portal for use by the Sydney Harbour Observatory which is managed by The University of Sydney.
The SHO customisations were built by Intersect Australia in collaboration with the University of Sydney. The software development was funded by the Australian National Data Service (ANDS). ANDS is supported by the Australian Government through the National Collaborative Research Infrastructure Strategy Program and the Education Investment Fund (EIF) Super Science Initiative.
This code is licensed under the GNU GPL v3 license - see LICENSE.txt
AODN Open Geospatial Portal
The AODN open geospatial portal is a Grails application for finding, visualising, and downloading geospatial data. The application integrates with the GeoNetwork metadata catalog and OGC Web Map Services.
You can view the portal in action at the following locations;
- AODN the main AODN portal
- IMOS the Integrated Marine Observation Systems portal
- WAODN a Western Australia-focused portal
- SHO a Sydney Harbour Observatory-focused portal which is managed by The University of Sydney
- Faceted search for easy navigation of datasets.
- Animation controls such as pause, fast-forward, etc.
- Configurable themes and splash page.
- Save and share data visualisations.
- Subset and aggregate multiple datasets into a single file for download.
- Filter data before download.
- OpenID authentication.
- Advanced spatial search that ensures results have features in the region of interest. Not just a bounding box intersection.
New Features added in SHO
- AAF authentication (SHO only).
- Support Users from different organisations.
- Support activate and deactivate users.
- Enable users to manage access to specific data sets
- Enable users to describe research data collections.
- Ingest data feeds from different data providers.
- Support CRUD operations on metadata of datasets.
- Create metadata party record and collection record xml files for uploaded datasets, and make them available for harvesting via OAI-PMH.
- Enable users to query the systems research data collections.
- Enable users to download research data sets.
- Enable the collection, description and storage of manually collected field data.
Getting Your Hands on Portal
Firstly we welcome contributions so please feel free to fork the project, address any issues or add features and submit a pull request.
Building From Source
If you want to build from source you will need to have Grails installed on your build machine.
Once you have the source it should be as simple as
$ grails war in the root folder where you have checked out portal
then deploy the war to your application server.
Feel free to ignore the pom.xml, this is an old artifact from when we used Maven as our build tool. We now use the Grails tooling directly to build our artifacts. We have a dependency on Maven to launch our Jasmine, we are in the process of removing that dependency, you can help with that too
Can I Get A Pre-Built War?
Yes you can. You can write to us, info at emii dot org dot au to discuss the best way of getting portal and keeping your version up to date.
You can fork portal and have your configuration included in your code base however portal offers the ability to specify
your configuration externally via an environment context variable named
aodn.configuration you can clone an
example AODN config here and modify as required. The example should be
descriptive enough to get you up and running however you can always shoot questions at us via our contact email.
Configuring Portal Authentication Method (OpenID Or AAF)
To configure Portal Authentication Method, you can modify AODN authentication config here and modify as required. The provided configuration hould be descriptive enough to get you up and running however you have to set up OR get a working AAF Service Provider to use AAF as authentication Method.
Portal has a few collaborating applications that you may also want to deploy
- An OpenID provider
- AAF Authentication Service Provider (SHO only)
- JOAI - Data Provider/Harvester
If you want to mimic the AODN portal searching capabilities then you should consider deploying an instance of spatial search note that spatial search has a dependency on a specific minimum version of GeoNetwork. If you cannot deploy at least that version then you should consider not using spatial search for performance reasons and using GeoNetwork directly for spatial extent searching. Note that at time of writing this means that your results may not be as fine grained as available via spatial search.
(How Do I Drive This Thing?) Read the Getting Started guide on the wiki