Working with an AI teammate
Get the most from Mapstack: say what matters, give it the context only you have, and shape the result together.
Working with Mapstack is like working with a skilled colleague who never runs out of time. You describe what you need. It finds the data, does the analysis and makes the map, the report or the print, making sensible calls along the way and telling you what they were. Then you shape it together, a message at a time, until it is exactly what you want.
It thinks about each job
Mapstack reads your request and your data and works out how to do the job, the way an expert would. That makes it flexible: it handles requests no menu would have anticipated, and it can take the same brief more than one way. Ask for "a map of income by area" twice and you may get two good takes, with different colours, breaks or titles. When you want options, ask for them: "Show me two other ways to colour this."
Say what matters, and leave the rest to it
What you state, Mapstack follows exactly: "five classes, natural breaks, darkest for the lowest incomes". What you leave open, it decides, and it tells you what it chose. So say the parts that matter to you, and let it handle the rest.
Give it the context only you have
You know the place, the audience and the purpose. A line of that goes a long way:
- Which place. "Newport in Wales", "the High Street in Kingston".
- Which measure. "A 10-minute walk along paths", not just "near".
- Who it is for. "For a committee pack, printed in black and white."
- What you already know. "Allerton should come out low; that's why we're looking."
Shape it as you go
Every change is just the next message.
- Say what to change. "Make the lowest class pale yellow." Everything else stays as it was.
- Steer early. Redirect after the first reply ("walking, not driving"), and everything after builds on it.
- Build on what you have. "Now a report for the committee from this map." Each new thing is made from the same data, so the numbers agree everywhere.
- Answer its proposals. On an open request, Mapstack first says what it understands and waits. Reply yes, or say what you'd like instead.
Review it like a colleague's work
You are the expert on what the result is for, so you are the reviewer. Mapstack makes that easy:
- It shows its working. Ask "How did you get 92.9%?" and it gives the steps, the inputs and the date of each.
- Look at the extremes. The highest and lowest areas, and any point far from the rest, tell you quickly whether the result fits what you know.
- Open what it made. The map, the table and the print are the work itself: look at them alongside the reply.
- Ask it to test. "Are any of these addresses outside the county?" gets Mapstack to check every row.
Example: the question 'Where in London are people most packed in?', the map of every ward that answers it, and Church Street, the most packed, opened to check its figure: 26,449 people per square kilometre against a ward average of 8,712.
Every figure about your data is worked out from your data, and anything from general knowledge is labelled as such.
Carry on, or start fresh
Keep going in the same session while each step builds on the last. For a new job, start a new session and describe it in one message. Everything you have made is in your Library, ready to use by name.
You make the calls
Mapstack asks before it makes or changes anything on an open request, tells you before a large job what it will use, and explains what it decided. Ask what it would do, and it gives you a recommendation with its reasons. The decisions that matter stay yours. For more, see How Mapstack works with you and How to ask for things.