Stuff for the nodejs port #375
Conversation
``` $ du -sh /data 30G /data ```
disable TTY for prepare scripts to avoid unsightly buffering
Update oa, now we should use `fr/countrywide.csv`
South America Project
disable TTY for prepeare scripts to avoid unsightly buffering
Now that the Who's on First downloader defaults to using SQLite downloads and supports country-specific bundles thanks to pelias/whosonfirst#487, we can start using that new functionality. This PR sets the `imports.whosonfirst.countryCode` property appropriately across all our current projects. This should not only help make all imports quite a bit faster, but it will require much less disk space for everyone. Since we're now sponsoring the Who's on First downloads here at Geocode Earth, the bandwidth savings also make us happy :) Along the way I made a few minor changes to remove some deprecated config options like `importVenues` and `sqlite`.
Add `countryCode` property to WOF configuration
- does not contain all of NYC's transit data (subways only)
Also matches the order of importers specified in `docker-compose.yml` to the Australia project
New York City Project
Include the official data from the 3 regions (updated regurarly, full coverage) in Belgium, see also openaddresses/openaddresses#4582
Update pelias.json for Belgium
docs: add project header to readme
docs(readme): simplify quick-start docs
GitHub is deprecating Ubuntu 20 based runners [on April 1](https://github.blog/changelog/2025-01-15-github-actions-ubuntu-20-runner-image-brownout-dates-and-other-breaking-changes/), so we want to be off well before then. Connects pelias/pelias#951
CI: update Github Action runner Ubuntu versions to 22.04
…pose fix(australia): remove duplicate `csv-importer` service from docker-compose.yml
|
Hi @arnesetzer this isn't a priority for us at the moment and has the potential to be a fairly disruptive change as it would require everyone to change their workflow. I'm not sure what your plans are for this, is it for personal use or would you like to get it merged at some point? |
My current pre-processing setup is a bit of a mess to be honest. I was looking for a way to clean it up and found this old PR. I thought this suite would be perfect for my needs. As this is an open source project, I thought someone else might benefit from it too. I totally understand that changing the technical side of things is hard, especially since this project has grown so much since 2020, making a disruptive change even harder. If it gets merged at some point I would be happy, but I can totally understand that this change is too big to implement and that it would kill a lot of installations. |
20 participants
👋 I did some awesome work for the Pelias project and would love for everyone to have a look at it and provide feedback.
Here's the reason for this change 🚀
Here's what actually got changed 👏
Rebased on the current master branch
Make the node scripts runnable by adding
shell:trueto the options in the compose sectionAdded support for
docker composeanddocker-composeAdd some elastic commands (Rest follows)
pelias compose
pelias download (still requires some control-flow code to allow parallel downloads)
pelias import
pelias elastic
pelias prepare
pelias system
pelias test
Here's how others can test the changes 👀
../../pelias any command