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

Feature Request: add base mbtiles to catalog #34

Open
tim-moody opened this issue Oct 6, 2020 · 7 comments
Open

Feature Request: add base mbtiles to catalog #34

tim-moody opened this issue Oct 6, 2020 · 7 comments

Comments

@tim-moody
Copy link

map-catalog.json contains all the installable regions in a list named maps.

It would be nice if other prerequisite or base mbtiles were also in the catalog to make managing their urls easier. This could be done either by adding them to the existing maps list and then adding a property that the user interface could use to distinguish between maps the should be displayed in the download list and those that should not or by adding a top level list parallel to maps that contains base mbtiles.

The tiles in question are:

  • osm-planet_z0-z10_2019.mbtiles
  • planet_z0-z6_2019.mbtiles
  • satellite_z0-z6_v3.mbtiles
  • satellite_z0-z9_v3.mbtiles
@georgejhunt
Copy link
Contributor

georgejhunt commented Oct 6, 2020 via email

@tim-moody
Copy link
Author

I think a separate base list makes sense.

Also, I'm not clear on the relationship between and meaning of

"osm_size": "10099986432"
"sat_size": "976416768"
"size": 5940756480

is any of these the size of the actual mbtiles file and if not can we have that?

@georgejhunt
Copy link
Contributor

georgejhunt commented Oct 6, 2020 via email

@tim-moody
Copy link
Author

I put comments on #36

tangentially do these space requirements seem right? I need them for estimated space calculations if the user elects to download a set of satellite images:

100 x 100 km ~ 5 MB ~ 5 min download
300 x 300 km ~ 50 MB ~ 0.5 hour download
1000 x 1000 km ~ 500 MB ~ 5 hour download

sort of estimated size in MB = 5 * (radius/50)^2. maybe round to nearest MB so as not to promise too much precision.

@holta
Copy link
Member

holta commented Oct 7, 2020

Yes those space & time estimates were carefully measured & revised 10 days ago.

Sometimes the space varies by 2X (depending on the imagery complexity/compressibility in that part of the world) so again these are about the very best approximations we can provide.

Note the times are extremely consistent, due to Sentinel Cloudless' ~300 kbit/s speed cap.

@georgejhunt
Copy link
Contributor

georgejhunt commented Oct 7, 2020 via email

@tim-moody
Copy link
Author

not sure this ticket is still relevant

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

3 participants