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
{{ message }}
This repository has been archived by the owner on Sep 18, 2024. It is now read-only.
we're looking at moving into the AR space, and really do look forward to this component. Here are some high level thoughts and feature requests:
Seamless integration with mapbox tiles and location data:
a) I'd love to be able to select a layer in the map data (say POIs or other point sources) and render those in an AR context. Typically, we'd be interested in limiting the number of points rendered based on a radius from the user's location and perhaps even some clustering based on angle and distance to these points.
d) Occlusion: We'd love to be able to occlude AR elements based on map layers. Ex: Only show a POI in AR when the line of sight is clear based on a polygon or line string barrier layer (typically buildings)
e) Elevation support: This may be tricky, but it would be nice if we could position AR entries along the Z axis based a property in the map data, and use the mobile device's GPS to attain a rough user elevation difference. Elevation computation should be optional tho as a lot of custom data may not have elevation properties.
For anyone that would like to leave feedback on what they would like to see in our upcoming major release please leave your feedback here
The text was updated successfully, but these errors were encountered: