-
Notifications
You must be signed in to change notification settings - Fork 53
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
datasetID
or Dataset ID
#14
Comments
In ERDDAP, for all of the actual data requests, the data variable (column)
names will be exactly the same for all types of response file types. There
can be some differences in the way the data is presented: notably, in the
.htmlTable response, a datum that is a URL will be presented as an <a href>
tag and possibly with a related viewer (e.g., for audio files).
In ERDDAP, for other requests (notably dataset listings), there may be a
slight difference between the column names in an .htmlTable response
(notably, capitalization, spaces, newlines, extra content/tooltips) vs. all
other file types (which will be identical). The column name cells will
often also have lots of other content, e.g., <a href> tags. Again, cells
which have URLs are presented differently in .htmlTable responses vs. all
other file types.
In general, the .htmlTable response is optimized for human consumption in a
browser. All other responses are much more consistent, but there are
quirks. E.g., Since ERDDAP still makes the older style Matlab files which
are limited to 32 (31?) character names -- so ERDDAP shortens and adds a
hash to longer variable names in Matlab files.
I hope that explains ERDDAP's behavior and sounds reasonable.
…On Sun, Dec 3, 2017 at 11:01 AM, Rich Signell ***@***.***> wrote:
If you query ERDDAP using allDatasets, dataset ID is returned as datasetID
.
If you query ERDDAP using advanced search , dataset ID is returned as Dataset
ID.
Is there a reason for this?
It's not a big deal, but it messed me up for a bit when writing my little
ERDDAP time series explorer.
To pull the lon/lat values from the allDatasets table that matched the
datasets returned from advanced search, I needed to do:
dfr = dfll[dfll['datasetID'].isin(dfa['Dataset ID'])]
https://github.com/reproducible-notebooks/ERDDAP_timeseries_explorer/blob/
master/ERDDAP_timeseries_explorer.py#L214
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#14>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABarOCbDP33Ml8ah6CoPW9fj3OzUZUMtks5s8vAQgaJpZM4Qz1wv>
.
--
Sincerely,
Bob Simons
IT Specialist
Environmental Research Division
NOAA Southwest Fisheries Science Center
99 Pacific St., Suite 255A (New!)
Monterey, CA 93940 (New!)
Phone: (831)333-9878 (New!)
Fax: (831)648-8440
Email: bob.simons@noaa.gov
The contents of this message are mine personally and
do not necessarily reflect any position of the
Government or the National Oceanic and Atmospheric Administration.
<>< <>< <>< <>< <>< <>< <>< <>< <><
|
@BobSimons this all sounds reasonable, but I don't know if this explains why if you query ERDDAP using allDatasets, you get |
allDatasets is a dataset (in the DAP sense). It behaves in the strict way
that all DAP requests respond.
Advanced search is not a dataset and is not a query of a dataset.
…On Tue, Dec 5, 2017 at 9:35 AM, Rich Signell ***@***.***> wrote:
@BobSimons <https://github.com/bobsimons> this all sounds reasonable, but
I don't know if this explains why if you query ERDDAP using allDatasets,
you get datasetID, and if you query ERDDAP using advanced search , you
get Dataset ID. Both are returned as csv.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABarOED9x_EiHcnzqq3IBaM9pSs7y3rtks5s9X7YgaJpZM4Qz1wv>
.
--
Sincerely,
Bob Simons
IT Specialist
Environmental Research Division
NOAA Southwest Fisheries Science Center
99 Pacific St., Suite 255A (New!)
Monterey, CA 93940 (New!)
Phone: (831)333-9878 (New!)
Fax: (831)648-8440
Email: bob.simons@noaa.gov
The contents of this message are mine personally and
do not necessarily reflect any position of the
Government or the National Oceanic and Atmospheric Administration.
<>< <>< <>< <>< <>< <>< <>< <>< <><
|
Ah, okay. Now I get it. |
I should have also said:
The goals of searching allDatasets and using Advanced Search are basically
the same: finding datasets which meet certain criteria.
But the way that they work, what you can do with them, and the nature of
the results table (e.g., column names) is very different.
It is unfortunate that Advanced Search has "Dataset ID" and allDatasets has
"datasetID".
allDatasets is stricter (as dataset queries are) and was written many years
after Advanced Search.
I am reluctant to change them significantly (e.g., column names) to make
them more consistent because external systems (like yours) are written to
work with them as they are.
On Tue, Dec 5, 2017 at 9:40 AM, Bob Simons - NOAA Federal <
bob.simons@noaa.gov> wrote:
… allDatasets is a dataset (in the DAP sense). It behaves in the strict way
that all DAP requests respond.
Advanced search is not a dataset and is not a query of a dataset.
On Tue, Dec 5, 2017 at 9:35 AM, Rich Signell ***@***.***>
wrote:
> @BobSimons <https://github.com/bobsimons> this all sounds reasonable,
> but I don't know if this explains why if you query ERDDAP using
> allDatasets, you get datasetID, and if you query ERDDAP using advanced
> search , you get Dataset ID. Both are returned as csv.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#14 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ABarOED9x_EiHcnzqq3IBaM9pSs7y3rtks5s9X7YgaJpZM4Qz1wv>
> .
>
--
Sincerely,
Bob Simons
IT Specialist
Environmental Research Division
NOAA Southwest Fisheries Science Center
99 Pacific St., Suite 255A (New!)
Monterey, CA 93940 (New!)
Phone: (831)333-9878 <(831)%20333-9878> (New!)
Fax: (831)648-8440 <(831)%20648-8440>
Email: ***@***.***
The contents of this message are mine personally and
do not necessarily reflect any position of the
Government or the National Oceanic and Atmospheric Administration.
<>< <>< <>< <>< <>< <>< <>< <>< <><
--
Sincerely,
Bob Simons
IT Specialist
Environmental Research Division
NOAA Southwest Fisheries Science Center
99 Pacific St., Suite 255A (New!)
Monterey, CA 93940 (New!)
Phone: (831)333-9878 (New!)
Fax: (831)648-8440
Email: bob.simons@noaa.gov
The contents of this message are mine personally and
do not necessarily reflect any position of the
Government or the National Oceanic and Atmospheric Administration.
<>< <>< <>< <>< <>< <>< <>< <>< <><
|
I was actually expecting you to say this: better to have a minor imperfection than break people's code. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you query ERDDAP using
allDatasets
, dataset ID is returned asdatasetID
.If you query ERDDAP using advanced search , dataset ID is returned as
Dataset ID
.Is there a reason for this?
It's not a big deal, but it messed me up for a bit when writing my little ERDDAP time series explorer.
To pull the lon/lat values from the allDatasets table that matched the datasets returned from advanced search, I needed to do:
https://github.com/reproducible-notebooks/ERDDAP_timeseries_explorer/blob/master/ERDDAP_timeseries_explorer.py#L214
The text was updated successfully, but these errors were encountered: