Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a sites method. #2

Open
SimonGoring opened this issue Jul 29, 2016 · 3 comments
Open

Add a sites method. #2

SimonGoring opened this issue Jul 29, 2016 · 3 comments

Comments

@SimonGoring
Copy link
Contributor

Especially with Neotoma data, it is possible to return a large number of occurrence results from a few sites.

This would also be applicable for trying to estimate sampling effort, e.g., show me all sites from which data has been collected in some sort of bounding box (that could include time).

I would like to suggest a sites method, which returns:

  • site name (or some identifier)
  • lat
  • long
  • age younger
  • age older
  • database
  • number of samples (?) - maybe not, this gets into differences in analysis units & occurrences, for microfossil records I'm not as interested in the total number of occurrences within a dataset/site as I am with the number of analysis units.

so:

/sites?bbox=-127,23,127,24&ageYounger=2&ageOlder=6

would return all sites from the composite data service that match this. We could search with many (all?) of the same parameters that we do with the occurrences.

/sites?bbox=-127,23,127,24&ageYounger=2&ageOlder=6
@mmcclenn
Copy link
Collaborator

mmcclenn commented Sep 7, 2016

Yes, I agree we need one of these. In order to make this work, I need to be able to query Neotoma for sites. I will talk to Mike Anderson about creating one.

@SimonGoring
Copy link
Contributor Author

There is already a sites method, it's documented at http://api.neotomadb.org/doc/resources/sites. Really, on the Neotoma side, we'd need something that lies in between the datasets and sites methods. So that we don't return duplicate sites if they have multiple dataset types at them.

I assume in PBDB you have the paleocoords linked through collection_no to the collection and then to the occurrences? In this case, then maybe we need to think of Neotoma datasets as more akin to PBDB collections, where a collection is a single point or bounded polygon. Is that fair?

@mmcclenn
Copy link
Collaborator

mmcclenn commented Sep 8, 2016

That method doesn't suit the purpose. We need something equivalent to http://apidev.neotomadb.org/v1/data/occurrences that will take the same set of parameters but return a list of distinct sites rather than a list of distinct occurrences.

Is there a forum for the Neotoma developers where I can raise this as an issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants