San Francisco is a perfect city microscope because its contradictions are measurable: a small city with enormous software output, extreme housing pressure, intense cultural mythology, and a regional economy larger than its municipal boundary.
This report does not try to finish the comparison yet. It defines the questions a serious SF data portrait has to ask.
FAST FACTS
DATASET CONTEXT
DataSF provides Socrata/SODA API access to city datasets, including registered businesses, building permits, 311 cases, public safety, transportation, housing, and civic operations. Regional identity requires adding BEA, Census ACS, BLS, Commerce export data, and Bay Area transportation sources.
These charts are a framework pass: they show what the SF report should test when direct APIs are pulled.
Reader path: if you are new to the topic, treat each chart as a guided tour of one question: who leads, how concentrated the field is, what changes over time, and where the outliers sit. If you already know the domain, use the same charts as a challenge: check whether the metric is the right proxy, whether the source omits an important population, and whether the headline survives the limitations section.
CHART 1 - IDENTITY STACK
The simplest wrong answer is that San Francisco exports apps. The deeper answer is that it exports systems: venture risk, engineering labor, platform logic, taste, and institutional permission for strange ideas.
That is why the city can be small in population but enormous in economic imagination.
CHART 2 - TRADEOFF HISTORY
The SF story is not only success. It is absorption capacity. A small peninsula city generated global software wealth while underbuilding the physical city needed to metabolize that wealth.
The assumption to test later is whether housing, downtown vacancy, transit, and cultural retention are symptoms of the same bottleneck.
CHART 3 - NEIGHBORHOOD PRESSURE
A citywide average misses the point. SoMa, the Mission, Chinatown, the Tenderloin, and the Sunset each carry a different mixture of price, memory, commerce, and political meaning.
The DataSF layer matters because the city is small enough for block-level data to change the argument.
CHART 4 - COMPETITOR SET
Seattle is a software competitor. New York is a capital and talent competitor. Boston is a research competitor. Austin is a cost/relocation competitor.
The right competitor depends on the variable being contested.
CHART 5 - OPEN QUESTIONS
The next report should not merely rank San Francisco. It should ask whether the city can build housing, refill downtown, retain artists, keep AI local, and connect biotech to the same regional engine.
That is the bioeconomics question: can a place survive the metabolism of its own strongest trait?
CONCLUSION
The main claim is that San Francisco's identity is an invention machine constrained by physical absorption. The city makes ideas, companies, and cultural permission faster than it makes space.
That claim can later be tested against building permits, business registrations, office vacancy, transit recovery, migration, venture capital, payroll, and cultural venue data.
REFERENCES
DataSF / SF.gov. Open Data portal and developer documentation.
Socrata / SODA API documentation.
BEA. Metropolitan GDP and regional data.
U.S. Census ACS. Housing, income, commuting, and demographic tables.
International Trade Administration. Metropolitan Export Series.
World Cities Culture Forum. CREATIVE Data Framework.
EDITOR'S NOTE
Values are editorial indices for a source-backed framework. They should be replaced with direct DataSF, BEA, Census, BLS, and export aggregates in the full city-specific report.