Conversation
3nprob
force-pushed
the
misc-docs-log
branch
from
58cb178 to
c198c4f
Compare
|
|
||
| #### OpenAddresses address mappings | ||
|
|
||
| By default, a planet-wide address database is downloaded from [OpenAddresses](https://openaddresses.io/). You can supply your own addresses (for example exports from https://openaddresses.io) in either CSV or GeoJSON format. To do so, the file needs to be provided to the `openaddresses` container and configured in `csv/areas.csv`. For example: |
There was a problem hiding this comment.
By default, a planet-wide address database is downloaded
That should be true only for planet builds. Smaller builds should not include any openaddress data, unless it's been specified in the service/areas.csv. Are you seeing otherwise?
Modify
dagger/pelias.goto include your file by adding aWithFile("/data/openaddresses/myadds.geojson", p.Pelias.Headway.ServicesDir.File("myadds.geojson").line to theImportOpenAddressescontainer.
It should be sufficient to add the OpenAddress file names to the service/areas.csv (like I have for Seattle). Running the build should then download the data from OpenAddresses. It is not necessary to manually download and then edit the dagger code.
Or is there some other use case I'm not considering?
In any case, it'd be good to have this better documented, and it might be nice to encourage people to upstream any mappings they need in that file.
Long ago I actually started an experiment to dynamically download the OA data by bounding box: main...mkirk/openaddresses-downloader
...might be nice to revive that some day.
2 participants
bin/buildis very encouraging about runningk8s/bin/regenerate-all. Reword the message to make it more obvious that it is only relevant for kubernetes users.BUILD.md: Add rudimentary instructions for how to use a custom openaddresses file