Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a2449f1209b021ca

Jump to content

Talk:Discrete global grid

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 7 years ago by Krauss in topic Review all article using OGC standard

New OGC API - DGGS Standard

[edit]

Review in light of the new OGC API - DGGS Standard, which is an implementation standard with concrete requirements for interoperability, while Abstract Specification Topic 21 (latest version 2.0) was conceptual. It defines requirements for implementing servers supporting querying and retrieving data using zone identifiers, and provides example Discrete Global Grid Reference Systems (Annex B).

Check

[edit]

Other DGGs:

Review all article using OGC standard

[edit]

The new OGC DGGS standard entitled “Topic 21: Discrete Global Grid Systems Abstract Specification” is online! It includes important information on definitions, conventions, functional algorithms, the core data model and more... see:

Krauss (talk) 23:51, 19 April 2019 (UTC)Reply

You can use also didactic texts and discussions:

grabularity

[edit]

What does grabularity mean? Should this be granularity?  Preceding unsigned comment added by 67.188.178.167 (talk) 03:19, 15 December 2018 (UTC)Reply

corrected

Notes about key-words and references

[edit]

About flat and hierarchical grids

[edit]

The term "flat" is perhaps preferable to the term "non-hierarchical". See "flat vs hierarchical" organizations, design architectures, clusters, structures, etc. About properties, see this didactic article comparing both for spatial-partition in games, as decisions:

  • flat grid, advantages:
    • Simpler: the flat data structure is simpler, and it is simpler to implement.
    • Memory usage is constant. (spatial partition can often be fixed ahead of time).
    • Faster: it can be faster to calculate or update, when objects change their positions.
  • hierarchical grid, advantages:
    • It handles empty space more efficiently.
    • Neighboring objects can be moved quickly.
    • The partitions can be imbalanced. When objects clump together, you get better performance, avoiding to waste memory in the empty areas.

Grid classification

[edit]

It is possible to adapt Grid classification article, and generalize relationships of the DGG areas...