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

Caching not creating files v0.19.0 is working. BUT master / v0.20.0 is NOT working. #997

Closed
spreeker opened this issue Jul 3, 2024 · 9 comments

Comments

@spreeker
Copy link

spreeker commented Jul 3, 2024

tag v 20 out put run:
((v0.20.0))> ./tegola cache seed --log-level INFO --concurrency 3 --overwrite --min-zoom 13 --max-zoom 16 --config /home/stephan/work/cdfopen/tegola-config/config_gasverbruik_2024_06.toml --bounds "3.011234,50.16669,7.64906,54.683876"

2024-07-03 12:01:53 [INFO] config.go:406: loading local config (/home/stephan/work/cdfopen/tegola-config/config_gasverbruik_2024_06.toml) 2024-07-03 12:01:53 [INFO] providers.go:82: registering provider(type): cdf (mvt_postgis) 2024-07-03 12:01:53 [INFO] seed_purge.go:194: zoom list: [13 14 15 16] 2024-07-03 12:01:53 [INFO] worker.go:94: seeding map (kvenergie202406v1) tile (13/4096/4095) took: 5ms 2024-07-03 12:01:53 [INFO] cache.go:213: waiting for workers to finish up 2024-07-03 12:01:53 [INFO] worker.go:94: seeding map (kvenergie202406v1) tile (16/32768/32767) took: 1ms 2024-07-03 12:01:53 [INFO] worker.go:94: seeding map (kvenergie202406v1) tile (14/8192/8191) took: 14ms 2024-07-03 12:01:53 [INFO] worker.go:94: seeding map (kvenergie202406v1) tile (15/16384/16383) took: 15ms 2024-07-03 12:01:53 [INFO] cache.go:223: all workers are done 2024-07-03 12:01:53 [INFO] provider.go:289: cleaning up providers 2024-07-03 12:01:53 [INFO] postgis.go:1039: cleaning up postgis providers
`

So like 5 tiles are generated and nothing else.

in v0.19.0:

all tiles are generated. So what changed?

@spreeker
Copy link
Author

spreeker commented Jul 3, 2024

after commit 64729d1 cache seed of files stopped working for me.

@iwpnd
Copy link
Member

iwpnd commented Jul 3, 2024

if im reading this correctly it is because the seed function was changed to default to webmercator as of this change for whatever reason. so in your case its trying to determine the tiles on a 3857 grid but with 4326 input bounds. You should be able to confirm this by reprojecting your input bounds to webmercator and retry, I thiiiink?

@spreeker
Copy link
Author

spreeker commented Jul 3, 2024

I'm not allowed to give input bounds via the cli other then 4326 i think.

/tegola cache seed --log-level INFO --overwrite --min-zoom 8 --max-zoom 13 --config /home/stephan/work/cdfopen/tegola-config/config_gasverbruik_2024_06.toml --bounds "293518.1886,6555239.5457,847533.7696,7136160.9607"

invalid lng value(293518.1886) for bounds (293518.1886,6555239.5457,847533.7696,7136160.9607)

I used http://bboxfinder.com/#50.625073,2.636719,53.820112,7.613525 for the bbox.

@iwpnd
Copy link
Member

iwpnd commented Jul 3, 2024

oh right, the cli has validation. 🤔

hm, i wanna get this confirmed by @ARolek or @gdey if my suspicion is correct.

@gdey
Copy link
Member

gdey commented Jul 3, 2024

I'll take a look at this tomorrow.

@gdey
Copy link
Member

gdey commented Jul 4, 2024

Okay, I was able to create a quick test case for this. I'm digging into it. I think you are correct @iwpnd . Need to dig into why we made such a change. Looks like most of the .20 issues are from the upgrade. I'll keep people posted as I find out more.

@ARolek
Copy link
Member

ARolek commented Jul 20, 2024

Note, @gdey is working on a fix in the geom/slippy package that should address this issue. A PR will be ready soon and then we can do some testing.

@gdey
Copy link
Member

gdey commented Jul 24, 2024

Okay, I'm very close to having some fixes for this. Got the slippy tile to native working again. And Writing up some tests on tile families, which is how get the set of tiles to use for seed/purging.

@ARolek
Copy link
Member

ARolek commented Aug 15, 2024

This has been addressed in #1007 and will be included in the next release.

@ARolek ARolek closed this as completed Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

4 participants