A city report should not start with a postcard. It should start with a system map: what the city makes, what it imports, who it serves, what it prices out, what it remembers, and what it cannot replace.
This report creates the frame for the next geo-economics layer of Artometrics. Comparisons can come later; first the site needs a way to ask the right questions of a place.
FAST FACTS
DATASET CONTEXT
The source stack includes BEA regional GDP, Commerce metro exports, DOSE global subnational output, Census ACS, World Cities Culture Forum, and local Socrata portals such as DataSF or NYC Open Data.
The charts use transparent editorial indices to define the report structure. A production pass should replace each index with a direct API or CSV aggregate.
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 - SYSTEM LAYERS
A city is not one industry. It is a layered machine: firms, ports, universities, housing, cultural venues, finance, infrastructure, rules, and stories.
The first Artometrics question is not whether a city is good. It is what kind of system the city is trying to be.
CHART 2 - GOODS AND SERVICES
Houston and Los Angeles still have obvious goods/logistics signatures. New York and San Francisco sell more invisible products: finance, software, expertise, media, and market access.
That matters because invisible exports are harder for casual viewers to see, but they often define the city's price structure.
CHART 3 - HISTORY LAYERS
History is not background flavor. It is infrastructure that keeps generating data: street grids, warehouses, universities, firm clusters, zoning, and habits of migration.
A city report should explain which older layer is still driving the present numbers.
CHART 4 - CITY FINGERPRINT
One variable lies. A fingerprint requires a pattern. The same GDP level can mean very different things under different housing, transit, culture, and export structures.
This is why a city profile should read like a data portrait, not a fact sheet.
CHART 5 - QUESTIONS
Before building comparisons, the local report needs its diagnostic questions. What does the place make? What does it import? What is scarce? Which cities are its real competitors?
Those questions turn open data into an identity argument.
CONCLUSION
The central assumption is that cities have data signatures. The challenge is to separate slogan from system: what is produced, what is scarce, who competes, and what historical layer still controls the present.
This gives future city reports a repeatable spine before deeper city-to-city comparisons begin.
REFERENCES
BEA. Regional GDP by county and metropolitan area documentation/API.
DOSE / PIK. Global subnational economic output dataset.
World Cities Culture Forum. CREATIVE Data Framework and 5th Edition Data Explorer.
DataSF and NYC Open Data. Socrata/SODA portal documentation.
U.S. Census ACS and International Trade Administration Metropolitan Export Series.
EDITOR'S NOTE
Values are editorial indices designed to define the analysis contract. They should be replaced with direct source aggregates during city-specific production passes.