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
Allow BBOX
to be set in .env
file
#1013
Conversation
Currently, the `BBOX` setting in `.env` is ignored for all areas except `planet`. On the other hand, the `planet` area is an overkill for any `BBOX` setting other than the default - `-180.0,-85.0511,180.0,85.0511`. With this PR, `quickstart.sh` would not override a modified `BBOX` value in `.env`. Also, this provides a way to avoid the pessimistic `BBOX` computation for `osmfr` extracts, as described in openmaptiles/openmaptiles-tools#297 (comment)
I expect this PR to work well also with the planned replacement of |
BBOX
to be set in .env
fileBBOX
to be set in .env
file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think your PR may conflict with https://github.com/openmaptiles/openmaptiles/pull/1012/files
Results evaluating commit 421e18b (merged with base 341c4df as 290d0aa). See run details. PostgreSQL DB size in MB: 2665 ⇒ 2593 (-2.7% change)
expand for details...
|
I believe there is no functional conflict between #1012 and this PR. When combined, if |
Hi @zstadler, thanks for PR. I think that the I think that change a |
Hi @TomPohys First, a confession - I'm a proud user of Unlike all other settings in the
Hopefully these PRs will be the last step in a long process of cleaning-up legacy complications, a process that began with the removal of |
Hi @zstadler, sorry for the delayed answer. I still thinking about this. It can be very confusing, that change in manual steps are now like - if there is *.bbox file, take bbox from *.bbox, if there is not *.bbox, take bbox from .env for quickstart will be like - if not an I understand, that now is not possible to change bbox for quickstart, but it works every time with the right bbox for the downloaded area. |
Hi @TomPohys, I'm not sure if your comment is about the proposed user experience or the implementation. I would like to discuss the user experience first. If we agree on the desired "what", we'll proceed to the "how". Currently
Problem statementWhile users of a Proposal
Note: - # BBOX may get overwritten by the computed bbox of the specific area:
- # make generate-dc-config
- BBOX=-180.0,-85.0511,180.0,85.0511
+ # By default, tile generation is done for the full extent of the given area.
+ # Un-comment and set BBOX below to overwrite it.
+ # BBOX=-180.0,-85.0511,180.0,85.0511 |
Hi @zstadler, thank you again. Let's use it. Change bbox for Let's keep the comment about bbox in Thanks |
Service using OpenMapTiles background
Thanks, looks good. I just change bbox site that using the OpenMapTiles background map. |
Currently, the
BBOX
setting in.env
is ignored for all areas exceptplanet
.On the other hand, the
planet
area is an overkill for anyBBOX
setting other than the default --180.0,-85.0511,180.0,85.0511
.With this PR,
quickstart.sh
would not override a modifiedBBOX
value in.env
.Also, this provides a way to avoid the pessimistic
BBOX
computation forosmfr
extracts, as described in openmaptiles/openmaptiles-tools#297 (comment)