COFFEEDEX is a thing I made to track coffee prices worldwide.
Late in the iD Editor sprint, I wrote osm-auth to make the OAuth dance easier for potential future editors, thinking that a lot of common editing tasks would require super-focused UIs. COFFEEDEX is more or less the first attempt at doing that: it edits a single tag on a single type of node,
amenity=cafe, and only on local nodes.
Does this bloat the database? My back of napkin math says that if we tagged all 150,000 cafes with 32 chars of
<tag k='coffee:price' v='$10' /> we’d end up with a grand total of 38.4MB of bloat, on a database that weighs 38GB, so we’re talking a tenth of one percentage of an increase.
Which brings me to the idea: what other things can we conquer in a single tag? Wheelmap is the great-grandaddy and most awesome example of this. How about:
- An editor that asks you how many stories the building you’re currently standing in has. Or what color?
- Bridge height entries
- Opening-hours-only editor
See a bug? If you have a GitHub account and want to be super nice to me, please file a bug in the GitHub issue tracker!