LogoLogo
  • welcome
    • Introduction
    • Explain Like I’m Five
    • Network Governance
      • Open Camera
    • Data Protection and Privacy
  • Contribute
    • Map With Hivemapper
      • Device Models
      • Bee
        • Assemble the Bee
        • Insert your SIM Card
        • Mount your Bee
        • Get Bee Maps App
        • Mount Check
        • Start Driving and Mapping
        • Upload Contributions (LTE)
        • Upload Contributions (WiFi)
        • Updating Bee Firmware
        • Add Bee LTE to Fleet (optional)
      • Creating a Guild
        • Adding a New Driver
        • Token Splits
        • Access Control List
        • Giving Access to Locked Devices
        • Hivemapper Guild Resources
      • Authorized Resellers
      • Accessories
      • Driver FAQs
    • Train the Map AI
      • Landmark Label
      • Position
      • Azimuth
      • Merge
      • Confirm Position & Azimuth
      • Dashcam View
      • Dashcam Tilt
      • Speed Limit
      • Speed Type
      • Turn Restrictions - No Turns 1
      • Turn Restrictions - No Turns 2
      • Confirm Attribute
      • Confirm Class
      • Stop Sign
      • Traffic Light
      • Highway Exit Signs
      • Highway Exit Info
      • Confirm Clarity of View: Interior vs Exterior
      • Confirm Clarity of View: Forward-Facing vs Side-Facing
      • Confirm Roadwork
      • Classify Roadwork
  • Use Map Data
    • Hivemapper App Developers
  • NETWORK PROTOCOL
    • Map Data Structure and Verification
    • What Is HONEY?
    • HONEY Burn and Mint
    • HONEY Token Restrictions
    • Earning HONEY
      • Reward Types
      • Global Map Progress
      • Individual Reward Factors
        • Map Tile Saturation
        • Usable Imagery
        • Clarity of View
      • Beware of Scam Airdrops
  • OLDER
    • HDC & HDC-S
      • Install an HDC
      • Install an HDC-S
      • Connect Dashcam to Hivemapper Companion App
      • Start Driving and Mapping - HDC/HDC-S
      • Upload Your Contributions - HDC/HDC-S
Powered by GitBook
On this page
  • Game Contents
  • What Makes Device Views Good?
  • What Makes Device Views Bad?
  • What Doesn’t Make Device Views Bad?
  1. Contribute
  2. Train the Map AI

Dashcam View

Learn how to train AI to grade the quality of a device's view

PreviousConfirm Position & AzimuthNextDashcam Tilt

Last updated 17 days ago

Well-mounted devices are critical for the Hivemapper community to generate high-quality map data. Based on input from a decentralized community of AI Trainers, contributors with good-quality, unobstructed devices receive a better reputation score, resulting in better rewards. Contributors with poor-quality, blocked devices receive worse rewards, and in extreme cases, receive no rewards at all.

In this game, you must answer only one question: did the driver mount their device with a clear, unblocked view?

Game Contents

You will be presented with the following information:

  1. A sample image from the device being rated

  2. An overlay that shows where objects inside of or part of the device's vehicle are and are not allowed

You have three choices:

  1. “Good” for a device that is not blocked in the defined area

  2. “Bad” for a device that is blocked in the defined area

  3. “Not sure” if you don’t know how to answer for this device

Please remember: you are only grading the view of the device. You are not grading the quality of the image, the weather, or if the device is tilted too far up or down. You should select “Good” as long as the device is correctly not blocked by objects, even if the windshield is covered in rain or the road features are difficult to see due to glare from the sun.

You are never penalized (or rewarded) for selecting “not sure.” Do not hesitate to use it, to help ensure that contributors are graded fairly for the quality of their mount.

What Makes Device Views Good?

  • There is nothing attached to the vehicle blocking the inner region defined by the overlay

  • The dashboard and hood of a vehicle are not blocking the region defined by the overlay

  • There may be temporary objects, such as a moving windshield wiper or raindrops, in the region defined by the overlay

Let’s take a look at some examples of good Dashcam View imagery:

Good Device View Examples

  • The device is blocked by an active windshield wiper, but is otherwise unobstructed

What Makes Device Views Bad?

Let’s take a look at some examples of bad Tilt angle imagery:

Bad Mount Examples

What Doesn’t Make Device Views Bad?

Do not select “bad” for an image just because one of the following is true. The view may be bad for other reasons, but these alone are not enough to grade the clarity as bad:

  • Trees or hills blocking the camera

  • Device facing the side instead of the front

  • Device being blocked by an object outside of and not attached to the vehicle, such as another vehicle

  • Raindrops, glare, active windshield wipers, or other temporary objects visible by the device

  • Small cracks or string-like objects, such as car antennae

There is a part of the car blocking the area defined by the overlay

There is another object mounted to the windshield that is blocking the defined area

There is an object sitting on the device that is blocking the defined area

❌
❌
❌
The hood of the vehicle is below the region defined by the overlay
The device is pointing out of the side window but otherwise unobstructed
Obstruction by a side mirror
Device with another mounting arm or suction cup within the defined region
Device blocked by hood or dashboard
Device facing the side instead of the front
Deviceam being blocked by an object outside of and not attached to the vehicle, such as another vehicle
Raindrops, glare, active windshield wipers, or other temporary objects visible by the device
Small cracks or string-like objects, such as car antennae
✅
✅
❌
❌
❌
✅
✅
✅
✅