Submit for review
Putting a Map in the public catalog is one button and a wait. The button is π Submit for Approval; the wait is a person looking at it.
Before you press it
The submission dialog shows a π Checklist, and it is worth reading rather than clicking past β it is the same set of things a reviewer sees:
| Checked | What it wants |
|---|---|
| Anchor Points | At least three. Fewer and the Map cannot place anybody |
| Calibration quality | No warnings. See read the accuracy heat map |
| Description | Present. It is what somebody reads in the catalog before installing |
| Tags | At least one, recommended. Tags are how your Map is found by search |
A warning does not block submission β you can submit with three anchors and a high error figure β but it is the likeliest reason to be turned down, so fixing it first is faster than a round trip.
And fix calibration before publishing, not after. Calibration is the change map creators most often want to make once real people are using the Map, and after publishing it costs a new Map Version rather than an edit.
What happens when you submit
The status becomes Pending, and visibility reads Private (until approved) β so nothing is public while it waits, and the editor says an admin will review your map shortly.
While it is Pending you cannot edit it, because what is under review has to stay the thing that was submitted.
What a reviewer looks at
Three questions, in roughly this order:
- Is this a real place, drawn usefully? A calibrated image of a venue with named Areas, rather than a test, a joke or a blank.
- Is the image yours to publish? You tick a box confirming you have the rights to it, and whatever you wrote in Image Source is shown to the reviewer. A venueβs official map published by that venue is straightforward; somebody elseβs copyrighted map is not.
- Is it safe and appropriate? Area names are reader-facing copy on a public surface, and they are read as such.
Nobody checks your calibration against the real world β that cannot be done from a desk. Accuracy is yours, which is why the checklist surfaces the figure rather than judging it.
How long it takes
There is no queue position and no SLA, because review is a person rather than a service. Expect days rather than minutes, and rather than hours around a weekend.
So do not submit the day before the event. If a Map has to be public for a specific date, submit it a week ahead β and in the meantime, let your Group use it directly, which needs no review at all: let your Group use an unpublished map.
The two outcomes
- Approved. Visibility becomes Public, the panel shows the date it went live, and anybody can find and install it. From that moment it cannot be edited β a published map cannot be edited.
- Rejected. It goes back to Private with notes explaining why, and you can fix it and resubmit β it was rejected.
Submitting an update to something already public
You do not resubmit the same Map. A change to a published Map goes into a new Map Version, which is submitted the same way and reviewed the same way, while the published one stays live throughout: create a new Map Version.