-
Notifications
You must be signed in to change notification settings - Fork 6
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
Please clarify the use of osm_size within the code base. [& discussion of init.json browser viewport, centered on lat/long + zoom-level] #60
Comments
The last remaining small issue is this noted error
This file does exist in iiab but is not installed. |
That looks like the lat/long viewport, so browsers showcase the most recently installed continent/region (centering & framing its green rectangle within your browser) e.g. whenever a new person visits http://box/maps So init.json is probably intended to be missing on fresh IIAB software installs — until a continent/region is installed — sounds like everything is probably working fine (or am I wrong?) |
General context, just in case others run into this ticket — and want to learn a bit more about IIAB's map catalog(s) — that currently contain info about 14 .mbtiles files for world continents and similar regions: https://github.com/iiab/iiab/wiki/IIAB-Maps#how-do-i-upgrade-an-iiab-map-pack Most of these are OpenStreetMap (OSM) vector map files, but there is one exception at the moment — i.e. the 1.2 GB satellite_z0-z9_2020.mbtiles is also included in the catalog(s). Just FYI current file sizes are here: |
Yes, it is used for custom focus when you visit the page with the contents below the map will roughly center on Winnipeg with a zoom of 8
Installed the base map set and this file does not exist, should it? or maybe as a init.json.example to use as a guide? The ability gained by it's presents is a great customization, any plans to add editable lat lon and zoom fields for init.json to admin-console? |
This issue has 3 or 4 distinct items. Is this the last standing one? init.json is created when a maptile set is added so as to put focus on its region. It's true that a dummy could be installed that would put focus on the center of the world if someone cares to say what that is. I think the current code does that in the absence of the file. |
Ok init.json shows up once one of the z11+ mbtiles are installed, still would be nice to be able to tweak the focus at some point later. Is there a hint to this ability? I might of glossed over it in the docs.. |
This is a good idea. I've started a Customizations section here: |
Above Customizations expanded. Pointing implementers in the right direction to modify the green rectangles (for continents/regions) and yellow squares (for satellite photos) e.g. if they need to fine-tune those colors to show suitable contrast against the vegetation (or lack thereof) in their part of the world. |
https://github.com/iiab/maps/blob/master/2020/map-catalog.json no osm_size has 2020 entries
https://github.com/iiab/iiab-admin-console/blob/master/roles/common/files/map/adm-map-catalog.json no osm_size has 2020
What is the significance of "seq" below and these 2 versions are so close could they be unified going forward?
http://download.iiab.io/content/OSM/vector-tiles/map-catalog.json has osm_size has 2019 entries
https://github.com/iiab/maps/blob/master/osm-source/jupyter-code/README.md
I get the impression that osm_size is going/gone away and just using 'size' 'mbtile_size' only now in map-catalog.json?
These tools mention osm_size:
https://github.com/iiab/maps/blob/master/osm-source/jupyter-code/maps.ipynb has 4 mentions of osm_size, one within what looks to be a python traceback.
https://github.com/iiab/maptools/search?q=osm_size
Other mentions of osm_size https://github.com/iiab/maps/search?&q=osm_size
The text was updated successfully, but these errors were encountered: