ArcGIS REST API
GISBox is a one-stop 3D GIS data editing, conversion and publishing platform that supports editing in multiple GIS formats such as OSGB/GEOTIFF/RVT, converting to 3DTiles/Terrain and publishing.
Introduction
ArcGIS REST API is a set of interfaces designed based on the REST architectural style for accessing and using the geospatial services published by ArcGIS Server. It allows users to obtain and operate various GIS resources on the server, such as map services, feature services, geometry services, etc., through URLs. Since ArcGIS Server 9.3, ArcGIS REST API has been providing services through which clients can access GIS services published on the server. For example, users can obtain the GIS service directory through a specific URL, or perform operations such as map output and query.
Data Format Overview
ArcGIS REST API supports multiple data formats: JSON/GeoJSON for efficient data interaction and cross-platform map rendering; HTML for directly embedding dynamic maps; PNG/JPG for outputting static maps; KML for supporting 3D visualization; GeoRSS for real-time event subscription; CSV for exporting tabular attribute data; Shapefiles need to be converted before being called; and TIFF and other formats are used for raster data (such as remote sensing images).
Pros
- Simple and open: Provides a simple and open interface to facilitate users to access and use the services published by ArcGIS Server. Users can directly obtain and operate the resources and operations in the service through the URL, which reduces the threshold for use.
- Support multiple languages: Any scripting language that can call RESTful Web services and parse responses through HTTP can be used, such as Python, Java, JavaScript, etc., which is convenient for developers with different technical backgrounds to integrate and develop.
- Rich in functions: Supports a variety of geospatial service operations, such as map output, click to view, search, generate KML, etc., which can meet the diverse geographic information processing needs of users.
- Dynamic update and monitoring: In the geoprocessing service, two options for running tasks, synchronous and asynchronous, are provided, which are suitable for jobs with different processing times, and the geoprocessing results can be visualized through the result map server, which is convenient for users to track and monitor the task status.
Cons
- **Uncertainty of search results: **Its search function may have problems when programmatically finding specific records. For example, the order of results may be different each time a search is performed, which is not very friendly for automated script development that needs to accurately obtain specific records.
- **Learning cost: **Although the interface design is relatively simple, it still takes some time for beginners to understand and master how to correctly construct URL requests, process response results, and call various service operations.
- **Dependence on server status: **As an interface for accessing ArcGIS Server services, its performance and availability depend on the running status of ArcGIS Server. If the server fails or has performance problems, it will directly affect the use of ArcGIS REST API.
Application Scenario
OGC API - Coverages is suitable for processing complex raster stacks such as satellite imagery and hyperspectral data in the remote sensing field, extracting environmental data (such as meteorological temperature and ocean salinity) by region or time series in the meteorological and oceanographic fields, and geospatial data analysis that requires standardized access to raster data and supports spatial, temporal and attribute queries for integration into GIS systems for analysis.
Example
- An architectural overview of how your services interact with geodatabases and ArcGIS Enterprise.
