Photo Logging should respect database source filters (critical for non-US users)
I love the Photo Logging feature – the AI recognition is impressive and the workflow is fast. But there's a fundamental problem for anyone outside the US: Photo Logging is hardcoded to map all recognized foods to NCCDB entries, completely ignoring the database source filters I've set under Add Food.
Why this matters:
**
**The US mandates fortification of grain products with thiamin, riboflavin, niacin, folic acid, and iron. Most other countries (EU, UK, Australia) do not. The NCCDB reflects US food composition, so when Photo Logging maps my German whole wheat bread to an NCCDB entry, it reports ~0.40 mg thiamin/100g instead of the actual ~0.10 mg in non-fortified European bread. That's a 4x error on a single nutrient – and it compounds across every grain-based food in a day.
I specifically configured my filters to use NEVO (Netherlands) and CoFID (UK) instead of NCCDB/USDA to avoid exactly this problem. The manual food search respects these filters perfectly. Photo Logging does not.
The result: I can't use Photo Logging for micronutrient tracking, which is the main reason I'm paying for Gold.
Feature request:
• Photo Logging should respect the user's existing database source filters, or
• Photo Logging should have its own database preference setting, or
• At minimum, Photo Logging should flag when it maps to a database the user has excluded, so the user knows to swap
I understand NCCDB has the broadest coverage (17,000+ entries vs. ~600 for NEVO), so a fallback chain would make sense: try the user's preferred databases first, fall back to NCCDB only if no match is found, and clearly label when a fallback was used.
This affects every Cronometer user outside the US who tracks micronutrients. Given that Cronometer markets itself as the most accurate nutrition tracker, database accuracy for international users seems worth addressing.
Anyone else running into this?