Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OGC Code sprint july 2024 suggested doc improvement #144

Merged
merged 3 commits into from
Jul 12, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added docs/assets/img/map-context-menu-copy-extent.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
20 changes: 20 additions & 0 deletions docs/elements/meta.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,26 @@ values of `name` related to maps include:
| cs | A case-sensitive [coordinate system abbreviation](../input#units). |
| zoom | (min=_minimum zoom value_,max=_maximum zoom value_,)(value=_current zoom value_) |

:::tip

The grammar rules for the `<map-meta name="extent" content="..."></map-meta>`
`content` attribute require that you specify coordinates of the top-left and
bottom-right corners of the extent being marked up. You must specify the axis values of the
extent as values for a set of four comma-separated keys which identify the coordinate
system being used (i.e. pcrs, gcrs, tile, tilematrix, map or tcrs) by virtue of
the axis names. For example `top-left-easting=-8433179` identifies that the
coordinate system being used is pcrs. You cannot mix coordinate systems within
a single `content` attribute value, for example `top-left-easting=-8433179, top-left-latitude=49.02174,...`
is not legal.

You can copy a correctly marked-up `<map-meta name="extent" content="...">` value
onto the clipboard for the current map viewport, in pcrs coordinates (by default),
via the map context menu Copy > Extent item as shown below:

![Copy extent context menu](../assets/img/map-context-menu-copy-extent.png)

:::

---

| <!-- --> | <!-- --> |
Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
21 changes: 21 additions & 0 deletions i18n/fr/docusaurus-plugin-content-docs/current/elements/meta.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,27 @@ L’attribut `name` indique le type de métadonnées définies. Les valeurs poss
| cs | [Abréviation du système de coordonnées] sensible à la casse](../input#units). |
| zoom | (min=_valeur de zoom minimale_,max=_valeur de zoom maximale_,)(value=_valeur de zoom actuelle_) |

:::tip

Les règles de grammaire de l'attribut `<map-meta name="extent" content="..."></map-meta>`
`content` exigent que vous spécifiiez les coordonnées des coins supérieur gauche
et inférieur droit de l'étendue à marquer. Vous devez spécifier les valeurs d'axe
de l'étendue en tant que valeurs pour un ensemble de quatre clés séparées par des
virgules qui identifient le système de coordonnées utilisé (c'est-à-dire pcrs, gcrs,
tile, tilematrix, map ou tcrs) en vertu des noms d'axe suivants des noms d'axes.
Par exemple, `top-left-easting=-8433179` indique que le système de coordonnées
utilisé est pcrs.

Vous ne pouvez pas confondre les systèmes de coordonnées dans une même valeur
d'attribut `content`, par exemple `top-left-easting=-8433179, top-left-latitude=49.02174,...`
n'est pas légal. Vous pouvez copier une valeur `<map-meta name="extent" content="...">`
correctement marquée dans la planchette à pince pour la fenêtre de visualisation
actuelle de la carte, en coordonnées pcrs (par défaut), grâce au menu contextuel
de la carte Copier > Étendue, comme indiqué ci-dessous :

![Copy extent context menu](../assets/img/map-context-menu-copy-extent.png)

:::
---

| <!-- --> | <!-- --> |
Expand Down
12 changes: 6 additions & 6 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading