maps
maps copied to clipboard
iiab
Feature Request: add base mbtiles to catalog
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
I like that idea. I think that a base list beside maps list will require fewer changes to existing programs. I'll start working on it today. But the testing will take at least until Thursday.
On Tue, Oct 6, 2020 at 5:28 AM Tim Moody [email protected] wrote:
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
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/iiab/maps/issues/34, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOTQHA3XQRO65CTWOVZOJ3SJMENNANCNFSM4SF6RO4Q .
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?
see https://github.com/iiab/maps/pull/36. I think this needs to be merged, but I want your input first.
On Tue, Oct 6, 2020 at 10:09 AM Tim Moody [email protected] wrote:
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?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
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.
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.
That seems fine to me.
On Wed, Oct 7, 2020 at 6:39 AM Tim Moody [email protected] wrote:
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.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.