Map Export, Printing, and Digital Delivery Standards

Why Delivery Format Matters

A map that looks perfect on screen can print muddy or pixelated if exported with the wrong settings. Conversely, a print-ready file sent to a web portal can take minutes to load and frustrate users. As a GIS technician or survey professional, your final deliverable is only as good as your export workflow. This lesson covers the two dominant delivery channels—print and digital/web—and the standards that govern each.

Print-Ready Export: PDF/X and Resolution

Large-format printing (plotters, offset presses) requires high resolution and a color model that matches physical ink. The key specifications are:

• Resolution: 300 dpi (dots per inch) at the final output size. For a 24" × 36" poster, every inch must contain 300 dots of information. Exporting at lower resolution produces visible pixelation on raster layers and fuzzy text.
• Color space: CMYK (Cyan, Magenta, Yellow, Key/Black). Printers mix these four inks. If you export in RGB and send it to a commercial printer, their software converts it automatically—often with color shifts, especially in reds and oranges. Export in CMYK yourself so you control the result.
• Format: PDF/X is an ISO standard subset of PDF designed for reliable print exchange. It embeds all fonts, flattens transparency, and excludes interactive elements that printing equipment cannot process. In ArcGIS Pro, choose the PDF export option and select "PDF/X" compliance when that checkbox is available. If the option is not exposed, a standard PDF at 300 dpi CMYK is acceptable for most plotter workflows.

In ArcGIS Pro: Share → Export Layout → PDF, then set Resolution to 300, Color Mode to CMYK, and confirm layers are visible at the export extent before clicking Export.

Web-Ready Export: PNG and Screen Resolution

Web and portal clients need files that load quickly on mobile connections. The specifications are almost the opposite of print:

• Resolution: 96 dpi. Computer and phone screens are typically 72–96 dpi (some high-DPI displays go higher, but 96 is the web standard for static images). Exporting at 300 dpi produces a file three times larger than needed with no visible benefit on screen.
• Color space: RGB (Red, Green, Blue). Screens emit light in RGB. Web browsers cannot interpret CMYK; they will either refuse the file or auto-convert it with unpredictable results.
• Format: PNG is preferred for maps because it is lossless—fine lines, text, and legend symbols stay sharp. JPEG compresses by blurring similar colors together, which creates artifacts around crisp map edges. Use JPEG only for photographic imagery where file size is critical.

In ArcGIS Pro: Share → Export Layout → PNG, Resolution = 96, Color Mode = RGB.

Publishing to ArcGIS Online

A static image is one deliverable; an interactive web map is another. ArcGIS Online lets clients pan, zoom, toggle layers, and query attributes on any device.

Workflow: In ArcGIS Pro, open the map (not the layout). Go to Share → Web Map. Set the name, summary, and tags. Choose sharing level—Owner only during testing, Organization for internal clients, or Public only if the data is cleared for public release. Always check your organization's data-sharing policy before making a map public; survey data may carry confidentiality or property-boundary concerns.

After publishing, open the item in ArcGIS Online, click Open in Map Viewer, and test on a mobile device or the browser's mobile-emulation mode. Confirm layers draw, pop-ups work, and the basemap is appropriate for the audience.

Attribution: Every web map must credit data sources. In ArcGIS Online, the item description and the map's attribution line must list the coordinate reference system, datum, data source agencies, and date of collection. Omitting attribution violates data-use licenses and undermines professional standards.

Metadata and the Client Delivery Package

A professional delivery package is more than a PDF. Clients and future technicians need context to use the data correctly. Standard components:

1. Multi-page PDF — all map sheets, 300 dpi CMYK, bookmarked by sheet name.

2. Metadata XML — describes the dataset: projection, datum, coordinate system, data sources, accuracy, lineage, and contact information. ArcGIS Pro can export FGDC-CSDGM or ISO 19115 metadata from the Catalog pane.

3. README.txt — plain-text file stating the datum (e.g., NAD 83), projection (e.g., UTM Zone 15N), linear units, file list, and any known data limitations. Never assume the client will infer this information.

4. Thumbnail image — a small PNG (typically 200 × 133 px or similar) that previews the map in a file browser or portal. Export at 96 dpi and crop to the map frame.

Organize all files in a clearly named folder (e.g., `Smith_Property_Survey_2024-06`) before compressing or transferring.

File Naming and Storage Safety

Use only letters, numbers, underscores, and hyphens in file names—no spaces or special characters, which break command-line tools and some GIS software. Keep originals on the school network or a backed-up drive. When delivering on a USB drive, scan the drive for malware before handing it to a client. Never store the only copy of a deliverable on a single USB drive.

Connecting to Credentials

Esri's ArcGIS Pro certification tests export and sharing workflows directly. NSPS CST candidates must understand map accuracy, datum documentation, and deliverable standards. FAA Part 107 pilots who collect aerial imagery are often responsible for the map products derived from that imagery, so understanding delivery quality is part of the full workflow.