diff --git a/bp/index.html b/bp/index.html index 823815b4..91914d11 100644 --- a/bp/index.html +++ b/bp/index.html @@ -2113,8 +2113,8 @@

Possible Approach to Implementation

A number of techniques can be used to deliver representations of geometries at an accuracy, precision, and size fitting the requirements of a given use case.

The following list, although not exhaustive, outlines the approaches most widely used, especially for the Web delivery and consumption of geometry data.

Choosing the right technique requires taking primarily into account whether the derived geometry is fit for the target use case. Technical limits — as network bandwidth and processing capabilities — are of course important, but secondary. Of course, the ideal situation is when you are able to find the technique offering the right trade-off between these two types of requirements.

-

Whatever option is used, the key requirement is that the derived geometry data are not replacing the original ones, but are made available as alternative representations.

-

, and provide general guidelines that can be used for the publication of alternative representations of geometries, providing at the same time information on their characteristics. These include, but are not limited to, the use of different URIs for different representations, and HTTP content negotiation. Moreover, whenever geometry data are made available in RDF [[RDF11-PRIMER]], specific properties can be used to specify the geometry type and the level of accuracy and precision. More specific examples are included in the approaches described below.

+

Whatever option is used, the key requirement is that the derived geometry does not replace the original ones, but are made available as alternative representations.

+

, and provide general guidelines that can be used for the publication of alternative representations of geometries, providing at the same time information on their characteristics. These include, but are not limited to, the use of different URIs for different representations, and HTTP content negotiation. Moreover, whenever geometry is made available in RDF [[RDF11-PRIMER]], specific properties can be used to specify the geometry type and the level of accuracy and precision. More specific examples are included in the approaches described below.

  1. Compress geometry data

    @@ -2140,7 +2140,7 @@

    Possible Approach to Implementation

    Providing geometries at different scales or resolutions is actually one of the first criteria to be considered for addressing different use cases. This is common practice in the geospatial domain, especially, but not only, for reference data. For instance, the dataset of the Nomenclature of Territorial Units for Statistics (NUTS) of the European Union is made available at five different scales — ranging from 1:1,000,000 to 1:60,000,000.

    Scale reduction uses a number of generalization techniques that can be used also outside this specific use case in order to provide geometries at different levels of accuracy and precision.

    @@ -2238,8 +2238,8 @@

    How to Test

  2. Compressed version of geometry data can be obtained via HTTP content negotiation or other mechanisms.
  3. Centroids and bounding boxes are made available, without the need of downloading and processing the relevant geometry data.
  4. It is possible to get a 2-dimensional representation of a 3-dimensional geometry.
    5. -
  5. Geometry data are available at different levels of precision, e.g., by allowing users to specify the maximum number of decimals in point coordinates.
    6. -
  6. Geometry data are available at different scales / spatial resolutions.
    7. +
  7. Geometry is available at different levels of precision, e.g., by allowing users to specify the maximum number of decimals in point coordinates.
    8. +
  8. Geometry is available at different scales / spatial resolutions.