This section provides an extensive explanation of the various services exposed by the OGC Resource Server, detailing their purpose, usage, and output. The OGC Resource Server adheres to key Open Geospatial Consortium (OGC) standards, facilitating the management and dissemination of geospatial data through RESTful APIs. These services include endpoints for managing geospatial features, collections, tiles, processes, and spatiotemporal assets. Additionally, the server implements audit and metering services for tracking API usage and enforcing compliance with resource access policies.
Additionally, anyone can verify if the server conforms to OGC standards by visiting the following links:
The Feature Services allow users to retrieve both individual geospatial features and all features within a specific collection. These features, representing points, lines, or polygons, are returned in GeoJSON format with detailed information about their geometry and properties. Users can retrieve a specific feature from a collection, or query for multiple features, filtering results based on parameters like bounding box (bbox), datetime, and limit. This service is useful for applications that require access to detailed geographic entities, supporting spatial queries or visualizations over a specified region or time period. The response includes links to related resources, enabling further exploration of the geospatial data.
For more information, you can refer here
The Tile Retrieval service is a key component of the server’s ability to support visualizations and map-based applications. A tile is a small, rectangular piece of a larger map or dataset that is retrieved individually based on its coordinates and zoom level. Tiles are especially useful for efficient rendering of large geospatial datasets, as they allow applications to load only the parts of the map that are currently in view. To retrieve a tile, clients must specify the collection ID, the tile matrix set ID, and the tile’s row, column, and zoom level. The server supports both raster tiles (such as PNG images) and vector tiles (such as Mapbox Vector Tiles). Depending on the type of data being requested (e.g., aerial imagery or vectorized building footprints), the server responds with the appropriate tile format. This service is optimized for high performance, as tile-based rendering is crucial for web mapping applications, mobile GIS apps, and any other platform that requires interactive geospatial visualizations. It supports requests for large-scale datasets by breaking them into small, manageable tiles, which can be requested and rendered on demand.
For more information, you can refer here
The Processes Service in the OGC Resource Server is highly adaptable, compliant to OGC Processes API, supporting various geospatial tasks such as feature collection onboarding, appending data to existing feature collections, tiles onboarding, and vector integration. The feature collection onboarding process allows users to add new geospatial datasets, while the appending process expands existing feature collections by adding new data seamlessly. The tiles onboarding process handles the integration of new tile layers for map visualizations, ensuring smooth tile setup. Additionally, vector integration facilitates tasks like transforming and analyzing vector data. The service also supports the generation of S3 pre-signed URLs, which are essential for securely uploading or accessing data on Amazon S3. This flexibility makes the Processes API a key tool for managing, updating, and interacting with geospatial collections and tiles, as well as facilitating secure cloud storage operations.
For more information, you can refer here
The STAC (SpatioTemporal Asset Catalog) API allows access to spatiotemporal assets such as satellite imagery and geospatial datasets, designed to manage large collections of geospatial data. The current implementation provides access to the STAC catalog, enabling users to browse available collections of geospatial data and their associated resources. Users can retrieve metadata for STAC collections, which provide detailed information about spatiotemporal data sets. Additionally, the API allows access to individual collections, where users can explore specific geospatial datasets. Each collection includes links to assets, which represent the actual data files or resources. The service is useful for cataloging and exploring geospatial data in a structured and manageable way.
For more information, you can refer here
The Coverage Services in the OGC Resource Server handle geospatial coverages, representing continuous phenomena like elevation, temperature, or rainfall across spatial areas. The Retrieve Coverage Data service allows users to access coverage data, with support for formats such as GeoTIFF or NetCDF, which can be processed in GIS applications for analyzing continuous data fields. Currently, users can only retrieve coverage data by specifying the coverage ID. This service is essential for applications working with continuous spatial data, including environmental modeling, climate analysis, or topography visualization.
For more information, you can refer here
The DX Auditing Server is responsible for tracking and logging all API calls made to the OGC Resource Server. Every successful API request is recorded in an audit log, capturing metadata such as the user ID, the resource ID accessed, the time of the request, and the response size. This service is essential for monitoring and managing access to geospatial resources, ensuring that users comply with access policies, and providing transparency in API usage.
The service processes audit logs asynchronously using RabbitMQ for queuing, making it efficient and scalable. Audit logs are especially important in environments where data access needs to be controlled or where usage-based billing is implemented. For example, an organization might track how many API calls a user makes in a given month and charge them accordingly. The audit service ensures that all API interactions are accounted for and can be reviewed later if needed.