I'm happy to publicly announce that there is an up-to-date rebirth of the old City of Data site.
The site is accessible at https://cod.uberguy.net/
This is meant as a successor to Red Tomax's original City of Data, and borrows heavily from that site's organization and visual display of information. Quite a few things have changed, , though, both in the game and our understanding of its data, so it's not identical to the old site. It shows more information in a lot of cases, and lets you see more "raw" data.
This site would not have been possible without the extremely impressive work done by @RubyRedto create the Powers project and the coh.tips site. Ruby's Code Archeology blog post made me realize this project was achievable using Ruby's work as a starting point.
I also want to thank @Bopperfor help trying out the early versions of the site, finding bugs and making suggestions. @Captain Powerhouse also gave valuable feedback, and some of his suggestions are still in the pipeline as tweaks and improvements.
The site's data is extracted from Homecoming's game files using a modified version of Ruby's tool. This version exposes the raw data in a Python environment, where I perform additional transformations before exporting it as JSON. This version of the data acts as the backing for the website. The site is entirely dynamic on the client side - there is no server-side page rendering. This does mean the site requires Javascript to be enabled and a relatively modern browser. If you've updated your browser in the last couple of years, you should be fine. (If you haven't, I hope you have either an excellent antivirus or exceptional opsec skills.)
There are some ways of displaying things the old CoD did which aren't the most practical for this version. They're possible, but more work (or cause more traffic) due to design decisions I made about how the power and other data is structured. Old CoD built display pages on the server, where the new CoD is entirely client-side logic. This means how the site displays things is more tightly coupled with decisions around the structure of the files it pulls in to show you data. For example, every power is sent as a distinct data file, so displaying a whole powerset on one page would currently require pulling down every power in the powerset. Do-able, but not great. (A more compact whole-powerset display is possible, but ideally calls for a better slice-and-dice export of the powerset as one file.)
I've made some effort to check that the site works on mobile devices, but it is not really visually optimized for that. I have no way to test the site on Safari or iOS devices. I can test it on browsers that run on Linux, Windows and Android. Most of my testing was done in Chrome and Chromium-based browsers, plus Firefox.
Questions and feedback are welcome. Be sure to check out the "Help" pages on the site, which are accessed via the question mark link on the top right of every page.