opengeospatial / opengeospatial/ogcapi-features

Precision level filter responsibility?

Open
#17 6 comments 0 reactions 1 assignee View on GitHub

@cportele is already working on this.

Since Jun 3, 2024.

Part 7: Geometry Simplification
Dominant language
CSS
Stars
386
Forks
92
Avg merge
3d 4h
Merged PRs (30d)
15

Description

I'm wondering if limit precision should be managed in the spec with a filter like 'precision=6' or should be kept at data file/store behind the web service or both.

This viewpoint comes from 2 main reasons:

  • Sending ten digits precision has no meaning: see this summary https://gis.stackexchange.com/a/8674
  • The cost of geometry precision: for WGS 84, each coordinates with 10 digit precision would cost around 30% of the geometry size

Geometry with 6 digits (10 characters)

179.999999

Geometry with 10 digits (14 characters)

179.999999999

For point geometry, the gain is small but for lines and polygones, the improvement would be worth for the response size.

The other question it would open is about rounding or cutting for this precision, if considered in the core spec.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.