file-geocoder
Advanced tools
Comparing version 0.3.4 to 0.3.5
{ | ||
"name": "file-geocoder", | ||
"version": "0.3.4", | ||
"version": "0.3.5", | ||
"description": "Geocodes a file (JSON or CSV). Requires a Google-style geocoder.", | ||
@@ -5,0 +5,0 @@ "repository": "https://github.com/gabrielflorit/file-geocoder.git", |
@@ -17,3 +17,3 @@ file-geocoder | ||
file-geocoder adds several geocoding fields ([what's the deal with GeocodeAdminAreaLevel1?](https://developers.google.com/maps/documentation/geocoding/#Types "Address Component Types")): | ||
**file-geocoder** adds several geocoding fields ([what's the deal with GeocodeAdminAreaLevel1?](https://developers.google.com/maps/documentation/geocoding/#Types "Address Component Types")): | ||
@@ -50,3 +50,3 @@ ``` | ||
#### Your laptop battery died before the geocoder finished. No problem. file-geocoder stores its work on a .db file. Let's resume the geocoding: | ||
#### Your laptop battery died before the geocoder finished. No problem. **file-geocoder** stores its work on a .db file. Let's resume the geocoding: | ||
```sh | ||
@@ -66,1 +66,5 @@ file-geocoder \ | ||
npm install file-geocoder -g | ||
## Notes | ||
**file-geocoder** imports the JSON/CSV file to a [NeDB](https://github.com/louischatriot/nedb "NeDB") datastore before geocoding. For performance reasons, NeDB [keeps a copy of the whole database in memory](https://github.com/louischatriot/nedb "Memory footprint"). In other words, **file-geocoder** is a memory hog. If the JSON file is 1GB, you better have at least that much RAM. |
Sorry, the diff of this file is not supported yet
10186
68