Overview
ArcGIS Pro is the application that geographic work runs on in most places that do geographic work seriously. A project holds maps, scenes, layouts, toolboxes and connections together, so the analysis, the cartography and the data all travel as one thing. It reads and writes the file and enterprise geodatabase formats, the open exchange formats, imagery and point clouds, and it does the analysis in the same window where the map is drawn rather than shipping it out to a separate tool.
This is the full desktop installation with every extension present rather than a base licence with the interesting parts locked. Spatial analysis, 3D analysis, network analysis, geostatistics, image processing, data interoperability and the publishing tools are all available from the moment it opens. The licensing layer is handled locally, so there is no portal sign-in, no named user check and no timeout when the machine is offline.
Maps, scenes and layouts
A project can hold any number of maps and 3D scenes side by side, with layers shared between them so a symbology change propagates. Symbology covers the full range from a single symbol through graduated colours and proportional symbols to dot density and multivariate displays, and every symbol is editable down to its individual layers. Labelling runs through the placement engine with weights, conflict resolution and expression driven text.
Layouts are where the map becomes a document. Multiple map frames, dynamic text that reads from the project, north arrows, scale bars, legends that update with the layer list, and a series generator that walks a grid or a set of features and produces one page per index feature. Export goes to the print formats with vector content preserved and with the georeferencing embedded where the format supports it.
Analysis and geoprocessing
The geoprocessing toolbox is the heart of it. Several thousand tools covering overlay, proximity, statistics, interpolation, hydrology, terrain, suitability modelling, network routing and raster algebra, all callable from a dialog, from a model built visually, or from the scripting environment. Models built in the visual editor are saved into the project toolbox and can be shared as files.
The scripting environment is a full Python distribution with the spatial libraries present, running in a console docked inside the application. Anything the toolbox does is available as a function call, which is how repeatable analysis gets built. Notebooks can be stored inside the project so the analysis and its documentation stay together.
Imagery, 3D and data management
Imagery handling covers multispectral analysis, orthorectification, mosaic datasets that stitch many images into one addressable layer, and the classification workflows including the pixel and object based approaches. Point clouds from lidar are read natively, classified, and rendered in the 3D scene with elevation, intensity and class colouring.
The data management side is the quiet reason this software is hard to replace. Geodatabases with domains, subtypes, relationship classes and topology rules keep data correct at entry rather than through cleanup afterwards. Versioning supports multiple editors on the same dataset, and the editing tools handle the awkward cases like shared boundaries that must move together.
What you get
- Projects holding maps, 3D scenes, layouts and toolboxes together
- Full symbology range with editable multi layer symbols and expression driven labels
- Layout series generation producing one page per index feature
- Geoprocessing toolbox with several thousand analysis tools
- Visual model builder and a docked Python console with the spatial libraries
- Imagery processing including mosaic datasets and pixel or object classification
- Native lidar point cloud reading, classification and 3D rendering
- Geodatabase management with domains, topology, relationships and versioning
- All extensions available rather than licensed separately
Inside the archive
- ArcGIS Pro 3.7 desktop application, offline installer
- Full extension set enabled at install
- Bundled Python distribution with the spatial library stack
- Coordinate system and transformation data
- Language packs for the interface list shown above
- Install notes covering the licensing layer
System requirements
| Operating system | Windows 10 version 22H2 or Windows 11, 64-bit |
|---|---|
| Processor | Quad core, 2.6 GHz or faster, six cores recommended |
| Memory | 16 GB minimum, 32 GB for imagery and 3D work |
| Graphics | DirectX 11 capable card with 4 GB VRAM, 8 GB for scenes |
| Storage | 32 GB free on an SSD |
| Display | 1920 by 1080 or higher |
Installing it
- Unpack to a local drive with at least 40 GB free.
- Turn off real time protection before running setup.
- Install the bundled runtime component first if the installer offers it as a separate step.
- Run the main setup as administrator and accept the default install location.
- Launch ArcGIS Pro. It opens directly to the project screen with no portal sign-in.
Mirrors
| Route | Region | Note | State |
|---|---|---|---|
| Direct, primary | Europe | No wait, resumable | Online |
| Direct, secondary | North America | No wait, resumable | Online |
| Torrent magnet | Global | Recommended for this size | Online |
Release history
- Coordinate transformation data refreshed
- Fixed a crash when exporting a layout series above 500 pages
- Point cloud rendering performance improved on large tiles
- First release of the 3.7 cycle
- Object based image classification workflow reworked
- Geodatabase versioning conflict resolution corrected
- Python console startup time reduced
Questions about this release
Does it need a portal sign-in?
No. The licensing is handled locally in this build, so it opens straight to the project screen with the machine offline.
Are the extensions all available?
Yes. Spatial, 3D, network, geostatistics, image analysis and data interoperability are all enabled rather than sold separately.
Can it open projects from a newer version?
No. Project files are forward stamped and a newer project will refuse to open. Older projects upgrade on open.
Why is 3D rendering slow?
Scenes are the most demanding thing the application does. Below 4 GB of video memory a large scene will page constantly regardless of the processor.
Comments
Layout series of 800 pages exported without the crash this time. That fix was the reason I updated.
Big install but it went through clean. Python console has all the libraries already.
Comments are read before they appear. If a build stops working, say so here and it gets rebuilt rather than quietly left up.
Opens offline with every extension lit up. Ran a suitability model that used to need a separate licence.