# Dashcam View

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 hood of the vehicle is below the region defined by the overlay

✅ The device is pointing out of the side window but otherwise unobstructed

* The device is blocked by an active windshield wiper, but is otherwise unobstructed ### What Makes Device Views Bad? * :x: There is a part of the car blocking the area defined by the overlay * :x: There is another object mounted to the windshield that is blocking the defined area * :x: There is an object sitting on the device that is blocking the defined area Let’s take a look at some examples of bad Tilt angle imagery: #### Bad Mount Examples

❌ Device with another mounting arm or suction cup within the defined region

### 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

✅ 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

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.hivemapper.com/contribute/train-the-map-ai/dashcam-view.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.