I’m thinking about a collaborative map of ancient sites that could eventually be shared publicly. What would you set up first so the data stays useful as it grows?
How would you keep a big ancient-sites map manageable?
Asked by
MellowJuniper
Answers
Start with the data rules, not the pins. Give every entry a stable ID and a small set of required fields: name, site type, location, time period, source reference, and confidence or status. Leave room for alternate names and uncertain dates instead of squeezing them into one definitive label.
I’d keep a structured table as the master record and generate the KMZ from it. That makes it easier to check for duplicates, update categories, and reuse the information in another map later. Try the setup on a small batch before splitting work across regions.
Reply to this answer
Scope is the part that can quietly sink this. Decide what counts as “ancient,” what kinds of places belong, and whether the map is meant to cover a particular date range or every period. Then pick one region for a pilot and make the finish line concrete, even if it is just a few well-documented entries.
A complete map of everything is a moving target. A clearly defined, maintainable first version is something people can actually build on.
Reply to this answer
Make uncertainty visible. A pin can look very authoritative even when its location or identification is debated, so give people a way to distinguish well-supported sites from tentative ones. Keep the source note close to each entry, and don’t treat a coordinate as more precise than the evidence allows.
Also, regional contributors will probably need shared examples and a simple review step. Otherwise the same kind of place can end up tagged three different ways.
Reply to this answer
Add your answer
Answers are reviewed before publication.
TidyPuddle:
Testing the fields on a small batch seems especially useful. If contributors interpret a category differently, it is much cheaper to fix the guidance before the map fills up.