Mapping Tainan as a Cultural Interface

Tainan is often described as an old city. That is true, but it is not precise enough. Age alone does not explain why a place matters. What makes Tainan interesting is the density of overlapping histories: temples, Japanese-era buildings, old rivers, public halls, family gardens, food, literature, law, city gates, NCKU, political memory, and everyday street movement.

A city like this already contains cultural material. The design problem is that material does not automatically become readable. People need a way in. They need routes, stories, comparisons, media, translations, and prompts that help them understand how one place connects to another. Without that interface, cultural assets remain scattered across archives, expert memory, old maps, buildings, and private family stories.

A cultural map should do more than show pins. It should show relationships between time, power, architecture, food, education, religion, conflict, and daily life. A court building can be law, theatre, colonial history, architecture, tourism, and civic memory at once. A river route can explain movement, commerce, settlement, and environmental change. A school uniform can carry family memory as strongly as a monument.

The original Tainan note points toward comparing old maps to see how the city changed. That is a powerful product idea. A historical map interface could reveal where the old river moved, how city walls and gates shaped circulation, how Japanese colonial administration altered infrastructure, and how NCKU sits inside a larger urban history rather than outside it.

This is data-driven design, but with cultural data. The goal is not analytics for clicks. It is analytics for memory: a way to structure evidence so people can notice patterns that were already present but hard to see.

The same cultural asset should not be explained the same way to everyone. The note names mothers, high school students, backpackers from Europe, Japanese tourists, and other audiences. That list turns cultural mapping into service design.

A local high school student may need a personal connection to the city they think they already know. A visitor from Japan may need more context around colonial-era buildings. A European backpacker may need world-history anchors. A family may need shade, bathrooms, food stops, and a walkable pace. A design student may want visual references, systems, and case studies.

This is why the database is only the raw material. The experience depends on audience, route, duration, language, mobility, weather, motivation, and the social situation of the visit. A cultural interface should let the same city become legible through several lenses.

The source note lists drama, theatre, comic books, handouts, schedules, tours, maps, and apps. That range is important because it refuses the lazy question: should this be an app? The better question is which medium makes this cultural relationship easiest to feel, understand, and share.

Some stories belong in a walking tour because the body needs to move through distance and heat. Some belong in a comic because the relationships are visual and sequential. Some need a map because location and time matter. Some need a school assignment because the real audience is a student learning to notice their own city. Some need software only after the real-world experience has been understood.

A good cultural system lets media forms support one another. The map gives structure. The story gives emotion. The route gives bodily memory. The archive gives evidence. The interface should not replace the city. It should send people back into it with sharper attention.

Cultural projects often fail when they are treated as campaigns. A beautiful launch can hide the harder question of maintenance. Who updates the information? Who verifies corrections? How are rights handled? How do translations stay accurate? What happens when a route becomes unsafe, a building closes, or a community contests the official story?

A serious cultural map needs infrastructure: data models for places, time periods, people, events, images, routes, audiences, languages, sources, and update status. It needs editorial workflows, accessibility information, version history, and ways for communities to contribute without turning public memory into an unmoderated comment box.

That is the larger HAAM lesson from the Tainan note. Cultural heritage is not only a content problem. It is information architecture, service design, localization, software, public history, and maintenance. The goal is not to turn Tainan into tourist facts. The goal is to help people notice the relationships already present in the city and give them better ways to move through them.