Jochen Topf

> Regarding a more efficient sorting of the index, if I understand correctly your suggestion in point 2, the idea would be: build a vector of pairs while shrinking the...

"name" tags are problematic, because there are so many different names. There are over 11 million different name tags, much more than, say, the 780 different highway tags. This makes...

Anything other than plain text in the description isn't supported by taginfo. Here there is a link `[[Tag:barrier=lift gate|lift gate]]` embedded in the description that taginfo can't handle. You can...

The current UI works somewhat on smaller screens, but some functionality is not available: * Links to Overpass etc. * Language switching * Values bar graph on keys page obscures...

That's because there was a redirect from the wiki page `Key:office=diplomatic` which confuses taginfo (*). I have marked this page in the wiki as to be deleted, because it doesn't...

@daniel-j-h The existing "index" code in libosmium is templetized, so it can be used not only for ID->Location lookups, but also for ID->ID lookups or similar things. So this should...

This sounds like a useful addition. Maybe somebody who needs this themselves wants to give it a try?

Thanks for the report. The fix will show up on the site soon.

Most pages in taginfo have tables and those tables resize automatically for the screen size. But this doesn't work for those pages (like the chronology graph) which don't have tables....

Changeset replication is something totally different. This isn't supported by pyosmium-get-changes or any of the other tools.