Skip to content
This repository has been archived by the owner on Sep 18, 2024. It is now read-only.

[1.0.0] API Design #13

Open
nitaliano opened this issue Jun 8, 2018 · 2 comments
Open

[1.0.0] API Design #13

nitaliano opened this issue Jun 8, 2018 · 2 comments

Comments

@nitaliano
Copy link
Contributor

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

@kristfal
Copy link

kristfal commented Aug 3, 2018

Hey,

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.

Offline support

AR view overlaid with a map view. Like this.

Thanks and keep up the good work.

@nitaliano
Copy link
Contributor Author

@kristfal I sent you a message on Gitter

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants