# MIP-17 ### Summary MIP-17 created a cutoff of 65 kph for side-facing imagery. Customers have little demand for side-facing imagery outside of urban areas, so this change prevented low-value imagery from being rewarded. ### Timeline * [x] [Proposal: Published](https://medium.com/hivemapper-foundation/map-improvement-proposal-17-mip-17-e80008f19fd2) (June 3, 2024) * [x] [Comment Period: Complete](https://discord.com/channels/715439007764316191/1247264793182863441) (June 10, 2024) * [x] [Outcome: Finalized](https://medium.com/hivemapper-foundation/map-improvement-proposal-17-mip-17-e80008f19fd2) (June 14, 2024) ### Detailed Changes MIP-17 created a cutoff of 65 kph for side-facing imagery. After the launch of the Hivemapper Network, it became clear that map data customers have far less demand for side-mounted imagery outside of urban areas. For this reason, it was decided to only accept imagery from side-mounted dashcams below 65 kilometers per hour (approximately 40 miles per hour) to focus on denser areas. With the launch of the next-generation Bee camera, side-facing imagery was no longer supported, effective in March 2025. --- # 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/welcome/network-governance/mip-17.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.