|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
A sample API conforming to version 1.0.0 of the OGC API - Processes - Part 1: Core Standard (ranked 146 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/q7dYGiMhkI9mLu5_oJj9z_a_sample_api_conforming_to_version_1_0_0_of_the_ogc_api___processes___part_1__core_standard_json.jsonGENERAL INFORMATION
A sample API conforming to version 1.0.0 of the OGC API - Processes - Part 1: Core Standard.
Copyright (c) 2021 Open Geospatial Consortium.
To obtain additional rights of use, visit http://www.opengeospatial.org/legal/
This document is an API definition document provided alongside the OGC API - Processes standard. The OGC API - Processes Standard specifies a processing interface to communicate over a RESTful protocol using JavaScript Object Notation (JSON) encodings. The specification allows for the wrapping of computational tasks into executable processes that can be offered by a server and be invoked by a client application.
Contact
- Name: Open Geospatial Consortium (OGC)
- Name: standards-team@ogc.org
- Contact API maintainers
License
- Name: OGC license
- See License
SECURITY 4/5
The security score of an API is computed as the number of OWASP top 10 vulnerabilities detected in the API.
- OWASP issues detected: API7:2023
PERFORMANCE 4/5
The performance score is derived from the median response time of the API, sometimes referred as p50. The median is the value separating the higher half from the lower half of a data sample, here the response times of the API.
- The median response time of the API is 180 ms .
Get p50 under 220 ms to get a 4/5 score.
RELIABILITY 5/5
The reliability score is derived from the number of inconsistent server responses, either server errors or non-conforming return values.
- Self compliance: response objects matched the declared response types.
- Server errors: the server did not return any 5xx error.
DESIGN 2/5
The design score reflects the quality of the specification file (usually named openapi.json or swagger.json). Having a high-quality specification file (with up-to-date types and examples) help developers understand the API and tools produce relevant documentation.
- Respects OpenAPI 3.0.3 schema specification.
- Contains comments and summaries.
- Contains examples.
- Does not contain duplicated objects.
Popularity 4/5
The popularity score is computed from the number of references to the API found on the internet. Have your API used by many developers to get a higher score!