[MCC] Unstable example for checking remote file with mcc.

[MCC] Unstable example for checking remote file with mcc.

Postby omkarr » Sat Oct 01, 2016 4:22 am


The example given in the API documentation(for checking the metadata compliance of a remote file) here [0] is not a stable example since it points to a git project here [1], which is also a metadata compliance checker and the data here changes continuously. Due to this your example remote file[2] is unstable.

A temporary solution can be pointing to a different example file in the same git project, for example this [3].
A permanent solution could be pointing to a reliable remote dataset which does not change with time.


[0] http://podaac-uat.jpl.nasa.gov/mcc/about_api
[1] https://github.com/ioos/compliance-chec ... tests/data
[2] https://github.com/ioos/compliance-chec ... im-grid.nc
[3] https://github.com/ioos/compliance-chec ... nc_file.nc
Posts: 25
Joined: Wed Jun 15, 2016 12:34 am

Return to Metadata Compliance Checker (MCC)