How to Make a Professional Mineral Exploration Map

A professional exploration map needs five things: a basemap that suits the audience, a legible title block with project name, company and date, a scale bar and north arrow, a legend that names every layer, and an export sized for where the map will actually be seen. Choose the basemap by output — light for reports, satellite for investor decks, topographic for access and infrastructure. Export PDF for anything printed or filed, PNG for slides and email.

Build the map, not the layout. Title block, legend, scale bar and north arrow are toggles, not a page-layout exercise.
Open Exploration Maps →

What separates a figure from an illustration

A map without a scale bar and a north arrow is an illustration. Reviewers of technical reports expect both on every figure, and investors read their presence as competence without consciously noticing them. The same is true of a legend that names every layer and a title block that says what the project is and when the map was made. None of this is difficult — it is just easy to forget under deadline, and its absence is the first thing an experienced reader notices.

Choose the basemap by where the map is going

The basemap is the single biggest decision, and it should be made by output rather than by taste.

BasemapUse it forWhy
LightTechnical reports, permitting, regulatory filingsNeutral grey canvas keeps claim boundaries, collars and labels legible, and survives photocopying and greyscale printing
SatelliteInvestor presentations, location mapsAnswers 'how remote is this?' and 'is there access?' before anyone asks. Pair with light-coloured layer strokes
TopographicAccess, infrastructure, drill planningContours and elevation shading carry the story when it is physical — road access, pad locations, powerline routes
DarkWebsite heroes, social posts, on-screen dashboardsHigh contrast makes coloured layers glow on screen. Do not print it

Add context, then get out of the way

Two overlays sharpen almost any exploration map: the Context overlay (roads, water bodies and towns) and Reference Labels (place names that orient a reader instantly). Drop the context opacity to roughly 40–60% so your own data stays dominant. The failure mode here is enthusiasm — a map carrying every available layer at full strength communicates less than one carrying three.

Exploration map with claim boundaries over a satellite basemap, context overlay at reduced opacity
Context at reduced opacity: enough to orient, not enough to compete

Scale bar and north arrow

Both live in the Design section and both are toggles. The scale bar calculates real ground distance for the current view and picks a clean round number that updates as you zoom, so there is nothing to hand-edit and nothing to get wrong when you change the framing.

  • Scale bar: bottom-left or bottom-right, away from the legend
  • North arrow: a top corner, opposite the title block
  • Neither should overlap data, labels, or an inset map
  • Elements assigned to the same corner stack automatically with correct spacing

Distance rings, when proximity is the argument

A distance ring turns 'remote project' into a number, and it earns its place whenever proximity is part of the story — distance to the nearest town, port, rail line, mill or power line, or a 'within trucking distance' argument for a development-stage project.

Centre the ring on the infrastructure rather than on your project. The label then reads as the distance to it, which is the direction the argument runs. Enable the curved arc label and keep the text short — distance plus landmark, e.g. "50 km from Port of Prince Rupert".

The title block

Project name, company name, and the map date. The date matters more than people expect: a claim map without one is undateable evidence, and tenure status changes. Click the title on the map to edit it, set the date in Design → Text & Metadata, and upload your logo at the bottom of the Layers section.

Export: match the output before you frame

Set the export ratio first. The on-screen guides then show exactly what the exported file will contain, so you frame once rather than exporting, checking, and re-framing.

Going toFormatRatio
Slide deck, website, emailPNGLandscape 16:9
Technical report figure, permitting documentPDFLetter or A4 portrait
News release attachmentPDF or PNGLandscape 16:9 for the wire, portrait if it is also a report figure
Print at sizePDF at 3× pixel ratioMatch the page

Check it at the size it will be seen

The most common export mistake is judging a map at full screen when it will be viewed as a slide thumbnail, in an email on a phone, or as a half-page figure. Shrink the browser window, or open the exported file at its real display size, and confirm the labels and the scale bar are still readable. If they are not, the fix is fewer labels rather than smaller ones.

Export a figure at the size it will actually be seen. Frame once against the ratio guides, then export PNG or PDF.
Open Exploration Maps →

Frequently Asked Questions

What map elements does an exploration map figure need?
At minimum: a scale bar, a north arrow, a legend naming every layer, and a title block with the project name, company and date. Technical report figures are also usually expected to state the coordinate system and datum. Beyond that, include only what supports the point the figure is making.
Which basemap should I use for an investor presentation?
Satellite, in most cases. It gives an audience immediate physical context — terrain, vegetation, water, existing roads and disturbance — which answers the access and remoteness questions investors ask early. Use light-coloured strokes on your layers so they stay visible over imagery.
Should I export PNG or PDF?
PDF for anything printed or filed — technical report figures, permitting documents, formal attachments — because it preserves exact page dimensions. PNG for slides, websites and email, because it is lighter and drops straight into PowerPoint or a mail client.
How do I make a map readable when it is printed in greyscale?
Use the light basemap, and make sure nothing important is distinguished by colour alone — vary line weight, dash pattern or fill hatching as well. Then print a test page in greyscale before you commit; it takes a minute and catches the layers that collapse into the same grey.
Where should the scale bar and north arrow go?
Scale bar in a bottom corner away from the legend; north arrow in a top corner opposite the title block. The rule underneath both conventions is simply that neither should ever sit on top of data or labels.