A pixel pitch read off the wrong row

Most of what arrives here is a number. A pixel pitch transcribed from the wrong row of a datasheet, a lens listed at 35 mm that ships at 50, a unit that has been out for a season and is not in the 67 here yet, or a price that moved the week a new core shipped. Every one of those is worth sending, because a wrong pitch or focal length does not just sit in a table — it propagates into all three range estimates for that unit and into any guide it appears in.

Disagreements about the method are welcome too. The range figures are a model of the optics, not a measurement, and the assumptions behind them are written out in how we compare. If you have measured one of these units against a target at a known distance and the estimate is out, that is the most useful message this form can carry.

What happens next: the message lands in two inboxes, both belonging to the people who run the site — there is no queue and no support desk. A claimed correction is checked against the manufacturer’s own published page or datasheet before anything changes, and when it does, the source note on that unit’s page changes with it. A model that is genuinely missing goes into the next catalog pass. The current one was recorded 2026-09-20.

One thing this form is not for: paid placement. Nobody can buy a position, a better write-up, or a link, and manufacturer enquiries asking for one get a short answer. More on who runs the site and why it is built this way is on the about page.

If a datasheet screenshot is easier: chelsea@hagadornwebdev.com