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

batch feature locations #12

Merged
merged 1 commit into from
Jul 18, 2024
Merged

batch feature locations #12

merged 1 commit into from
Jul 18, 2024

Conversation

michaelkirk
Copy link
Owner

@michaelkirk michaelkirk commented Jul 18, 2024

We now make an educated guess as to how much "overfetch" to do based on the proximity of subsequent Features.

It's just a guess because we don't know how large the Feature's page actually is until we fetch the page's header.

image

The initial load of https://michaelkirk.github.io/geomedea/examples/maplibre/large.html goes down from 1.1MB to 312kb.

Now if I could just get the damn wasm file to be smaller 😅
Screenshot 2024-07-18 at 15 49 33

We now make an educated guess as to how much "overfetch" to do based on
the proximity of subsequent Features.
@michaelkirk michaelkirk force-pushed the mkirk/batch-feature-locations branch from 6bd783f to 246a673 Compare July 18, 2024 22:45
@michaelkirk
Copy link
Owner Author

@dabreegster - I'd be curious for you to try this. I'm hopeful it'll reduce the amount of transfer you see when using geomedea.

Note this is not a format breaking change. It should work with anything built with e8808ea or later.

@michaelkirk michaelkirk merged commit 417d4f4 into main Jul 18, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant