Atlases and map books
Can export an entire map series in batches, with the legend showing only what appears on each sheet, the sheet index coming from a report, and a single PDF with bookmarks.
Deliverable: single PDF + control CSV per batchOcto for map production in ArcGIS
Almost everything done by hand in an ArcGIS Pro layout has an equivalent in the ArcPy mapping module (arcpy.mp): opening the .aprx project, swapping data sources, adjusting the legend, exporting map series and reports, merging PDFs and importing ArcMap .mxd files. With that, Octo can build entire atlases, audit hundreds of projects and check migrations, all prepared for human review. Publishing, editing the official database and signing the map stay with authorized people.
Six possible deliverables, drawn from the survey. All of them start from the client's project and data; none of them publishes anything on its own, and all go to review by whoever is responsible for the map.
Can export an entire map series in batches, with the legend showing only what appears on each sheet, the sheet index coming from a report, and a single PDF with bookmarks.
Deliverable: single PDF + control CSV per batchCan sweep the network folders, open each .aprx project read-only, list the broken layers and, with an approved mapping, repair them on a copy with updateConnectionProperties.
Can import the .mxd collection into ArcGIS Pro projects with importDocument, export each layout and compare it with the before image, ranking what changed most.
Can call the ArcGIS Enterprise printing service (Export Web Map Task) with curl, changing the extent and layout template text for each neighborhood or project. It even runs on Linux.
Can prepare vector tile package (.vtpk) generation and check beforehand what the symbology loses: hatching, gradients and most effects do not carry over.
Can note the ArcGIS Pro version, project, layout, resolution and pages of each product, so the atlas can be redone the same way next year.
Deliverable: record of version and parametersThree hand-made drawings to show the type of product, not screenshots or real maps. The layout, names and numbers are fictitious.
The same Octo cycle, applied to map production. Each arm has a narrow role; whoever publishes and whoever signs the map are authorized people.
How many .aprx, .lyrx and .mxd projects exist, in which folders, saved by which ArcGIS Pro version, and which layouts and map series are already set up.
Geodatabases, .sde connections, services and image folders for each layer; what is broken and where it should point. Without the right source, there is no right map.
Property registries, health and public safety may contain personal (LGPD) or confidential data. Sending anything to an external service, including AI, is assessed with the client first; credentials do not go into reports.
arcpy.mp on the licensed Windows machine when the project needs to be opened; the printing service over REST when the map is already published; plain Python to check images and reports.
Batch export with resume, repairs always on a copy, before/after comparison, with the documentation for each call noted in the file itself.
Fifty sheets before five thousand, one known project before three hundred. Checks by the content of the PDF, not by the absence of errors in the terminal.
Only with your OK, it runs in the environment the client approved and leaves the PDFs, copies and reports there. Publishing a service or replacing the original project is your decision.
ArcGIS Pro version, project, layout, resolution and the mapping for each run. Next year's atlas starts from this record, not from someone's memory.
Octo does not publish services to production, edit the official database or sign maps. That belongs to the data owner and the licensed professional.
The criteria Octo uses to choose. The ArcGIS Pro project remains the reference; the scripts produce, check and record.
| Task | Path | Note |
|---|---|---|
| Atlas of thousands of sheets | Spatial map series + MapSeries.export in batches + PDFDocumentCreate | export replaced exportToPDF in 3.4 |
| Legend that changes per sheet | LegendItem.showVisibleFeatures | Not every renderer supports it |
| Sheet index | ArcGIS Pro report + Report.export | Report set up beforehand, in the interface |
| Broken sources across many projects | listBrokenDataSources + updateConnectionProperties | Repair on a copy, with validate=True |
Migrating .mxd | importDocument + PNG export + image comparison | No ArcMap needed to import |
| Web printing, in batch | Export Web Map Task via curl | Runs on Linux; layout templates vary by server |
| Vector tile package | CreateVectorTilePackage | Web Mercator in ONLINE mode; simplified symbology |
Three steps. Each one only makes sense after the previous one has shown results in your cartography department.
A proposal, not a promise
With read access to the folders, Octo shows the state of the collection before any change.
Atlases, repairs and prints now run by script, with control and resume.
.mxd migration with visual verificationEach cartographic product now has a recipe: project, version, parameters and verification.
Each point below has a source published by the vendor, the project or the responsible agency. The sources are in the next section.
4
points with a published source, each with its reference alongside.
MapSeries.export(export_format, {mapseries_export_options}, {display_options}) replaced exportToPDF in 3.4. Pages are chosen with setExportPages (ALL, CURRENT, CUSTOM, SELECTED_INDEX_FEATURES) and customPages.Source: ArcGIS Pro documentation, MapSeries and MapSeriesExportOptions classesupdateConnectionProperties exists on projects, maps, layers, layer files and tables; by default it only swaps if the target is valid. If nothing matches, it finishes without errors and without changing anything; the project must be saved.Source: ArcGIS Pro documentation, "Updating and fixing data sources"importDocument accepts .mxd, .sxd, .3dd, .mapx, .pagx and .rptx. ArcMap 10.8.x is the last series; Esri asks users to migrate to ArcGIS Pro.Source: ArcGISProject class; ArcMap lifecycle, EsriLayout_Item_ID since 11.3.Source: ArcGIS Pro lifecycle, Esri; ArcGIS Pro system requirements; Export Web Map TaskOcto prepares everything, but does not sign. The document of record stays with whoever is accountable for it.
Gathers, calculates, organizes and produces the documents: spreadsheets, reports, maps and drafts.
Deliverable: material ready for reviewThe licensed professional reviews what Octo delivered before signing. If something doesn't add up, it goes back to Octo with the correction.
Step: review by whoever signsOcto does not sign. Designs, technical reports, ART/RRT, accountability reports and any official document are still signed by the licensed professional at the company or agency: here, the professional of record for the map or survey.
Signature: professional of record for the map or surveyEsri documentation used in the research, accessed October 29, 2026.
The assessment starts with an atlas or a set of projects you already have, read-only. You get a snapshot of the collection and a proposal for what can be produced in batch, and decide with it in hand.