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

(A) "size" erroneous in map-catalog.json (B) NEW OSM dataset from Oct/Nov 2020 (C) Prep for future datasets incl Satellite Photos #3077

Closed
holta opened this issue Dec 21, 2021 · 12 comments

Comments

@holta
Copy link
Member

holta commented Dec 21, 2021

@georgejhunt

  1. Should we fix "size": 16841445376 that appears 3 times in http://download.iiab.io/content/OSM/vector-tiles/map-catalog.json which is apparently drawn from https://github.com/iiab/maps/blob/master/public/2021-01-27/map-catalog.json ?

    • Line 21 under osm-planet_z0-z10_2019.mbtiles
    • Line 47 under satellite_z0-z9_v3.mbtiles
    • Line 75 under osm_africa_z11-z14_2019.mbtiles
  2. Is 2020-10-06/modify_catalog.py the most recent and best way of doing this?

    Do you have any recommendations here, in general?

  3. In contrast, 16841445376 appears only once (on Line 124, under osm_africa_z11-z14_2019.mbtiles) in /library/www/html/common/assets/adm-map-catalog.json ~= https://github.com/iiab/iiab-admin-console/blob/master/roles/common/files/map/adm-map-catalog.json — apparently because it's auto-created by something like https://github.com/iiab/iiab-admin-console/blob/master/roles/cmdsrv/files/scripts/osm-vect_v2_finish_install.py ?

  4. NEW OpenStreetMap datasets from Oct/Nov 2020 are now posted to https://archive.org/details/osm-vector-mbtiles that we should take a look at in coming months (when we can!) in service to low-income communities worldwide and their students who will greatly benefit...

    We should lay out a rough plan for 2022 so these communities get what they want (is Sentinel satellite data...essentially auto-updated at the moment?!)

Thanks!

Historical footnote:

Tangentially related:

@holta holta added this to the 7.2 milestone Dec 21, 2021
@tim-moody
Copy link
Contributor

there are two catalogs because the osm module and adm cons do the math differently, and the difference with respect to size reflect the different math.

@holta
Copy link
Member Author

holta commented Dec 21, 2021

there are two catalogs because the osm module and adm cons do the math differently, and the difference with respect to size reflect the different math.

Thanks for context. I haven't dug into the details, but just FYI "size": 16841445376 is marked as identical in both files (all 3 + 1 = 4 cases) so this doesn't look like a math issue...?

  1. "size": 16841445376 appears 3 times in map-catalog.json
  2. "size": 16841445376 appears once at adm-map-catalog.json#L124

PS I revised the quick explanation of adm-map-catalog.json in point 3. above, and it's probably not 100% perfect (!) but hopefully at least clarifies a bit — towards helping everyone sort this all out for 2022 & Onwards.

@tim-moody
Copy link
Contributor

I'm not clear on what the issue is here. There could be as many as three.

  1. "size": 16841445376 has the wrong value

What should the value be and why do you think so? Is it just that three things probably don't have the same size?

  1. This size appears three times in one catalog and once in another

  2. The tiles files could be upgraded.

Is there also a question about synchronization between the repo and d.iiab.io?

@tim-moody
Copy link
Contributor

The last question is why does it matter?

@holta
Copy link
Member Author

holta commented Dec 21, 2021

The 3 issues in the subject line (A), (B) and (C) are to get offline communities and offline students of all kinds ready for the maps they need in 2022 and many years beyond.

Item (D) is definitely less important, but could be added as appropriate: should the stale "url" field be removed from iiab-catalog.json in future — if perhaps this information from soon-to-be-5-years-ago (perhaps) proves no longer irrelevant? An example from https://github.com/iiab/maps/blob/master/public/2021-01-27/map-catalog.json#L78 is here:

      "url": "https://archive.org/download/en-osm-omt_africa_2017-07-03_v0.23/en-osm-omt_africa_2017-07-03_v0.23.zip",

Item (E) that @tim-moody (almost but not quite!) suggests above: Should iiab-catalog.json itself possibly be hosted on GitHub, if not now, then perhaps sometime in the future? Visible versioning might greatly help field communities in future, to show lineage of different .mbtiles files and Map Pack offerings available to them each year and in recent years. (Possibly not needed in 2022? But curatorial/library-oriented implementation gurus greatly appreciate this kind of choice + transparency of this nature...if and when it's achievable!)

Item (F) can happen along the way (the social glue that holds everything together) and is implicit, and rarely talked about (until it's too late, and then "Where Are The Docs?" is suddenly the most popular question, when they don't exist...)

Specifically: which community docs and/or pipeline automation might be most important to make this quality mapmaking welcoming to new talent contributors over the coming ~5 years, helping @georgejhunt and others make this extremely valuable contribution fresh every 1-2 years or so, and for many years to come?

RECAP: Routine technical glitches can easily be solved now or in due course. At the same time, the higher-level purpose should be protecting our foundation so that in 5 years from now...the extremely useful foundation we've built over the past 5 years...is honored and disseminated increasingly broadly (and inevitably in new ways, that we cannot yet predict, as 2020 becomes 2030...)

@holta
Copy link
Member Author

holta commented Apr 28, 2022

@holta
Copy link
Member Author

holta commented Apr 29, 2022

Question(s):

@tim-moody
Copy link
Contributor

still needed?

@holta
Copy link
Member Author

holta commented Sep 21, 2022

Good enough!

@holta holta closed this as completed Sep 21, 2022
@holta holta modified the milestones: 8.1, 8.0 Sep 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants