Honest opinion: Really charming on first look, but nothing where you can get lost in the details, because once you look closer, the soullessness of the generated imagery comes through. So I spent about 5 minutes looking at it, then moved on, and likely won't ever go back there.
With other things, like Floor796 that other people pointed out, I can spend so much time looking at all the labor of love that went in there, but making something to look at too closely likely wasn't the point here.
Ouch, this seems unnecessarily harsh for a side project made for fun. This might be acceptable if this was a low effort single prompt to an AI but it’s pretty clear from the write up that that is far from the case.
I was thinking the same..in fact it made me think enough that I wrote a blog/rant article about the topic AND created then a HN account. Well not this one specifically but all the other projects together I have seen recently and I just happened to have time today
https://burnoutdv.bearblog.dev/the-golden-age-of-hobbyiest-p...
> The source is Google Photorealistic 3D Tiles. Isometric.nyc explored and rejected the use of 3d building data. It is pretty insane that US gov has free LIDAR data for every city in the US available to the public. I spent <30mins exploring this and stuck to google 3d images. Claude Code whipped up a scraper to stream the 3D Tiles and render with three.js. This gives the best "real" texture base for the model to learn from. Anything else would involve a LOT of manual work to get the inputs right.
> Now that we have the 3D tiles, we need to generate the ground truth pairs for training! Similar to isometric.nyc, I generated a few ghibli-style pixel-art images using Google's Nano Banana. SF terrain is very interesting. There are quite a few distinct features like skyscrapers in FiDi, the hills in the southeast, 2 iconic bridges, lots of coastline, piers, parks, suburban grids and lots of water. I generated a ton of images and curated from them. Getting consistent style was a challenge. There was a LOT of manual trial and error. But as usual, Claude Code added this feature to the dev app that allowed me to select the best images and approve them.
interesting with the alcatraz island - I notice its invented some houses, and turned a cruise ship into a rock. I appreciate the difficulty and getting a lora to understand it - despite this the finished project is beautiful
I also feel that some of the technical explanations are a little dense here in the dev blog. I forget who it was who I saw mentioning it here on HN, but I've been having a lot of success with getting models to (re)write technical explanations in https://en.wikipedia.org/wiki/Simplified_Technical_English
I had to leave out a ton of details in the training process. But at every step, codex/cc built me a dev tool to navigate the complexity. That was such a unique side project experience.
I haven't used it but Vexcel makes oblique imagery available. They use planes I believe to get multiple passes of each are they image and from various angles. Then they combine it and make the maps available.
Nice! But for a city renowned for its steep streets, this looks suspiciously flat :) Ok, you could say it's only a 3D rendering of a 2D map, and it probably has to be this way for practical reasons, to avoid hills obscuring objects behind them, because you can't rotate the map as far as I can see, but not seeing actual height represented in a 3D view still takes some getting used to.
Also, there are neighbourhoods and landmarks, but not actual street names as far as I can see? Not to mention transit stops/lines and other fancy stuff one could add...
It’s vibe coded but it’s not slop. There’s a lot of human input here. So either the author overlooked the elevation issue or it was a deliberate decision, but in any case you can’t just pin this on “LLMs don’t understand isometric 3D”.
I've been busy with a rendered isometric map recently and I figured this is something Opus can help with, but it was near useless at understanding isometric designs along with elevation changes. It kept me busy for days.
Incredible. It's easy to just go on browsing and exploring. The massive, scrollable pixel art aspect reminds me a little of Floor796: https://floor796.com/
This is amazing, it got everything I could think of but not all, where’s little nightmares, silent hill, naruto, men in black, for a starter. But it’s neat regardless!
This is incredibly beautiful.
A few months back I tried to build a my own version of Google Earth rendered in voxels. Basically building from the terrain heightmaps scans available in open public data. Making it smooth and tessellation to work was incredible amount of work even for a simple vexed renderer
https://codetiger.in/earth/
Nice, but not sure I agree with your use of voxels. It appears more like pixelated height map, not the use of 3d pixels. From what I see every position on the globe can only have a single elevation
Those who know game dev know making good isometric maps can be deceptively difficult. You grabbed that bull by the horns and did so beautifully. Well done!
I've spent about a month all told in SF over a couple visits.
As a devout midwesterner, I didn't think I was going to enjoy the place. Having spent a bit of time there however, and having been shown around by natives, I absolutely get it.
There's so much to see and do packed in a small area, and the air just feels electric.
This could be a great anecdotal benchmark for agent/model progress. I wonder how much easier things have gotten with the latest Codex/Claude vs. when isometric.nyc was made.
I'm currently playing with something a bit similar and I was wondering about the fair use aspect.
What's the consensus on sharing the stylized assets created by diffusion models based on reference photos from e.g. Google Earth? Can the final output be shared as public domain or do Google, Airbus, et al. still hold some rights over them?
Very cool! Yesterday my wife and I watched Inside Out, and seeing the San Francisco setting felt very familiar (last year, 2025). Last year, in 2025, my wife and I went to San Francisco for our honeymoon. This website also showed me many familiar places.
Really cool. I can see some issues, like Starr King park turned into a lake for some reason, but it’s so much fun to look at. Do you have any way to patch errors and discontinuities at the tile boundaries?
Like the new york one, its just...unpolished. I dare to say slop. I am sure the author put some effort into it, BUT its just not there for me. The wiggly lines, the blurry designs and just everything. With something is pixelart or appears to be, I expected it to be pixel perfect, not just some random picture that looks like pixelart on the first glance.
The idea feels neat, but the execution needs so much more touch and polish. Maybe even handcrafting to be impressive.
Note that clicking the characters shows extra information.
Protip, visit About -> FAQ; there are many interesting questions like “What interactive elements are there?”.
Previously discussed: https://news.ycombinator.com/item?id=46401612 (and others).
FWIW I thought this was really cool.
https://sf.isopolis.city/dev.html
> The source is Google Photorealistic 3D Tiles. Isometric.nyc explored and rejected the use of 3d building data. It is pretty insane that US gov has free LIDAR data for every city in the US available to the public. I spent <30mins exploring this and stuck to google 3d images. Claude Code whipped up a scraper to stream the 3D Tiles and render with three.js. This gives the best "real" texture base for the model to learn from. Anything else would involve a LOT of manual work to get the inputs right.
> Now that we have the 3D tiles, we need to generate the ground truth pairs for training! Similar to isometric.nyc, I generated a few ghibli-style pixel-art images using Google's Nano Banana. SF terrain is very interesting. There are quite a few distinct features like skyscrapers in FiDi, the hills in the southeast, 2 iconic bridges, lots of coastline, piers, parks, suburban grids and lots of water. I generated a ton of images and curated from them. Getting consistent style was a challenge. There was a LOT of manual trial and error. But as usual, Claude Code added this feature to the dev app that allowed me to select the best images and approve them.
Love that attitude. Me too!
I also feel that some of the technical explanations are a little dense here in the dev blog. I forget who it was who I saw mentioning it here on HN, but I've been having a lot of success with getting models to (re)write technical explanations in https://en.wikipedia.org/wiki/Simplified_Technical_English
I had to leave out a ton of details in the training process. But at every step, codex/cc built me a dev tool to navigate the complexity. That was such a unique side project experience.
"Satellite images from highly oblique angles are pretty mindblowing"
If u like this u will like that
https://vexceldata.com/
Also, there are neighbourhoods and landmarks, but not actual street names as far as I can see? Not to mention transit stops/lines and other fancy stuff one could add...
[1] https://patcoston.com/sc2k/city/images/Calebopolis_Big.png
Naruto: https://floor796.com/#t2l4,684,675
The author continues adding and refining the project, so if it isn't in there yet, perhaps in the future.
Thank you for putting this together. Brought some fun memories back from my time living in SF
There are also a few massive square ponds in the Tenderloin that I am pretty sure do not exist lol
But I like the idea.
Planning to fix in the next version!
Less #127614 more #73ba14
So it looks less like Illinois
As a devout midwesterner, I didn't think I was going to enjoy the place. Having spent a bit of time there however, and having been shown around by natives, I absolutely get it.
There's so much to see and do packed in a small area, and the air just feels electric.
It's genuinely a different world.
This could be a great anecdotal benchmark for agent/model progress. I wonder how much easier things have gotten with the latest Codex/Claude vs. when isometric.nyc was made.
What's the consensus on sharing the stylized assets created by diffusion models based on reference photos from e.g. Google Earth? Can the final output be shared as public domain or do Google, Airbus, et al. still hold some rights over them?
Also, I would love to zoom in more. (pls give me the pixels)
I think a better data distribution should eliminate this. Also, my "water detector" was not too good and could be improved.
I wrote about a few of these things here: https://sf.isopolis.city/dev.html
I tried out a few ideas, but i think better training data around water will help a LOT.
I suppose that explains the yellow filter and the mixels
Like the new york one, its just...unpolished. I dare to say slop. I am sure the author put some effort into it, BUT its just not there for me. The wiggly lines, the blurry designs and just everything. With something is pixelart or appears to be, I expected it to be pixel perfect, not just some random picture that looks like pixelart on the first glance.
The idea feels neat, but the execution needs so much more touch and polish. Maybe even handcrafting to be impressive.