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.

Sign up for GitHub

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

add type to asset #175

Merged
merged 2 commits into from
Aug 15, 2018
Merged

add type to asset #175

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5fd8529
add type to asset
jeffnaus Aug 15, 2018
4bde46c
removed formats from catalog md
jeffnaus Aug 15, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion json-spec/json-schema/stac-item.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -137,14 +137,18 @@
"asset": {
"type": "object",
"required": [
"href"
"href",
"mime_type"
],
"properties": {
"href": {
"type": "string"
},
"name": {
"type": "string"
},
"mime_type": {
"type": "string"
}
}
},
Expand Down
9 changes: 6 additions & 3 deletions json-spec/json-spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,9 +76,12 @@ as any 'sidecar' files that are related and help a client make sense of the data
JSON, etc), unusable data masks, satellite ephemeris data, etc. Some assets (like Landsat data) are represented by multiple files -
all should be linked to. It is generally recommended that different processing levels or formats are not exhaustively listed in an
`Item`, but instead are represented by related `Items` that are linked to, but the best practices around this are still emerging.
An asset object currently just requires a href field, which can be a relative or absolute link, to provide a link to the
asset for download or streaming access. The 'name' field is optional, and is generally the display name for clients & users.
The asset definition will likely evolve soon to be able to explain itself more.

***Assets required fields***
asset for download or streaming access. The 'name' field is optional, and is generally the display name for clients & users.
* href - link to the asset object. The link can be a relative or absolute link The asset definition will likely evolve soon to be able to explain itself more.
* mime_type - the mime type of the object. Prefered that standard mime types be used when possible. Type can include; image/geotiff, image/geotiff+cog, or type with a vendor prefix, example: vnd.digitalglobe/til
****We would like to register image/geotiff as a mime type with IANA****

**thumbnail** is a special *strongly recommended* `asset` that is a downsampled image of the core asset, for direct display online in a web page or
interactive search application. Even assets that are less easily translated in to a visual image should provide some visual representation,
Expand Down
2 changes: 0 additions & 2 deletions static-catalog/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,8 +79,6 @@ _"Root" Catalog_
"url": "https://www.fsa.usda.gov/programs-and-services/aerial-photography/imagery-programs/naip-imagery/"
},

"formats": ["geotiff", "cog"],

"keywords": ["aerial"],
"homepage": "http://wherever",

Expand Down
7 changes: 0 additions & 7 deletions static-catalog/json-schema/catalog.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -107,13 +107,6 @@
"contact": {
"$ref": "#/definitions/entity"
},
"formats": {
"description": "Included asset formats",
"type": "array",
"items": {
"type": "string"
}
},
"keywords": {
"description": "Keywords",
"type": "array",
Expand Down