{"canonical_url":"https://engineer.company/glossary/arcgis/","content_markdown":"# ArcGIS\n\n## What it is\n\nArcGIS is the name Esri gives to a whole family of geospatial software rather\nthan to one program, and the parts are easiest to tell apart by where each one\nruns.\n\nOn the desktop the current application is ArcGIS Pro, and its system\nrequirements list Microsoft Windows and nothing else. Before Pro came ArcMap,\npart of what was sold as ArcGIS Desktop. Esri's life-cycle page lists ArcMap as\ndeprecated and in mature support, with 10.8.x as its final series of releases.\n\nOn a server, the centre of the platform is a portal: the place where content,\nusers, groups and data services are created and shared. Esri hosts one as ArcGIS\nOnline, a subscription software-as-a-service product, and an organisation can\nrun its own with ArcGIS Enterprise. Data in a portal is published as services,\neach with its own REST endpoint. A feature service gives access to spatial and\nnon-spatial data in feature layers and tables and lets a client add, update,\ndelete and query features. Vector tile and map tile services store and serve\ntiles, and an image service processes and mosaics raster data on the fly. Every\nlayer has an address of its own, of the form `…/FeatureServer/0`, and a `query`\noperation that takes a `where` clause, a list of fields and an output format:\nHTML by default, JSON, GeoJSON or [protocol buffers](https://protobuf.dev/).\n\nOn the client side, Esri publishes Maps SDKs for JavaScript, Kotlin, Swift,\nFlutter, .NET, Qt and Java, plus plugins for Unity and Unreal Engine. The same\ndeveloper documentation also covers open libraries that can draw ArcGIS\nservices, namely Leaflet, MapLibre GL JS, OpenLayers and CesiumJS. For scripting\nthere is ArcPy, the Python package for geoprocessing tools and map automation\ninside ArcGIS Pro, beside the ArcGIS API for Python and ArcGIS REST JS for\nworking with portals and services from outside it. Access to anything that is\nnot public goes through API keys, OAuth 2.0 or a signed-in user.\n\nOn disk, the format that travels with ArcGIS data is the file geodatabase: a\ndirectory whose name ends in `.gdb`, holding each of its tables as `.gdbtable`\nfiles inside it. Outside Esri's software, GDAL's built-in OpenFileGDB driver\nreads file geodatabases, has written and updated them since GDAL 3.6, and has\nhandled raster layers in them since 3.7.\n\n## Why it matters\n\nWhen an organisation already runs ArcGIS, the decision is seldom whether to\nadopt it. The decision is where its edge sits: which data stays in the portal as\nservices, which is copied into a database the rest of the stack controls, and in\nwhich direction edits flow between the two.\n\nInside that edge, a lot comes ready-made. Editing, symbology, sharing with named\nusers and groups, analysis services and low-code app builders all work against\nthe same portal, and staff who know ArcGIS Pro can keep working the way they\nalready do. Publishing a layer as a feature service gives every other system an\naddress to read it from.\n\nThe edge is crossable from both sides, and that makes the choice a real one\nrather than a lock-in. A feature service speaks JSON and GeoJSON over plain\nHTTP. GDAL's ESRIJSON driver reads a feature service URL like a file and pages\nthrough the result on its own, so `ogr2ogr` can copy a hosted layer into PostGIS\nor a GeoPackage in one command. Esri's own documentation shows Leaflet and\nMapLibre GL JS drawing its services. In the other direction, GDAL has written\nfile geodatabases itself since 3.6, so data can go back in Esri's own format.\n\nWhat costs effort is everything that lives on both sides at once. A layer copied\nout of a portal is a second copy, and a second copy needs a schedule, an owner\nand a way to tell when it has drifted from the first. The desktop is\nWindows-only and commercially licensed, which shapes who on a mixed team can\nopen a project. And ArcPy ships with ArcGIS Pro and ArcGIS Server; even\ninstalled into another Python environment it still needs ArcGIS Pro on the\nmachine, so a pipeline built on it runs only where ArcGIS does.\n\n## What it looks like in practice\n\nArcGIS turns up in two projects on this site, and in neither is it the whole\nstack.\n\nFrom 2015 to 2022, the GIS Software Development Team Lead role carried\n[more than thirty GIS projects from development through deployment to support](/portfolio/led-30-gis-projects-from-build-to-support/).\nSome of their web maps called the ArcGIS APIs, and others the HERE APIs. The\nmaps themselves were drawn with Mapbox GL and Leaflet, and the application code\naround them was written in JavaScript, Python, PHP and SQL. The spatial data\nlived in PostgreSQL with PostGIS, and QGIS and JOSM handled the hands-on data\nwork, so ArcGIS sat beside that stack as a set of APIs the maps could call.\n\nFrom 2022 to 2024, as a Data Engineer on a large-scale geospatial analytics\nproject, ArcGIS was one of the tools for repair.\n[Spatial errors were diagnosed and corrected using GDAL, QGIS and ArcGIS](/portfolio/resolved-1000-issues-in-geographical-data/)\nin combination, with recurring cleaning tasks automated in Bash. PL/pgSQL and\nTransact-SQL procedures managed and transformed the geographic and temporal data\nin PostgreSQL and SQL Server, with PostGIS carrying the spatial queries and\nindexing. That repair work, ArcGIS included, closed more than 1,000 issues and\nhelped cut spatial query run times by 35%.\n\n## Where it goes wrong\n\nMost of the trouble sits at the edge between ArcGIS and everything else, where\neach side assumes the other behaves like itself.\n\n**A layer download stops at a round number.** A feature service returns at most\n`maxRecordCount` features per request, a limit set per service. When a query\nmatches more, the response sets `exceededTransferLimit` to `true`, and a client\nthat reads the features and ignores that flag holds a partial layer that looks\ncomplete. Where the layer reports `supportsPagination`, the client pages with\n`resultOffset` and `resultRecordCount`, or with `resultPaginationToken`, until\nthe flag comes back `false`. GDAL's documentation adds that paging is reliable\nonly with a sort on a field such as `OBJECTID`:\n\n```sh\nurl='https://gis.example.org/arcgis/rest/services/Parcels/FeatureServer/0'\nq='query?where=1=1\u0026outFields=*\u0026orderByFields=OBJECTID+ASC\u0026f=json'\nogr2ogr -f GPKG parcels.gpkg \"ESRIJSON:$url/$q\"\n```\n\n**Coordinates arrive in metres where degrees were expected.** Without an `outSR`\nparameter, a query returns geometry in the spatial reference of the service's\nmap, which may be a projected system measured in metres. For GeoJSON output, the\nreference says that from 10.8 the result follows RFC 7946 only when `outSR` is\nleft out or set to 4326. Any other value returns projected coordinates in a file\nthat still calls itself GeoJSON, and a web map reading it will place features\nfar from where they belong. Ask for `outSR=4326` whenever the consumer expects\nlongitude and latitude.\n\n**An ArcMap script stops working in ArcGIS Pro.** ArcGIS Desktop, which includes\nArcMap, used versions of Python 2, and ArcGIS Pro runs Python 3, a line Esri\ndescribes as only partially compatible. Within ArcPy, the `arcpy.mapping` module\nwas removed and replaced by `arcpy.mp`. With ArcMap deprecated, scripts written\nfor it are a migration waiting to happen. Pro's Analyze Tools For Pro tool flags\nthe issues that would keep Python code, or geoprocessing tools built on Python,\nfrom running, and doing that pass on purpose beats discovering it the day a\nmachine is replaced.\n\n**A file geodatabase opens read-only.** GDAL before 3.6 could read a file\ngeodatabase through OpenFileGDB but write one only through the separate FileGDB\ndriver, which needs Esri's FileGDB API library at build time. Raster layers\ninside a `.gdb` need GDAL 3.7 or later. When a pipeline writes a `.gdb` on one\nmachine and fails on another, compare the GDAL versions and driver lists before\nblaming the data.\n\n## Further reading\n\n- [Developer documentation](https://developers.arcgis.com/documentation/) —\n  Esri's map of the platform: SDKs, portal and data services, and security.\n- [Query (Feature Service/Layer)](https://developers.arcgis.com/rest/services-reference/enterprise/query-feature-service-layer/)\n  — every query parameter, including `outSR`, the output formats and the three\n  ways to page.\n- [Python migration from 10.x to ArcGIS Pro](https://pro.arcgis.com/en/pro-app/latest/arcpy/get-started/python-migration-for-arcgis-pro.htm)\n  — what changed between Python 2 and 3 and in ArcPy itself.\n- [ArcMap Life Cycle](https://support.esri.com/en-us/products/arcmap/life-cycle)\n  — the support status of ArcMap and why 10.8.x is the last series.\n- [ESRI File Geodatabase vector (OpenFileGDB)](https://gdal.org/en/stable/drivers/vector/openfilegdb.html)\n  — GDAL's driver for `.gdb` directories, with the versions that added writing\n  and raster support.\n- [ESRIJSON / FeatureService driver](https://gdal.org/en/stable/drivers/vector/esrijson.html)\n  — reading feature service results with GDAL, and how its automatic paging\n  works.\n\n\u003chttps://engineer.company/glossary/arcgis/\u003e\n","date_modified":"2026-10-20T21:59:50Z","description":"What ArcGIS covers from desktop to hosted services, where its data meets open tools, and the paging, projection and migration traps between them.","formats":{"gemtext":"https://engineer.company/glossary/arcgis/index.gmi","gopher":"https://engineer.company/glossary/arcgis/gophermap","html":"https://engineer.company/glossary/arcgis/","json":"https://engineer.company/glossary/arcgis/index.json","markdown":"https://engineer.company/glossary/arcgis/index.md","pdf":"https://engineer.company/glossary/arcgis/index.pdf"},"kind":"page","language":"en","title":"What is ArcGIS?","url":"https://engineer.company/glossary/arcgis/","version":1}