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

Update thredds endpoints to return full path as URL #67

Open
roomthily opened this issue Mar 20, 2015 · 5 comments
Open

Update thredds endpoints to return full path as URL #67

roomthily opened this issue Mar 20, 2015 · 5 comments
Assignees
Labels

Comments

@roomthily
Copy link
Contributor

To get "actionable" endpoints, we need the full path and we should do this to standardize across the JSON docs. Which mostly means that we need to pass the source URL to the parsers.

@roomthily roomthily added the bug label Mar 20, 2015
@roomthily roomthily self-assigned this Mar 20, 2015
@roomthily
Copy link
Contributor Author

Magic string overlapping fun not with the ID and this is not a step forward in the world. It introduces a kind of ambiguity that is not in the FTP that it is trying to be.

@roomthily
Copy link
Contributor Author

See 01c2ff6 for the initial untethered url builder.

@roomthily
Copy link
Contributor Author

The endpoints should get dumped in the right location, JSON-wise, as well - if has_metadata, then pull those to the metadata element vs the dataset endpoints. catalogRef endpoints remain under the servce_description endpoints.

@roomthily
Copy link
Contributor Author

And need to handle the service base paths based on the access/serviceName attribute if there is one.

@roomthily
Copy link
Contributor Author

And now for something completely different:

https://rsg.pml.ac.uk/thredds/catalog-cci.xml?dataset=CCI_ALL-v1.0-MONTHLY

which returns the catalog.xml (can't ask for catalog.xml) but with query parameters and no way of knowing that.

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

No branches or pull requests

1 participant