Closed EliVolsch closed 8 months ago
Hi @EliVolsch, I'm facing some issues here when I'm uploading STAC metadata (yaml). I have tested the files using a stac-validator. We can discuss it on our meeting.
Sure we can. If you can please also provide a description of your problem here for reference. Then we can debug in the meantime as well
JSON file and YAML fies is workin need to test XML file
on the metadata capture ui some fields are mandatory to a specific metadata standard(SANS 1878). However the system will not allow a user to add a different metadata format(STAC) if those fields are empty. A warning message in needed in this case. Input N/A
Here if didn't specify a correct STAC specification, the system will our an error. Some STAC validators are able to automatically detect the STAC specification from a file or URL. Which STAC validator is being implemented on SAEOSS?
@voogt @EliVolsch
Hi @Indiphile the stac does not automatically detect which type of stac it is from a file, thats why I've added the dropdown to select the correct option. From there it validates the stac against a json file that can be found at https://github.com/radiantearth/stac-api-spec/blob/release/v1.0.0/stac-spec/item-spec/json-schema/item.json
Hi @voogt, yes you are right the stac from Radiant Earth doesn't detect stac type(there online tool . Take a look here. Feel free to send me an email for a testing session.
Hi @Indiphile thanks for the link! I will take a look at their tool
Hi @Indiphile I've updated the validation tool. Can you take a look at this PR https://github.com/kartoza/SAEOSS-Portal/pull/251 please?
Users requires a universally understandable and human readable interface to input metadata irrespective of the underlying metadata format and file type. This user facing interface should allow the user to ingest, view and modify partial or complete geospatial metadata documents in human-readable formats or in the following well-known file formats:
a. XML b. JSON c. YAML
Expectation: