> For the complete documentation index, see [llms.txt](https://docs.bawsaq.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bawsaq.org/the-city/map.md). # The city Eight districts around one crossroads. Where things are and what to do there. Los Santos here is a few blocks of GTA condensed into a city you can cross on foot in a couple of minutes. Two roads cross at the centre. Around them:


Grove Street and Ganton	The alley from the meme, the cul-de-sac, the Johnson house, the Sabre.	Grove Street and Ganton
Ballas turf	Idlewood and Big Smoke's crack palace.	Ballas turf
The Exchange	The BAWSAQ tower, its plaza, and Exchange Row's four towers.	The Exchange
Brand Street	San Fierro's parade of ten listed companies as real shops.	Brand Street
Las Venturas	The strip, the casinos, the fountain, the neon.	Las Venturas
Vice City	Ocean View Hotel and the Malibu Club, west of Grove Street.	Vice City
The Badlands and Mount Chiliad	The Truth's farm, the weed, the mountain and what sits on top of it.	The Badlands and Mount Chiliad
Lore and dossiers	24 boards, 47 company dossiers, and MISSION PASSED.	Lore and dossiers

## Getting your bearings The radar rotates with your camera and prints district names as you cross into them. From the spawn alley: **north** is Grove Street, **south** past the pavilion is Las Venturas, **east** along the main road is the Exchange with the Badlands and the mountain behind it, **west** is San Fierro and Brand Street, with the Vice City block up past Grove Street. {% hint style="info" %} Every district has at least one **lore board**, a big lit sign that retells a chapter of the San Andreas story. Walk up close and it counts toward your checklist. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.bawsaq.org/the-city/map.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.