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

get new osm component to work with custom tiles #787

Open
kfarr opened this issue Aug 23, 2024 · 0 comments
Open

get new osm component to work with custom tiles #787

kfarr opened this issue Aug 23, 2024 · 0 comments

Comments

@kfarr
Copy link
Collaborator

kfarr commented Aug 23, 2024

the new osm tile component is excellent, but this uses the default tile.openstreetmap.org service. The osm4vr component does not yet support proper appending of api key in tile image requests to use other, paid hosted tile services.

Instead of osm free tiles, we may need to use a private service that requires an api key to access the tiles for billing purposes.

If it is possible to make this work, then we can also have preset settings for different tile types. We can then replace the legacy "mapbox" component and use this osm component with different tile styles. that would also save ~800kb on the legacy "mapbox" component library.

@kfarr kfarr mentioned this issue Aug 23, 2024
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

No branches or pull requests

1 participant