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: README.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,17 +25,18 @@ Importing the library
25
25
>>>import censusbatchgeocoder
26
26
```
27
27
28
-
According to the [official Census documentation](https://www.documentcloud.org/documents/3894452-Census-Geocoding-Services-API.html), the input file is expected to contain a comma-delimited list of addresses, without a header, segmented into the following fields.
28
+
According to the [official Census documentation](https://www.documentcloud.org/documents/3894452-Census-Geocoding-Services-API.html), the input file is expected to contain a comma-delimited list of addressessegmented into the following fields:
29
29
30
-
* Your unique identifier for the record
31
-
* Structure number and street name (required)
32
-
* City name (optional)
33
-
* State (optional)
34
-
* ZIP Code (optional)
30
+
*``id``: Your unique identifier for the record
31
+
*``address``: Structure number and street name (required)
32
+
*``city``: City name (optional)
33
+
*``state``: State (optional)
34
+
*``zipcode``: ZIP Code (optional)
35
35
36
36
An example could look like this:
37
37
38
38
```text
39
+
id,address,city,state,zipcode
39
40
1,1600 Pennsylvania Ave NW,Washington,DC,20006
40
41
2,202 W. 1st Street,Los Angeles,CA,90012
41
42
```
@@ -73,7 +74,8 @@ Geocoding a comma-delimited file from the filesystem. Results are returned as a
0 commit comments