You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: geography/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -101,7 +101,7 @@ Placeholder -- link to schema to be added later.
101
101
|`description`| String | Optional | Detailed description of geography |
102
102
|`geography_type`| String | Optional | Type of geography, e.g. `municipal_boundary` or `council_district` or custom text. See [Geography Types](#geography-types). |
103
103
|`geography_id`| UUID | Required | Unique ID of geography |
104
-
|`geography_json`|UUID| Required | The GeoJSON that defines the geographical coordinates. |
104
+
|`geography_json`|JSON| Required | The GeoJSON that defines the geographical coordinates. |
105
105
|`effective_date`|[timestamp][ts]| Optional | The date at which a Geography is considered "live". Must be at or after `published_date`. |
106
106
|`published_date`|[timestamp][ts]| Required | Time that the geography was published, i.e. made immutable |
107
107
|`retire_date`|[timestamp][ts]| Optional | Time that the geography is slated to retire. Once the retire date is passed, new policies can no longer reference it and old policies referencing it should be updated. Retired geographies should continue to be returned in the geographies list. Must be after `effective_date`. |
0 commit comments