Skip to content

Apply multiple enhancement for v3 endpoints

Yifei Xu requested to merge aws-v3-improved into master

Type of change

  • Bug Fix
  • Feature

Does this introduce a change in the core logic?

  • [YES]

Does this introduce a change in the cloud provider implementation, if so which cloud?

  • AWS
  • Azure
  • GCP
  • IBM

Does this introduce a breaking change?

  • [YES]

Gitlab issues:

  1. crs-conversion-service#42 (closed)
  2. crs-conversion-service#43 (closed)
  3. crs-conversion-service#44 (closed)
  4. crs-conversion-service#41 (closed)

GET v3/coordinate-transformation and GET v3/coordinate-reference-system

  • Return all properties for these two endpoints
  • Edit integration tests

POST v3/coordinate-transformation and POST v3/coordinate-reference-system

  • Make CodeSpace non-mandatory for POST CRS and POST CT endpoints
  • Remove the "*" at the end of the query to avoid matching everything
  • Add query support for horizontalAxisUnitId and verticalAxisUnitId for POST v3/coordinate-reference-system
  • Fix unit tests and integration tests data
  • Edit unit tests
  • Add integration tests

POST v3/area-of-use

  • Change name of endpoints to POST v3/points-in-aou (and related file and variable names)
  • Remove "degreeDistanceOutside" from output
  • Remove "SuccessPoints" from output
  • Add a zero-based index of the failed points
  • Round all distances to nearest 1km (integer)
  • Ensure points exactly at the boundary are counted as PASS (within ~0.5km)
  • Change the formula to calculate distance
  • Extract distance calculation as a separate class
  • Fix 400 error for multi-polygon cases
  • Add unit test and integration test

Update and fix typos in Swagger doc

Upload postman collection file for V3

Edited by Yifei Xu

Merge request reports