How to Create an NI 43-101 Compliant Map
An NI 43-101 report map figure is expected to include a title with project and figure number, scale bar, north arrow, legend, coordinate/projection note, data source, effective date, and clean legible styling. Exploration Maps includes all of these elements — turn them on, fill in the title block, and export as PDF at 3× pixel ratio.
Turn public claim data into a clean map.
No GIS experience needed — import, style, and export in minutes.
Open Exploration Maps →
The standard figure checklist
Technical report figures follow strong conventions. Before any map goes to your QP, it should carry:
- Title block: project name, figure title, figure number
- Company name and map date (effective date of the data)
- Scale bar (true ground distance) and north arrow
- Legend covering every symbol and line style on the figure
- Location/index inset so the reader can place the map
- Data sources (e.g. 'Claim boundaries: BC Mineral Titles Online, retrieved 2026-07-06')
- Legible styling in print: no reliance on subtle colour differences
Where each element lives in Exploration Maps
| Requirement | Where | Notes |
|---|---|---|
| Title, company, date | Title block (Design section) | Shows project, subtitle, and date; add figure number to the title text |
| Scale bar / north arrow | Design section toggles | True-distance scale bar; corner-assignable |
| Legend | Per-layer legend settings | Every visible layer can carry a legend entry — audit before export |
| Location inset | Inset map (Design section) | Province/state inset places the property automatically |
| Source & datum note | Footer text | E.g. 'WGS84 / Web Mercator. Claims: MTO, 2026-07-06. Not an official tenure record.' |
| Print quality | Export settings | PDF, Letter/A4, pixel ratio 3× |
Build it in order
- Import claims/drillholes/targets and assign roles so styling follows convention
- Choose the Light basemap — it prints cleanly and keeps data prominent
- Fill the title block: project, figure title and number, company, date
- Enable scale bar, north arrow, legend, and the location inset
- Add the footer source/datum note
- Set Letter or A4 ratio, frame the figure, export PDF at 3× pixel ratio
What compliance actually means here
Your QP decides — this is figure craft, not legal advice
NI 43-101 is a disclosure standard, and the Qualified Person signing the report decides what its figures must show. The checklist above reflects standard expectations reviewers look for, not a legal guarantee of compliance. Always have the QP review final figures — and verify tenure data against the official registry before it appears in a report.
Build a report-ready figure in minutes.
Standard elements on by default — title block, scale, legend, inset.
Open Exploration Maps →
Import your file and export an investor-ready map.
Open the editor and have a shareable map in minutes.
Open Exploration Maps →
Frequently Asked Questions
Does NI 43-101 formally list required map elements?
The instrument requires that maps be legible and support the disclosure (location, tenure, results), and Form 43-101F1 requires certain maps (e.g. location, property). The specific elements — scale, north arrow, legend, sources — are standard professional practice that QPs and reviewers expect on every figure.
What projection/datum note should I use?
State what the map uses — for Exploration Maps exports that's WGS84 geographic data rendered in Web Mercator. A footer like 'WGS84 / Web Mercator; claim boundaries from [registry], retrieved [date]' covers datum, source, and currency in one line.
Can I use a satellite basemap in a technical report figure?
Yes, where imagery adds information (access, terrain, disturbance) — typically the location/access figure. For claim plats and results figures, the Light basemap keeps line work legible in print.
What export settings make a figure print-ready?
PDF at Letter or A4 page size with pixel ratio 3× — roughly 300 DPI equivalent. Check that the smallest text on the figure is still readable at 100% print size.
Is registry claim data reliable enough for a report figure?
Registry pulls are the right starting point, but tenure changes; verify ownership, status, and boundaries against the official registry as of the report's effective date, and date-stamp the source in the figure. The report's QP has final responsibility for the data shown.
Do I need a location inset on every figure?
Not every figure — but the property-location figure needs one, and small-scale detail figures benefit from one so readers stay oriented. It's one toggle, so the practical answer is: include it unless it crowds the figure.