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
+37-37Lines changed: 37 additions & 37 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,12 +11,12 @@ Geographical data will be stored as GeoJSON and read from either `geographies.js
11
11
## Table of Contents
12
12
13
13
*[General Information](#general-information)
14
-
*[Versioning](#versioning)
15
-
*[Transition from Policy](#transition-from-policy)
14
+
*[Versioning](#versioning)
15
+
*[Transition from Policy](#transition-from-policy)
16
16
*[Distribution](#distribution)
17
-
*[Flat Files](#flat-files)
18
-
*[Response Format](#response-format)
19
-
*[Authorization](#authorization)
17
+
*[Flat Files](#flat-files)
18
+
*[Response Format](#response-format)
19
+
*[Authorization](#authorization)
20
20
*[Schema](#schema)
21
21
*[Geography Fields](#geography-fields)
22
22
*[Previous Geographies](#previous-geographies)
@@ -45,7 +45,7 @@ Versioning must be implemented as specified in the [Versioning section][versioni
45
45
46
46
To ensure this Geography API is not creating a breaking change for the 1.1.0 release, it's expected that the data contained in the [`/geographies`](/policy#geography) endpoint in the Policy API is identical to this Geography API. This will ensure that when a Geography ID is used anywhere in this release, the data could be retrieved from either location.
47
47
48
-
This temporary requirement is to ensure backwards compatibility, but the overall intent is to remove the /policy/geographies endpoint at the next major MDS release.
48
+
This temporary requirement is to ensure backwards compatibility, but the overall intent is to remove the /policy/geographies endpoint at the next major MDS release.
49
49
50
50
[Top][toc]
51
51
@@ -65,7 +65,7 @@ Geographies should be re-fetched at an agreed upon interval between providers an
65
65
66
66
To use a flat file, geographies shall be represented in one (1) file equivalent to the /geographies endpoint:
67
67
68
-
-`geographies.json`
68
+
*`geographies.json`
69
69
70
70
The files shall be structured like the output of the [REST endpoints](#rest-endpoints) above.
71
71
@@ -89,7 +89,7 @@ Authorization is not required. An agency may decide to make this endpoint unauth
89
89
90
90
## Schema
91
91
92
-
Link to schema will be defined and added in a future release.
92
+
See the [Endpoints](#endpoints) below for links to their specific JSON Schema documents.
93
93
94
94
[Top][toc]
95
95
@@ -115,6 +115,8 @@ Obsoleting or otherwise changing a geography is accomplished by publishing a new
115
115
116
116
This field is optional can be omitted by the publishing Agency.
117
117
118
+
[Top][toc]
119
+
118
120
### Geography Type
119
121
120
122
Type of geography. These specific types are recommendations based on ones commonly defined by agencies. Others may be created by the Agency as needed, or the optional `geography_type` field may be omitted.
@@ -148,16 +150,17 @@ Type of geography. These specific types are recommendations based on ones common
148
150
Note: to use flat files rather than REST endpoints, Geography objects should be stored in `geographies.json`. The `geographies.json` file will look like the output of `GET /geographies`.
149
151
150
152
Example `geographies.json`
151
-
```json
153
+
154
+
```jsonc
152
155
{
153
-
"version": "1.1.0",
156
+
"version":"1.2.0",
154
157
"updated":"1570035222868",
155
158
"geographies": [
156
159
{
157
-
// GeoJSON 1
160
+
//Geography 1
158
161
},
159
162
{
160
-
// GeoJSON 2
163
+
//Geography 2
161
164
}
162
165
]
163
166
}
@@ -173,26 +176,26 @@ The Geography Author API consists of the following endpoints:
0 commit comments