Skip to content

Commit

Permalink
Update catalog-spec/catalog-spec.md
Browse files Browse the repository at this point in the history 
Co-authored-by: Pete Gadomski <[email protected]>
  • Loading branch information
@emmanuelmathot @gadomski
emmanuelmathot and gadomski authored Jul 9, 2024
1 parent 29e0a92 commit 2b73fcc
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion catalog-spec/catalog-spec.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,7 @@ The following types are commonly used as `rel` types in the Link Object of a STA
| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- |
| self | STRONGLY RECOMMENDED. *Absolute* URL to the location that the Catalog file can be found online, if available. This is particularly useful when in a download package that includes metadata, so that the downstream user can know where the data has come from. | application/json |
| root | STRONGLY RECOMMENDED. URL to the root STAC entity (Catalog or [Collection](../collection-spec/README.md)). Catalogs should include a link to their root, even if it's the root and points to itself. ONLY ONE link with `root` relationship and `application/json` type is allowed. Other version of the root link can be added with different `type` field as long as they point the same conceptual entity (e.g. identified by the ID). | application/json |
| parent | URL to the parent STAC entity (Catalog or [Collection](../collection-spec/README.md)). Non-root Catalogs should include a link to their parent. ONLY ONE link with `parent` relationship and `application/json` type is allowed. Other version of the parent link can be added with different `type` field as long as they point the same conceptual entity (e.g. identified by the ID). | application/json |
| parent | URL to the parent STAC entity (Catalog or [Collection](../collection-spec/README.md)). Non-root Catalogs should include a link to their parent. ONLY ONE link with `parent` relationship and `application/json` type is allowed. Other versions of the parent link can be added with different `type` field as long as they point the same conceptual entity (e.g. identified by the ID). | application/json |
| collection | URL to a parent [Collection](../collection-spec/README.md). *Absolute* URLs should be used whenever possible. The referenced Collection is STRONGLY RECOMMENDED to implement the same STAC version as the Catalog. A link with this `rel` type is *required* if the `collection` field in properties is present. | application/json |
| child | URL to a child STAC entity (Catalog or [Collection](../collection-spec/README.md)). | application/json |
| item | URL to a STAC Item. | application/geo+json (preferred) or application/json |
Expand Down

0 comments on commit 2b73fcc

Please sign in to comment.