Skip to content

Add better database structure for tracking errors #42

@himynamesdave

Description

@himynamesdave

The local SQLite database is structured with the following tables

  • input

    • id: UUID v4 for input
    • timestamp: time of import
    • cli_mode: selected via CLI
    • cli_input_path: selected via CLI (either directory to images, or video path)
    • cli_extract_fps: selected via CLI
    • cli_keep_extracted_frames: selected via CLI
    • cli_path_to_nadir: selected via CLI
    • cli_size_of_nadir: selected via CLI
    • cli_outlier_speed_meters_sec: selected via CLI
    • cli_max_output_video_secs: selected via CLI
    • cli_output_filepath: selected via CLI
    • cli_upload_to_streetview: selected via CLI
    • output_directory
    • streetview_id
    • streetview_status
    • steetview_error
  • video2video (for mode 1)

    • input_id: input ID video linked to
    • id: UUID v4 for video
    • length: extracted via exiftool
    • Width: extracted via exiftool
    • Height: extracted via exiftool
  • frames2video (for mode 2, 3, 4)

    • input_id: input ID video linked to
    • id: UUID v4 for video
    • Width
    • Height
    • ProjectionType
    • GPSLatitudeRef
    • GPSLatitude
    • GPSLongitudeRef
    • GPSLongitude
    • GPSAltitudeRef
    • GPSAltitude
    • GPSTimeStamp
    • GPSDateStamp
    • time_secs_to_previous
    • time_secs_to_next
    • distance_km_to_previous
    • distance_km_to_next
    • speed_kmh_to_previous
    • speed_kmh_to_next
    • error_reported
  • gsvauth

    • stores oauth key

    Can be done easily with geopy for speed/distance --> https://pypi.org/project/geopy/

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions