327 refactor mission visualization#331
Conversation
…on commands updating mission builder to support uavs and ground vehicles
to reuse in home position control, waypoint selection, rally point (todo), and drive to location
- added home location using LocationPicker - updated drive to location to use LocationPicker - added drive mode selector
removed code from mission builder to move to its own component
…to include drive and home location for mission builder
|
showing new mission vis layout |
salsajeries
left a comment
salsajeries
left a comment
There was a problem hiding this comment.
Mostly style/formatting changes
| export interface Waypoint { | ||
| id: string; | ||
| lat: number; | ||
| lon: number; | ||
| alt: number; | ||
| } |
There was a problem hiding this comment.
Extend MapPoint
import { MapPoint } from '@/modules/map/adapters/types';
export interface Waypoint extends MapPoint {
id: string;
}
| </v-col> | ||
| </v-row> | ||
| </v-form> | ||
| </template> |
There was a problem hiding this comment.
<style scoped>
.field-floating-details {
position: relative;
}
.field-floating-details :deep(.v-input__details) {
position: absolute;
top: 100%;
left: 0;
right: 0;
}
</style>
| <v-row | ||
| density="comfortable" | ||
| cols="12" | ||
| class="d-flex align-start justify-center" |
There was a problem hiding this comment.
class="d-flex align-center justify-center pb-4"
| cols="2.5" | ||
| xs="3" | ||
| > | ||
| <v-text-field |
There was a problem hiding this comment.
class="field-floating-details"
| cols="2.5" | ||
| xs="3" | ||
| > | ||
| <v-text-field |
There was a problem hiding this comment.
class="field-floating-details"
| disableWaypointSelection(); | ||
| isHomeLocationSelected.value = false; | ||
| isGeoPTZSelected.value = false; |
There was a problem hiding this comment.
Replace with disselectAllTools()
| disableWaypointSelection(); | ||
| isDriveLocationSelected.value = false; | ||
| isGeoPTZSelected.value = false; |
There was a problem hiding this comment.
Replace with disselectAllTools()
There was a problem hiding this comment.
Since Mission Builder has multiple different tools, maybe it should say which specific one is selected
| }, name: string, label: string): Promise<{ layer: typeof PointMarkerLayer; props: any }> { | ||
| const vizId = `location-${randomUUID()}`; | ||
|
|
||
| const icon = await getColoredIconUrl(`${ICON_BASE}/icons/waypoint/round-pin.png`, '#00BFFF'); |
There was a problem hiding this comment.
Consider different home markers to distinguish from waypoints/drive to which are more navigation?
Home: https://pictogrammers.com/library/mdi/icon/home-map-marker/
Drive-to:
There was a problem hiding this comment.
Couldn't pinpoint the cause of the issue, but LocationLayer icon color is different on Cesium vs. Leaflet
2 participants
Added new mavsdk controls to support uas/uav
refactored the layout of the mission builder
Added save/load missions from local storage
https://github.com/user-attachments/assets/501435eb-e8c7-4aeb-96a2-16f5fcfb2b8f