LogoLogo
  • welcome
    • Introduction
    • Explain Like I’m Five
    • Data Protection and Privacy
    • Network Governance
      • MIP-1
      • MIP-2
      • MIP-3
      • MIP-4
      • MIP-5
      • MIP-6
      • MIP-7
      • MIP-8
      • MIP-9
      • MIP-10
      • MIP-11
      • MIP-12
      • MIP-13
      • MIP-14
      • MIP-15
      • MIP-16
      • MIP-17
      • MIP-18
      • MIP-19
      • MIP-20
  • Contribute
    • Map With Hivemapper
      • Device Models
      • 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
  • CAMERAS
    • Open Camera
    • 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
  • Summary
  • Timeline
  • Detailed Changes
  1. welcome
  2. Network Governance

MIP-14

Map Improvement Proposal 14: Trigger for Stricter Map Progress Metrics

PreviousMIP-13NextMIP-15

Last updated 1 day ago

Summary

MIP-14 raised the bar for regions to achieve the top score on the Coverage and Activity components of Region Progress, which are used to determine the size of the weekly rewards pool and allocate rewards among regions of the world. This resulted in stricter requirements than were established in .

Timeline

Detailed Changes

In the long run, achieving a 100% score on the Coverage and Activity metrics would require mapping all roads on a regular basis. It is important to avoid "grade inflation" so that the top-performing regions, which are getting closer to this end state, earn more rewards than others that are farther away from achieving it. The threshold to achieve a 100% score needs to function like a curve on an exam.

MIP-14 established a "trigger" for imposing stricter requirements, specifically a guideline that regions receiving 100% on the Coverage and Activity metrics should account for no more than 5% of region weight. At the time when MIP-14 was implemented, this led to tougher requirements:

  • To maintain a 100% score for Coverage in a region, contributors needed to refresh 20% of unique km every 28 days, up from 15% before MIP-14.

  • To maintain a 100% score for Activity, contributors needed to submit 75% as many total km every week as there are road km in the region, up from 30% before MIP-14.

MIP-6
Proposal: Published
Comment Period: Complete
Outcome: Finalized