You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: