Custom Marker Map

A pin map tuned for presentation

Same engine as the pin drop map, framed for output: choose a colour per marker, keep labels legible, position the viewport deliberately, then export a crisp PNG that matches your screen's pixel ratio — retina-sharp for slides, proposals, invitations and worksheets. The workflow stays URL-native, so a client link reproduces the map without anyone installing anything, and GeoJSON/KML/CSV exports keep the same data usable beyond the image.

The colour palette is deliberately small and high-contrast so categories stay readable when printed; clicking a marker's swatch cycles it. Because the export captures the rendered basemap, the PNG is ready to paste as-is, while the GeoJSON preserves editability for later. When the story needs areas instead of points — catchments, territories, response zones — the radius and drive-time tools draw the polygons; when it needs hundreds of points, CSV-to-map clusters them. Free, browser-based, no watermark on anything you create.

Worked examples

• Five labelled pins — read instantly in a slide; thirty unstyled dots don't — restraint is the craft, and colour-by-category carries the grouping.
• Share-state URL — encodes pins, colours and labels as parameters: the link reopens the exact map on any device with zero server storage.
• PNG at retina ratio — drops straight into worksheets and decks, while the companion GeoJSON/CSV keeps the same data editable afterwards.

Making maps that communicate

A custom map is an argument: these places matter, in this order, with these names. The craft is restraint — a handful of labelled, colour-coded pins reads instantly, while thirty unstyled dots read as noise. Colour should carry category, labels should carry identity, and the viewport should be framed so the subject fills the frame. Export quality closes the loop: a PNG at screen pixel ratio drops straight into slides and worksheets, while GeoJSON, KML and CSV keep the same data editable for the next person.

Sharing deserves the same thought. The most durable share format for a small custom map is the URL itself: pins, colours and labels encoded as parameters reopen exactly as left, on any device, with no account and no server storage. It is also the most honest privacy model — the map exists only where you sent the link.

When the dataset grows beyond a few dozen points, the instrument changes: clustering keeps tens of thousands of rows fluid, category columns replace hand-picked colours, and imports replace clicks. Knowing when to move from pin-dropping to data-mapping is the difference between a charming figure and a maintainable one.

Tips & common mistakes

Limit each map to one message: pins for places, polygons for areas, rings for reach. When a single figure needs all three, it usually needs two figures instead.

Choose colour for category, not decoration: two or three high-contrast hues read instantly; a rainbow reads as noise. Labels carry identity, colour carries grouping, and the viewport should crop tightly to the subject.

Export twice: an image for the slide and a data format (GeoJSON/CSV) for the record. The image communicates; the data survives editing, and the pair keeps your map honest and reusable.

Design principles for maps people actually read

A custom map succeeds when a viewer can state its message in one sentence without help. That demands hierarchy: a tight viewport, a handful of labelled points or a few coloured areas, and a legend or title that says the point in words. Every additional pin beyond the message is noise; every colour beyond category is decoration. The tools here are deliberately simple because restraint is the feature — the craft lives in what you choose to leave off the map.

Equally important is durability. A map that lives only as a screenshot dies young; one exported as image plus data (GeoJSON/CSV) plus share-URL survives edits, corrections and re-uses. When the dataset outgrows hand-placed pins, switch instruments — clustering and category colouring in the CSV tools — instead of cramming. Knowing which instrument fits which scale is the quiet professionalism behind every map that looks effortless.

How professionals use this

• One map, one message; if you need two messages, make two maps.
• Colour = category, label = identity, viewport = argument. Nothing else earns ink.
• Export image + data + link together; each serves a different future reader.
• Beyond ~50 points, move to CSV-to-map with clustering rather than hand-pinning.

Step-by-step masterclass

1. 1. Write the one-sentence message first — If you can't state the map's point in one sentence, no styling will save it; the sentence chooses the symbols.
2. 2. Limit ink to the message — A handful of labelled pins or a few coloured areas; every extra colour beyond category is decoration, every extra pin beyond the message is noise.
3. 3. Frame tightly — Crop the viewport to the subject; empty ocean is not context, it's dilution.
4. 4. Export the trio — PNG for the slide, GeoJSON/CSV for the record, share-URL for the living version — three readers, three futures.
5. 5. Switch instruments at scale — Past ~50 points, move from hand-pinning to CSV clustering; the right tool at the right scale is the whole craft.

Conventions differ by audience: classrooms expect printable PNGs, analysts expect CSV/GeoJSON, journalists expect a clean embeddable image with attribution — exporting all three from one composition is what makes a small map professionally portable across those cultures.

Related questions people ask

Quick glossary

Viewport framing

Cropping the map tightly to the subject so the message fills the frame.

Cluster marker

A grouped dot representing many nearby points at low zoom.

Share-state URL

Encoding the whole map configuration in the link itself.

Pixel-ratio export

PNG export at device resolution for crisp slides and print.

Legend discipline

Every colour on the map appears in the legend, and vice versa — no orphans.

Attribution string

'© OpenStreetMap contributors' — the ODbL ask for reused basemap imagery.

From screenshot to artifact: making maps that survive contact with reuse

The final skill in map-making is longevity. A map that exists only as a pasted image dies the day its data changes; a map that exists as image plus dataset plus link lives through corrections, re-styles and re-uses. That is why the export trio matters more than any styling choice: the PNG persuades today's audience, the GeoJSON/CSV preserves the argument's evidence, and the share-URL keeps a living version one click from anyone who asks 'what if we moved that pin?'. Organisations that internalise this split stop losing maps the way they stop losing spreadsheets — the artifact has a source, and the source has a link. Combined with the restraint rules (one message, colour-as-category, tight framing), it turns a free browser tool into a small but genuinely professional cartographic pipeline.

• Name exports by message, not date: 'delivery-radius-proposal' outlives 'map-final-v3'.
• Keep the share-URL beside the PNG in any document; readers trust editable evidence.
• When a map needs a second message, make a second map — and cross-link them.

Honest limits & when to escalate

Custom maps inherit two honest limits: the basemap's and the message's. The basemap is OpenStreetMap's current picture with its ODbL attribution ask, and its gaps — new roads, thin rural detail — travel into every export that includes tiles. The message limit is design's classic one: a map can carry one argument well, and beyond a few dozen symbols the right instrument changes to data-driven mapping with clustering and categories. Both limits are stated where they matter, because the alternative is a beautiful figure that misleads its own author.

Within those bounds the workflow is complete and durable: pins, labels, colours, tight framing, pixel-ratio PNG for the slide, GeoJSON/CSV for the record, URL-state for the living version. Escalation is gentle by design — choropleths and territory shading belong to GIS with real boundaries (the blank-map library and GeoJSON exports feed it), cartographic print production wants vector pipelines, and brand-strict design systems want tokens this tool deliberately doesn't fake.

• Data-dense maps → CSV-to-map with clustering and category colour.
• Boundary shading/choropleth → GIS with census or OSM boundaries.
• Print cartography → vector exports into a design pipeline.
• Authoritative basemap gaps → local authority open data over OSM tiles.

Data & methodology note

Map imagery derives from OpenStreetMap via OpenFreeMap (ODbL attribution applies to reused basemap images); your pins and labels live only in the share URL.

Category context: Map Creation — Drop pins, label places and export your own custom maps. This page is one of the map creation tools on MapForge; the related-tools links below and the header's Tools menu connect every sibling instrument.