Building a map people can trust

Trust is one of the quietest parts of a map experience. When it is working, people do not think about it very much. They click a marker, read the details, compare the location to what they know, and decide whether the entry feels useful. When trust is missing, every point on the map starts to feel uncertain.

Locory is built around the idea that places need context, but context only helps when it is clear and reviewable. A useful Locory should make a specific claim about a place. It should explain what happened there, what someone can learn there, or why the location belongs on the map. It should also give other contributors enough information to improve the entry later.

That is why the product treats submissions, requests, reports, comments, and moderation as connected pieces instead of separate features. A new submission adds a place. A request points to something missing. A report flags something that may need attention. A comment can add local detail or a current update. Review tools help the community and administrators decide what should be visible.

None of those pieces need to be complicated to be valuable. The most important signals are often small: a precise title, a pin in the right location, a description that avoids exaggeration, tags that match the place, and enough detail for another person to understand the contribution without guessing. These are the habits that make the map easier to maintain.

We also want Locory to leave room for uncertainty. Not every interesting place arrives with a complete story. Sometimes a contributor knows that something belongs on the map but does not know the full background yet. In those cases, requests and comments can help turn partial knowledge into a better entry over time.

The long-term goal is a map that feels alive without feeling chaotic. That means encouraging discovery while still protecting quality. It means making room for local memory while giving users ways to correct mistakes. It means letting a place grow richer as more people add what they know.

Check the place before polishing the story

Consider a hypothetical entry for a former neighborhood theater. Its description may be engaging, but the pin could point to a different building with a similar name. Before expanding the story, a contributor should compare the name, address, surrounding streets, and available evidence. A strong description attached to the wrong location is still misleading. Accuracy begins with identifying what the marker actually represents.

The pin also needs to match the subject's scale. A story about a building, a public artwork, and a large park calls for different location choices. Describe the subject clearly enough that readers understand whether the marker identifies a specific feature or stands for a broader place. Do not make a coordinate look more precise than the supporting information allows. If the location remains unresolved, explain what needs checking.

Next, read the description as someone who has never visited. Can that person tell what exists there now, what happened there before, and which details are supported? A good revision might clarify one sentence or remove an exaggerated claim. More text does not automatically mean more confidence. The purpose of an edit is to make the relationship between the location and its story easier to understand.

Make corrections specific and useful

A report is most useful when it identifies a problem another person can investigate. Instead of saying that an entry is wrong, explain whether the issue is its position, name, description, duplication, or current condition. Include the relevant detail and, where possible, the evidence behind the correction. A reviewer then has a concrete question to resolve rather than a general expression of disagreement.

Comments serve a different purpose when they add context rather than flag an error. A contributor might explain how a public space is used today or suggest a source that adds background. Keep that contribution focused on the place, and distinguish direct observation from information heard elsewhere. Disagreement about a local story should lead to better evidence and clearer wording, not personal criticism of the people contributing it.

Review is a way to improve confidence, not a promise that every detail will remain correct forever. Places change, sources become available, and mistakes can survive an initial check. An approved entry can still need correction. That is why the ability to report issues and add useful context matters after publication as much as it does during the first submission.

Write for the next contributor

A maintainable entry gives the next person a starting point. Use names that can be checked, explain unfamiliar references, and identify sources for factual claims. Avoid phrases such as 'everyone knows' when the reader needs an explanation. For a historical location, distinguish the former use from the present use. For access information, make clear what was observed and when instead of treating a temporary condition as permanent.

Someone preparing a submission can use the submission guidelines as a final reading check: is this a specific place, is its location accurate, and does the description explain its significance? If the place is only partly understood, a request can be a better starting point than an entry that fills the gaps with guesses. Careful contributions make later review easier and give future contributors something solid to build on.

What comes next

We will keep refining the review flow, content guidance, and contributor tools around that goal. A trusted map is not built by one perfect feature. It is built by many small decisions that help people add context carefully, find useful places quickly, and leave the map better than they found it.