Sharing data

Help guide · Updated June 25, 2026

What this is. Campound's sharing format is the .campound archive — a single file containing your points, lines, and full-resolution photos (with the Dictionary types they need). Export one to send to a friend; open one they sent to add it to your map. Imports stay neatly separated as "bundles" you can show, hide, or remove without ever touching your own data.

Exporting your data

Open the More menu and pick Export points, lines & photos.

Export dialog with a Bundle name field defaulting to today's date and Cancel/Export buttons. — The bundle name is what the recipient sees when they open your archive in Manage imports. Default is today's date — change it to something memorable like "Cody's San Juans 2025".

Tap Export and Campound packages everything you own — your points, lines, photos (full-resolution originals, not just thumbnails), and the Dictionary types they reference — into a single .campound file. The system share sheet opens so you can send it via Messages, Mail, AirDrop, Slack, Drive, or save it to Files.

Photos are full-resolution. The archive includes the original bytes (HEIC, JPEG, whatever you shot) — not the on-map thumbnails. So a trip with 50 photos can be a sizable file. Use AirDrop or a file-sharing service for big bundles.

Receiving someone's bundle

When a friend sends you a .campound file, opening it (tap in Messages / Mail / Files) hands it off to Campound. The app reads the bundle, adds its features and photos to your map, and stamps each one with the bundle's identifier so they stay grouped.

Imported data sits alongside your own data on the same map layers (My spots / My routes / My photos). But under the hood it's flagged differently — so it can be shown, hidden, or removed without affecting anything you created yourself.

The Manage imports screen

To see everything you've imported, open the More menu and pick Manage imports.

Manage imports dialog with empty state: 'No imports on this device yet. When someone shares a .campound archive with you, opening it here will list it on this screen.' — Empty state. You haven't imported anything (yet).

Once you've opened some bundles, each one shows up as a row with its name and what's inside:

Manage imports populated with two bundles: 'Ash's Wind River trip' (2 POINTS, 1 PHOTO) and 'Cody's San Juans 2025' (5 POINTS, 3 PHOTOS), each with a red trash icon. — Two example imports, each summarized by its point/line/photo counts. The red trash icon removes the entire bundle from this device.

Removing a bundle deletes every point, line, and photo that came in with it — including the full-resolution photo originals. Your own data is never touched. There's a confirmation dialog with the bundle name and counts before the deletion goes through.

The bundle filter

Bigger picture: any of the "My" overlay layers (My spots, My routes, My photos) gets a Filter by type button next to it in the Layers menu when imported bundles are present. Tap it to open the "My data" filter, which has two sections side by side.

My data filter panel with two sections. BUNDLES: Mine, Ash's Wind River trip, Cody's San Juans 2025. MY SPOTS: Campsite, Point of interest, Water, Restroom, Parked, Fishing hole, Trailhead, Parked, Untyped spots — each with its icon and color. — Two axes: **BUNDLES** at the top filters by source (your own data vs. each imported bundle), **MY SPOTS** at the bottom filters by Dictionary type. They combine — you can show "only my campsites" or "only Cody's trip's photos."

Section	What it does
BUNDLES → Mine	Show or hide everything you created. Always present.
BUNDLES → <Each import>	Show or hide one specific imported bundle as a group. Tapping toggles every feature/photo from that bundle on or off.
MY SPOTS / MY ROUTES → <Each type>	Show or hide a Dictionary type. Affects both your own data and imported data of that type — they're treated as the same shape, different origin.

Copy-to-my-data

When you want to edit, re-export, or otherwise treat an imported feature as your own — say, a campsite Cody marked that you want to keep using year after year — there's a Copy to my data action on each imported feature. It forks the feature: copies the full-resolution bytes (for photos) into your own Filesystem path, regenerates a thumbnail, and stores a fresh copy under your own ownership. The original imported bundle stays intact; the new copy belongs entirely to you.

How bundles stay safe

Three guardrails keep imports from polluting your data:

Sync-skip. Imported features and photos never upload to your account, even if you're signed in. They live only on the device that opened the archive. (This prevents you from accidentally claiming Cody's data as your own.)
Dictionary remap. If a bundle defines its own Dictionary types, those types are renamed internally on import so they can't collide with yours. The result: their "Campsite" type and your "Campsite" type stay separate, even if you both happened to use the same name.
Tombstones. If you delete a bundle (or any feature/photo from it) and then re-import the same archive later, the deleted items don't come back — Campound remembers what you removed.

Tips

Name your exports for the recipient, not yourself. "2026-06-25" is fine for your own backups, but a friend opening "Cody's San Juans 2025" knows immediately what they're looking at.

Bundle filter only appears when needed. If you've never imported a bundle, the filter shows only the type list — no BUNDLES section. As soon as your first import lands, the section appears. (For My photos specifically the filter button itself only shows up once you have an import.)

Removing a bundle is a "this device" delete. The original archive file (in Files or wherever you saved it) isn't touched, and the original sender still has their copy. You're just cleaning up your end.

Re-exporting a bundle re-imports it as a new bundle. If you export your map and then re-import that same file (long story), the imported copy lands as its own separate bundle alongside your originals. The app can't tell that it's a round-trip of your own data — bundle identity comes from the file itself, not its contents.