-
Notifications
You must be signed in to change notification settings - Fork 119
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
Expiry and diff support #118
Comments
We also fall into the group of providers that render the full planet, and then re-generate dirty tiles. We don't have much in the way of documenting how all the services talk to each other, but we do have a vagrant image that should demonstrate how all the pieces fit together, in a purely local setting. I added some details to the vector-datasource wiki page you linked to, and the vagrant image repository can be found here: |
We do use osm2pgsql's tile expiry list. We can add that info to the docs. |
I thought tilestache didn't support "dirty" tiles and had no concept of serving old data that it knew to be outdated? |
Right - we are just using TileStache as the web server to generate the tiles. They are then stored in S3 + Fastly (in our install, could use other services in place of those), and the actual expiry and re-render process is handled outside of TileStache. @rmarianski will have more info :) |
Yup, that's correct. When osm2pgsql applies the update, we ask it to generate an expiry list, which we enqueue onto a work queue (sqs). That work is pulled off, and processed by a tool called tilequeue. That tool also handles enqueueing the work itself from the expiry list. |
I would open this at https://github.com/mapzen/TileStache, but it doesn't have tickets, and this is sort of a higher level question.
OSM data differs from other data in that it can be updated minutely. How is expiry of vector tiles handed in vector-datasource? The traditional raster stacks use a notion of a "dirty" tile that is rendered but not up to date. There are no public vector tile stacks with full diff support, but some providers are rendering the entire planet, then re-rendering any dirty tiles.
https://github.com/mapzen/vector-datasource/wiki/Mapzen-Vector-Tile-Service makes no reference to diffs, including reading them with osm2pgsql.
The text was updated successfully, but these errors were encountered: