Giter Club home page Giter Club logo

usavian's Introduction

USAvian experimental

Leveraging knowledge, experience, data, and tools to decision making in the bird conservation and management community.

About

This project was born from unsuccessful attempts of trying to build mental maps of who, what, where, and how various organizations, research groups, working groups, and state and federal agencies are doing conservtion science or delivery. We are designing a database of sorts to inform an interactive info-scape and companion user interface for digitally mapping out the complex network that is bird conservation.

An example of the layers USAvian map can integrrate includes but is most definitely not limited to:

Expected Benefits

Connecting Science and Decision Makers. Many researchers are producing science which is relevant, and in some cases can directly inform, avian conservation or management. However, unless the researcher is (a) funded by the relevant stakeholder(s) or (b) is hyperaware of the potential stakeholders, their science may not be consumed by stakeholders until they come across the published science. Even if the consumer finds this published research, they must then digest and translate the science published. This project has the potential to serve as a middle-person. That is, a researcher who is interested in efficiently disseminating their work might identify potential stakeholders based on taxonomic, spatial, or temporal attributes in the database.

Networking. Although most conservation groups are likely aware of those doing conservation or management work either in similar regions of the US, or are working with similar habitat or taxa, this tool may help users identify previously unknown entities who are perhaps working with similar taxa but in disparate areas, or in similar areas but with disparate taxa. This tool may help reduce the siloed divisions within the [bird] conservation community.

Outreach. Similar to its role in teaching, the tool may also help increase awareness outside the scientific communities of the conseravtion efforts in their immediate area, or with respect to taxa of interest. We also envision this map to as a resource to which communication professionals can refer when researching conservation news per region or species.

Iterative Design and Development of the User Interface

Desired Features

For updated lists of potential and acutal data sources, please visit Issues 2, 3, and 7.

Contributions

If you'd like to help or voice your strongly-worded opinion publicly, please visit Issue 1 or email JLB. Contributors must follow the Code of Conduct.

USGS Provisional Software

This software is preliminary or provisional and is subject to revision. It is being provided to meet the need for timely best science. The software has not received final approval by the U.S. Geological Survey (USGS). No warranty, expressed or implied, is made by the USGS or the U.S. Government as to the functionality of the software and related material nor shall the fact of release constitute any such warranty. The software is provided on the condition that neither the USGS nor the U.S. Government shall be held liable for any damages resulting from the authorized or unauthorized use of the software.

usavian's People

Contributors

trashbirdecology avatar

Stargazers

 avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

usavian's Issues

[usavian] Call for contributors & co-conspirators

Wanna help? Cool!

Drop me a line here (or via email).

Looking for folks interested in helping paint a clear(er) picture of bird conservation in the US and ideally those to help with contributions in the following areas:

  • Data collection
  • UX/UI (esp. using maps)
  • Database design
  • Database maintenance
  • Designing mechanisms for soliciting and fielding feedback

Data source dynamicity

I'm sure you are thinking about this already, but it seems like you are going to need some intensive focus on describing and encoding the routes to all source data and information for this model. None of this is static. You can produce a snapshot in some way, but we really need a whole set of algorithms designed to keep this information up to date and sorted out over time.

You'll run into the inevitable cases where some human has to click a link and do some work on a given dataset to whip it into shape for use in this integrating context. But even in those, we need a framework that maximizes what machines can do and minimizes human intervention. Behind every data and information asset in your stubbed out data structure, I would expect to see metadata describing access to the original source material and processing steps instantiated as code. Maybe you are already thinking along these lines, and I apologize if I missed something in the documentation.

[usavian] Wish-list: ecologically-relevant data layers

A wish list for cool stuff to overlay our core data:

  • Ecological disturbances
  • Cat colonies
  • Climate conditions and projections
  • Habitat variability
  • Major weather events (e.g., drought, severe winters)
  • Cropping patterns

[usavian] Data sources: threats and barriers to conservation efforts or birds generally

Cats!

Trap-neuter-release

A very interesting proposal via Twitter (by @therealmo777) to "please address the serious problem of feral cats and the misguided TNR programs". This is a very curious request, and would be pretty cool (and perhaps depressing) to visualize if it doesn't already exist.

We could reach out to those in anti-TNR advocacy for more info or ideas (e.g. Chris Lepczyk). (JLB contacted CAL 20191212)

Outdoor cats - policy, facts

Surely there are existing layers of predicted threats of cats

Collisions

Any existing layers/interpolations of predicted building, car, etc. collision impact?

Illegal take

Same ^?

[usavian] Data sources: conservation groups, agencies, and administrative territories

CLICK ME for a list of identified data sources, urls, and descriptions

JLB try to check each data source or webpage as done as it is mined or is added to the data list (^) so as to make progress on this Issue and related Milestones 2 and 3.

Identify geographical boundary data layers, and confirm which are/are not in PAD-US or SFR.

Actively managed properties

Federal and state

  • Dept. of defense properties (some or all are in PAD-US, need to check!)
  • Fish and Wildlife Service refuges (some or all are in PAD-US, need to check!)
  • Bureau of land management (some or all in PAD-US, need to check!)
  • State managed lands (some may be in PAD-US)

NGO and privately owned

  • TNC property
  • Audubon property
  • Land trusts
  • Conservation easements (see next Section)

Conservation units and boundaries

Nation-wide partnerships or plans

Regional, Local partnerships or plans

Observatories

  • Rocky mtn bird conservancy
  • Point Blue
  • Should we map the MAPS stations? Idk if they do any local conservation, but I assume conduct outreach...

Some webpages to mine for more information and potential layers

[usavian] Data sources: funding opportunities

Would it be useful to add a layer comprising regular funding opportunities for those trying to conduct either or both bird research and conservation. There would need to be a compelling reason, however, as to why we would overlap with the efforts of Cornell's land trust fundraising page

Existing lists of funding

To mine and/or point to

Funding types

Currently categorized as research, conservation, management, or outreach.

Conservation

Urban Bird Treaty
FWS coastal grants

Management

Outreach

Urban Bird Treaty

Research

Other relevant things

  • FundingRef: persistent identifiers and information standards for funding sources

[usavian] Data sources: bird ranges, distributions, other information

CLICK ME FOR LIST OF DATA SOURCES HERE

  • (โœ”) symbol indicates the data was added to /data/data_sources.csv

Below is a list of A list of desired data sources for bird ranges and distributions:

Data warehouses

Taxonomy

[usavian] Concept: avoiding the "if you built it they will come" model

In order to avoid the model of build it first ask questions later, I suggest we first identify our potential end user groups, and informally solicit feedback from persons (<9 non-feds or infinite feds) from groups in these communities.

We can certainly go about soliciting information this in a more systematic and scaled-up way at a later point, but to improve impact I'd like to do this sooner than later.

Here are the potential end users I see, please chime in with your opinions:

  1. Conservation groups who buy, retain, or manage lands* (e.g., TNC, Audubon local and national)
  2. Conservation and advocacy groups who do not buy, retain, or manage lands (e.g., GoMAMN)
  3. Conservation advisory groups (e.g., NABCI)
  4. Management agencies (federal and state management agencies, tribal agencies)
  5. General population
  6. Science producers (e.g. Auriel Fournier)
  7. Birdwatching community

*Includes those who are managing habitat not directly for but which ultimately impacts birds

[usavian] Conservation and management entities in the Great Plains

Summarise the state of conservation and management in the Great Plains region of US and Canada.

We will roll out the pilot USAvian tool for a region within the Great Plains, if not the entire ecoregion. Given our collaboration (and the fact that birds don't recognize political boundaries) with the Canadian Wildlife Service, we would prefer span the US/CAN border.

Database blueprint

Create a blueprint for the data structures required to incorporate into the USGS Biogeographic Information Systems framework (e.g., interoperable with the framework used to build tools like USGS maps).

Knowledge graph base for your information model

At its heart, what you seem to be building here is a knowledge graph with known and as yet unknown end members. I'd encourage thinking about it this way, building a conceptual model for the graph, and then instantiating it as the glue that holds everything together.

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.