An analysis of every word that’s visible on NYC’s streets (from 18 years of Google Street View Data). “The data is astonishing; it feels like sifting through the city’s source code. For example, here’s all 111,290 matches for ‘pizza’, on a map.”
This site is made possible by member support. ๐
Big thanks to Arcustech for hosting the site and offering amazing tech support.
When you buy through links on kottke.org, I may earn an affiliate commission. Thanks for supporting the site!
kottke.org. home of fine hypertext products since 1998.
Beloved by 86.47% of the web.
An analysis of every word that’s visible on NYC’s streets (from 18 years of Google Street View Data). “The data is astonishing; it feels like sifting through the city’s source code. For example, here’s all 111,290 matches for ‘pizza’, on a map.”
Comments 6
thread
latest
popular
This is incredible, a way to decode the city through its signage. Wow!
There's an outstanding talk from Yufeng Zhao from last year's !!Con explaining how he made the search engine. It's sad that this is the kind of innovation I would have expected Google itself to have built 15 years ago, and offered a free API to build on top of, but those days are long passed. Still, it's incredible that one engineer can now do this illicitly with scraped imagery using the OCR built into every Mac.
While reading The Pudding piece, I was thinking that if Street View hadn't been invented yet, there's in chance Google would be interested or even capable of making it happen.
Totally agree, their dreams of "organizing the world's information" are long dead. 10 years ago, I wrote about how Google gave up on that mission, with groups like Archive Team and the Internet Archive relentless pursuing it instead.
(BTW, I was typing the comment on my phone and misspelled the creator's name, it's Yufeng Zhao.)
((Corrected it for you...))
Amazing work: an analysis of words visible in NYC streetview https://pudding.cool/2025/07/street-view/ (via @kottke.org)
The top 12 most common words are all part of what I'll call a "vocabulary of restriction" ("stop", "no", "do not", "only", "limit", etc.)
("But on the back side, it didn't say nothin'!")
Hello! In order to comment or fave, you need to be a current kottke.org member. If you'd like to sign up for a membership to support the site and join the conversation, you can explore your options here.
Existing members can sign in here. If you're a former member, you can renew your membership.
Note: If you are a member and tried to log in, it didn't work, and now you're stuck in a neverending login loop of death, try disabling any ad blockers or extensions. Or try logging out and then back in. Still having trouble? Email me!
In order to comment or fave, you need to be a current kottke.org member. Check out your options for renewal.
This is the name that'll be displayed next to comments you make on kottke.org; your email will not be displayed publicly. I'd encourage you to use your real name (or at least your first name and last initial) but you can also pick something that you go by when you participate in communities online. Choose something durable and reasonably unique (not "Me" or "anon"). Please don't change this often. No impersonation.
Note: I'm letting folks change their display names because the membership service that kottke.org uses collects full names and I thought some people might not want their names displayed publicly here. If it gets abused, I might disable this feature.
If you feel like this comment goes against the grain of the community guidelines or is otherwise inappropriate, please let me know and I will take a look at it.
This thread is closed for new comments & replies. Thanks to everyone for participating!