Comments (7)
ok it looks like you DON'T run pelias prepare polylines
if you're using valhalla - and pelias prepare all
includes that (the pelias commands are all defined here) - so you;d do pelias prepare placeholder
and pelias prepare interpolation
, skipping the pelias prepare polylines that comes first in the definition of prepare_all
from docker.
As the author of the code in question I can tell you that it's unlikely that the algorithm I used will work for the planet regardless of how much RAM you throw at it.
You should consider these errors as fatal and follow the instructions in the warning message I left.
from docker.
Please don't use the issue tracker for general support, this case was clearly documented in the error message you provided along with a solution.
from docker.
I thought that valhalla was already being used by the docker install , having seen the ~/pelias/images/valhalla dir and dockerfile.
Sorry , my mistake .
I had added virtual memory which avoided this error but iiuc , valhalla should be used in any case.
from docker.
I tried using a valhalla-generated file (the one conveniently linked to here) , putting
"imports": {
....
"polyline": {
"datapath": "/data/polylines",
"files": [ "road_network.polylines" ]
},
....
into ~/pelias/projects/planet/polylines/pelias.json after putting the unzipped/renamed polylines file at /tmp/pelias/planet/data/polylines/road_network.polylines (my DATA_DIR being /tmp/pelias/planet/data), ran pelias elastic stop
, nuked the directory /tmp/pelias/planet/data/elasticsearch , and tried the install from start
, wait
, create
, prepare
but after prepare I still get the valhalla warning and see
converting /data/openstreetmap/planet-latest.osm.pbf to /data/polylines/extract.0sv
which was the previously-used polylines file . Is this expected ?
Trying again with pelias compose down
does remove the elasticsearch index , preventing an 'index exists' message on pelias elastic start
(I since realize that pelias elastic remove
will take care of removing a partially-built index) but otherwise the same - the valhalla msg appears and an extract.0sv starts getting built. Those msgs are generated by polylines:docker_extract.sh, called by prepare_polylines()
(in turn called by pelias prepare all
) for any pbf over 1Gb so I hope I am still on the right track - conceivably, one should only run the prepare steps other than prepare_polylines() if a polylines file is being supplied?
from docker.
Suggestion: Why not roll valhalla into pelias as a dependency, and when a file is too large, pelias' prepare script could execute the valhalla scripts for you.
from docker.
FYI I just added this 3 days ago https://github.com/pelias/docker-valhalla-baseimage
from docker.
Related Issues (20)
- s it possible to point the docker services(api, interpolation, libpostal) to a running elasticsearch cluster instead of your pelias-elasticsearch docker service ? HOT 5
- OpenAddress data missing in local Pelias build HOT 17
- Throw error if pelias.json is not configured correctly HOT 2
- ECONNREFUSED, address ::1
- pelias download osm/all is failed HOT 4
- unable to locate sqlite folder HOT 6
- host user running docker requires UID of 1000 for elasticsearch HOT 10
- inherent limit on OSM ID bit range? HOT 1
- "pelias elastic start" command is successful only for user 1001 HOT 3
- FATAL ERROR: 138 regression(s) detected. HOT 2
- Failed to download openaddresses data for Belgium, Luxembourg & The Netherlands HOT 5
- Geocode-Dashboard shows 400+ countries HOT 5
- `label` only consists of place `name` in the responses of `search`, `autocomplete` endpoints. HOT 6
- Unable to install Pelias HOT 8
- "docker compose up" leads to incorrect state - Pelias API depends on Elasticsearch HOT 10
- Planet Build for Download wof and osm failing. HOT 5
- No support for docker compose v2 HOT 2
- pelias_api stopped running, exit code 126 HOT 35
- access log of pelias container not found HOT 6
- Pelias search returns full features from localhost but features become empty when I send request using public IP.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from docker.