Merge pull request #69 from radiantearth/fix-54

Fix #54

STAC-extensions.yaml

@@ -1576,7 +1576,7 @@ components:
       type: object
       properties:
         datetime:
-          $ref: '#/components/schemas/datetime'
+          $ref: '#/components/schemas/datetime_interval'
     intersectsFilter:
       type: object
       description: Only returns items that intersect with the provided polygon.
@@ -1603,22 +1603,45 @@ components:
           $ref: '#/components/schemas/collectionsArray'
     datetime:
       type: string
-      description: |-
+      format: date-time
+      nullable: true
+      description: >-
+        The searchable date and time of the assets, in UTC.
+
+        It is formatted according to [RFC 3339, section
+        5.6](https://tools.ietf.org/html/rfc3339#section-5.6).
+
+        `null` is allowed, but requires `start_datetime` and `end_datetime` from
+        common metadata to be set.
+      example: '2018-02-12T00:00:00Z'
+    datetime_interval:
+      type: string
+      description: >-
         Either a date-time or an interval, open or closed. Date and time
-        expressions adhere to RFC 3339. Open intervals are expressed using
-        double-dots.
+        expressions
+
+        adhere to RFC 3339. Open intervals are expressed using double-dots.
+
 
         Examples:
 
+
         * A date-time: "2018-02-12T23:20:50Z"
+
         * A closed interval: "2018-02-12T00:00:00Z/2018-03-18T12:31:12Z"
+
         * Open intervals: "2018-02-12T00:00:00Z/.." or "../2018-03-18T12:31:12Z"
 
+
         Only features that have a temporal property that intersects the value of
+
         `datetime` are selected.
 
+
         If a feature has multiple temporal properties, it is the decision of the
+
         server whether only a single temporal property is used to determine
+
         the extent or all relevant temporal properties.
       example: '2018-02-12T00:00:00Z/2018-03-18T12:31:12Z'
     stac_version:

STAC.yaml

@@ -1279,7 +1279,7 @@ components:
       type: object
       properties:
         datetime:
-          $ref: '#/components/schemas/datetime'
+          $ref: '#/components/schemas/datetime_interval'
     intersectsFilter:
       type: object
       description: Only returns items that intersect with the provided polygon.
@@ -1306,22 +1306,45 @@ components:
           $ref: '#/components/schemas/collectionsArray'
     datetime:
       type: string
-      description: |-
+      format: date-time
+      nullable: true
+      description: >-
+        The searchable date and time of the assets, in UTC.
+
+        It is formatted according to [RFC 3339, section
+        5.6](https://tools.ietf.org/html/rfc3339#section-5.6).
+
+        `null` is allowed, but requires `start_datetime` and `end_datetime` from
+        common metadata to be set.
+      example: '2018-02-12T00:00:00Z'
+    datetime_interval:
+      type: string
+      description: >-
         Either a date-time or an interval, open or closed. Date and time
-        expressions adhere to RFC 3339. Open intervals are expressed using
-        double-dots.
+        expressions
+
+        adhere to RFC 3339. Open intervals are expressed using double-dots.
+
 
         Examples:
 
+
         * A date-time: "2018-02-12T23:20:50Z"
+
         * A closed interval: "2018-02-12T00:00:00Z/2018-03-18T12:31:12Z"
+
         * Open intervals: "2018-02-12T00:00:00Z/.." or "../2018-03-18T12:31:12Z"
 
+
         Only features that have a temporal property that intersects the value of
+
         `datetime` are selected.
 
+
         If a feature has multiple temporal properties, it is the decision of the
+
         server whether only a single temporal property is used to determine
+
         the extent or all relevant temporal properties.
       example: '2018-02-12T00:00:00Z/2018-03-18T12:31:12Z'
     stac_version:

openapi/STAC.yaml

@@ -600,7 +600,7 @@ components:
       type: object
       properties:
         datetime:
-          $ref: '#/components/schemas/datetime'
+          $ref: '#/components/schemas/datetime_interval'
     intersectsFilter:
       type: object
       description: Only returns items that intersect with the provided polygon.
@@ -625,13 +625,20 @@ components:
       properties:
         collections:
           $ref: '#/components/schemas/collectionsArray'
-    # - OAFeat.yaml#/components/parameters/datetime 
     datetime:
+      type: string
+      format: date-time
+      nullable: true
+      description: |-
+        The searchable date and time of the assets, in UTC.
+        It is formatted according to [RFC 3339, section 5.6](https://tools.ietf.org/html/rfc3339#section-5.6).
+        `null` is allowed, but requires `start_datetime` and `end_datetime` from common metadata to be set.
+      example: '2018-02-12T00:00:00Z'
+    datetime_interval:
       type: string
       description: |-
-        Either a date-time or an interval, open or closed. Date and time
-        expressions adhere to RFC 3339. Open intervals are expressed using
-        double-dots.
+        Either a date-time or an interval, open or closed. Date and time expressions
+        adhere to RFC 3339. Open intervals are expressed using double-dots.
 
         Examples: