> For the complete documentation index, see [llms.txt](https://wiki.roaddirect.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.roaddirect.co.nz/eboard/map.md). # Map The Map section of [eBoard](/eboard.md) displays a Google Maps overview of all job sites for a given time-period. This can be a single day, or multiple days. The Map section will request access to your location via the browser. It does this simply to centre the initial map view on your location. Job sites are indicated by a road cone marker, and are colour-coded based on the "Setup Importance" of the job. Clicking on a marker will display a pop-up showing information regarding the job site. This information includes: * Job Number * Location * Location Reference * Client Name * Contact Name (including a link to click to call contact's phone number) * Description of Work Activity * GPS coordinates --- # 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://wiki.roaddirect.co.nz/eboard/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.