Git Product home page Git Product logo

geodisy's Introduction

⚠️ While the pipeline can still be implemented with the resources in this repository,
The Geodisy Project is no longer in active development/maintanence as of Nov 8th, 2022 ⚠️

Geodisy

The world of data at your fingertips

What is Geodisy?

Find research data visually, spatially and quickly

Research data can be hard to find, and even harder if you're researching a specific place. Geodisy changes that, giving you a window into the world of research data with map-based tools familiar to everyone. Search by place name, or by drawing a box. The world of research data is yours to discover. Geodisy is the software that will let you do just that.

Who will use Geodisy?

People
Anyone looking for research data who wants to use a map or a box to find data. Researchers, students, journalists, and anyone else with an interest in data from university research will benefit from Geodisy's search tools.

Institutions
The first users of Geodisy will be FRDR, Canada's Federated Research Data Repository, for the quick and easy discovery of Canadian Research Data. When released, anyone with the available infrastructure will be able to plug in Geodisy and make a compatible repository more discoverable.

Why use Geodisy?

Data, and in particular research data, has always been difficult to find. Keywords can be hit and miss, and text based descriptions don't show you where your place of interest lies. Geodisy changes that, showing you where, not just what.

If you're a running a research data repository based on Dataverse, Geodisy will take your repository's data, search for geospatial metadata and files, and copy them to a new system which allows for visual searching. Your original data and search methods are untouched; you have the benefit of both.

How does Geodisy work?

Geodisy is a separate server software component that examines the metadata, such as the study records for research data and any associated data. If Geodisy finds spatial data, metadata and data are harvested, then normalized to have the same geospatial metadata standard. Afterwards, both data and metadata are injected into a geospatial data server and a viewer/search component.

For the more technically inclined

Geodisy consists of middleware (a piece of software living on a server, not directly accessible to end users) that:

  1. Harvests data and metadata from a repository (intially Dataverse)

  2. Cleans and normalizes metadata and data found in study recods

  3. Creates bounding boxes for data sets if applicable, and reads geometry from compatible files, such as shapefiles

  4. Injects bounding box data and/ or geospatial data into a geospatial server, in this case Open Geoserver

  5. Presents a visual search in the form of a Geoblacklight front end

Geodisy is open source All of the software you need will be free and open source (FOSS). The Geodisy middleware component will be available for download from Github. In addition to Geodisy, you will need:

  1. A Dataverse repository to harvest from

  2. Open Geoserver in which to place your data

  3. Geoblacklight to allow users to search

When will it be available?

Geodisy is available now. See it in action at geo.frdr.ca

Where can I find documentation?

Geodisy documentation is available in our Github repository

Where is the software?

Because Geodisy is an open source project, all of our software is freely available. Download or fork the software from Github.

Who is behind all of this?

None of this would be possible without our grant (RDM-059) from CANARIE, to whom we extend our thanks.

Core Project Team (UBC) Eugene Barsky Principal Investigator
Paul Dante Software Developer
Edith Domingue Advanced Research Computing (ARC) Client Services Manager
Mark Goodwin Geospatial Metadata Coordinator
Tang Lee Project Manager
Paul Lesack Co-Principal Investigator
Evan Thornberry Co-Principal Investigator
Project Partners Jason Brodeur McMaster University
Marcel Fortin University of Toronto
Alex Garnett SFU
Amber Leahey Scholars Portal
Jason Hlady University of Saskatchewan
Joel Farthing University of Saskatchewan
Venkat Mahadevan UBC ARC
Todd Trann University of Saskatchewan
Lee Wilson Portage Network

I want to know more!

Look for us on Twitter! #geodisy

We are happy to chat. Contact the Geodisy team at [email protected]

geodisy's People

Contributors

awoods avatar dependabot[bot] avatar ect123 avatar j-f-far avatar markjwgoodwin avatar mcfarland-ubc-library avatar pdante avatar pdante-ubc avatar plesubc avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

geodisy's Issues

GitHub Release for 1.0?

I see that there are release notes; however, it is unclear where to get the released application??

The first place I looked was in the project's "Releases", which, as of now, is empty.

Suggestion: To tag the software at the point of the 1.0 release, create a GitHub release for 1.0, include minimal installation/run instructions in the GitHub release page.

Change related datasets to be based on a custom metadata field rather than dc_source_sm

Currently, related datasets are using the dc_source_sm metadata field that deals with parent-child relations between records. This metadata field is more designed for dealing with an index map and the maps that are indexed, and our usage of it may cause our metadata to look strange if someone else harvests it from OpenGeoMetadata. It would be better if we could create a custom metadata field in the geoblacklight json and then display that custom metadata as related records in our customized GeoBlacklight interface.

The official description of how dc_source_sm is supposed to be used: https://github.com/geoblacklight/geoblacklight/wiki/Using-data-relations-widget

Uploading dataverse dataset to geoserver or geoblacklight (Docker)

We are working on a project with Dataverse, geoblacklight, and Geodisy.

It took time to get geoblacklight working (it may still have some bugs), and now I can't find a Guide or Documentation to set up Geodisy.

We have the current situation
In Docker:

  • Dataverse
    
  • postgis
    
  • postgres
    
  • geoserver
    
  • geoblacklight
    

My current changes

GeodisyStrings.java
SCHOLARS_PORTAL = "http://127.0.0.1:8080/"

PrivateStrings.java
PRIVATE_GEOSERVER_PASSWORD = "testpassword";
PRIVATE_GEOSERVER_USERNAME = "admin";
PRIVATE_POSTGIS_USER_PASSWORD = "geoblacklight";

GeoserverStrings.java
POSTGIS_USER = "geoblacklight"

GeodisyTask.java
"geo.harvestFRDRMetadata()" -> "geo.harvestDataverseMetadata()

The download works, but I have no idea, how to get the data uploaded to Geoblacklight (or geoserver).
In the end, everything should work locally in a docker, but for now, it should just work for testing.

Is there some guide that could help?
I looked in Documentation, but it is mostly for dependencies setup.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.