Skip to content
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

grid.json storage #27

Closed
calvinmetcalf opened this issue Feb 3, 2012 · 4 comments
Closed

grid.json storage #27

calvinmetcalf opened this issue Feb 3, 2012 · 4 comments

Comments

@calvinmetcalf
Copy link

exactly how the grids are stored in the file is not clearly defined making attempts at mbtile implementation which include grids difficult.

As far as I can tell they are spread across 3 fields in 2 views, with "keys":{ and "grid"{ including in the database but but "data":{ and grid( not plus 1 of the 3 fields is gziped.

@tmcw
Copy link
Contributor

tmcw commented Feb 3, 2012

Hmm, we could expand the specification a bit more in that direction, but the optimizations in most of the MBTiles implementations are outside of the spec - only the interface is specified exactly, not the views or anything like that. Views are a transparent way of compressing both tile & grid data (in pretty much the same way).

@calvinmetcalf
Copy link
Author

the non intuitive thing is just how you have to query 3 fields and put them together for the grids but not the tiles.

@tmcw
Copy link
Contributor

tmcw commented Feb 3, 2012

You mean with the views? As far as TileMill output, it's views for both grids and images.

@calvinmetcalf
Copy link
Author

oh sorry for the confusion, the fact that they are views not fields isn't an issue, the fact that to access the tile.json you have to querry grid field in the grids view plus key_name and key_json from grid_data and put them together is the confusing part

@tmcw tmcw closed this as completed in 2b82d81 Feb 25, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants