New sample demos for Cloud Styling, Roadmap Mode, Data Visualization,… - #50
New sample demos for Cloud Styling, Roadmap Mode, Data Visualization,…#50LoyalAbbas wants to merge 1 commit into
Conversation
… Field of View, Path Following, and Advanced Camera Animation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
There was a problem hiding this comment.
Android Lint found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.
| <activity android:name=".placedetails.PlaceDetailsActivity" android:exported="true" android:label="Place Details" android:theme="@style/Theme.AppCompat.DayNight.NoActionBar" /> | ||
| <activity android:name=".advancedcameraanimation.AdvancedCameraAnimationActivity" android:exported="true" android:label="Advanced Camera Animation" /> | ||
| <activity android:name=".datavisualization.DataVisualizationActivity" android:exported="true" android:label="Data Visualization" /> | ||
| <activity android:name=".cloudstyling.CloudStylingActivity" android:exported="true" android:label="Cloud Map Styling" /> |
There was a problem hiding this comment.
This has been removed, but CloudStylingActivity is still an activity on the code. Regression?
| import com.google.maps.android.compose3d.PolylineConfig | ||
| import kotlinx.coroutines.delay | ||
|
|
||
| class PathFollowingActivity : ComponentActivity() { |
There was a problem hiding this comment.
This doesn't seem to use SampleBaseActivity.
There was a problem hiding this comment.
Yes, I did this intentionally. The reason is that PathFollowingActivity needs its own specific UI controllers for the demonstration. If I were to extend SampleBaseActivity here, it would unnecessarily result in two different layouts trying to initialize the map instance.
However, if you look at the other features like DataVisualizationActivity, RoadmapModeActivity, etc., I did utilize the SampleBaseActivity layout by dynamically adding their respective controllers inside the activity_common_map layout.
Soon I will change for PathFollowingActivity also
|
There are a bunch of changes introducing only reformatting changes (like in ComposeDemos/MainActivity.kt). What if we agree to use the formatting rules from Android Studio, to avoid introducing those changes? Or if we want to formalise it, we could agree on using spotless, which can run on CI/CD. |
3 participants
New 3D SDK Showcase Features Added
Path Following (PathFollowingActivity): Real-time camera trajectory tracking along 3D polylines across urban (NYC) and rural (CA) routes with interactive altitude, range, speed, and heading controls.
Advanced Camera Animation (AdvancedCameraAnimationActivity): Animated 3D glTF airplane model paired with multi-step keyframe flight tours, frame dispatcher chase cameras, and 360° orbital landmark spins over San Francisco.
Roadmap Mode (RoadmapModeActivity): Showcase of 3D Vector Roadmap mode featuring 3D building geometries and street hierarchy layouts with dynamic switching between Roadmap, Hybrid, and Satellite modes.
3D Data Visualization (DataVisualizationActivity): Dynamic 3D flood elevation volume extrusion over coastal waterfront terrain with real-time risk severity badges and surge animation.
Field of View (FieldOfViewActivity): Camera perspective distortion and deterministic optical dolly-zoom scaling with live FOV slider adjustments (15°–120°) and instant lens presets.
Cloud-Based Map Styling (CloudStylingActivity): Custom map styling integration using Cloud Map IDs across 3D vector map layers with dynamic render mode support.