-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rawr + Metatile generation assistance #1537
Comments
Apologies for the confusion! We've changed how this works a few times, and we're still settling into a stable and documented way to do tile generation. A lot of this is still work in progress while we iterate towards something more automated. You understand correctly about the split between low ( An outline of the process is:
For the database, we use AWS RDS, and "replicate" by taking a snapshot and starting several servers from the snapshot. For the tile generation (RAWR, high and low meta), we use AWS Batch. Tiles are stored in AWS S3 buckets. Although all the logic in Hope that helps! |
Thanks! do you have a ecs app that runs the tileops scripts to orchestra the jobs? |
At the moment, we've just been running the scripts from our laptops. It's not ideal, and hopefully at some point soon we'll bundle the "control" parts into a container which can be kicked off and monitored from a web page. The |
So as I understand, using the rawr-tile job, means to enqueue the job (manually? with a loop?) with all of the tiles that would be in the sqs? would running |
The Making RAWR tiles through Batch + |
Please let us know if you have any other questions with a new issue :) |
I'm having trouble understanding the flow of commands needed to produce metatiles.
tileserver runs successfully, serving tiles from either tile store (local folder via
tilequeue process
) or directly from postgres.From what I understand (and please correct me where I'm wrong):
once data is in postgres, there are 2 flows:
for zoom <= 10, the tiles generation would be either with batch or on-demand to generate, store (in s3 or similar) and serve as is, via cdn and use caching (cdn or redis) where appropriate
for zoom > 10, rawr files needs to be created from which the tiles will be generated
rawr tiles, from what I gather, are created via its own queue (differnet from the
tilequeue process
queue) and are seeded from the TOI?tilequeue rawr-process
produces aadmin_areas relation does not exist
andtilequeue-rawr-seed-toi
explodes after some tiles due to theassert len(coords) == 1
I noticed a (undocumented) command for
metatile
andmeta-tile-low-zoom
which seems to fit the process described above but these command are a per tile commands, and do not read from a queue (which I'm not sure how the queue is populated, and by what logic and by who)thanks
The text was updated successfully, but these errors were encountered: