Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Version Française disponible en bas de page

...

The purpose of having a standardized naming convention is to provide an organized framework for the datasets, ensuring interoperability between users and platforms. (See below for Naming Convention for Information Products)

...

  • ISO3: The first part of the naming convention consists of the ISO3 code.  For example: wrl, afg, alb, etc.  Additional codes can be created for transnational datasets and are not limited to 3 characters.  Example: hoa for horn of Africa. [OCHA taxonomy reference source]

  • Code + Data type: The feature code as defined in the Dataset Naming Code Table (See below) followed by the first letter of the data type where:

    • a = polygon

    • l = arc

    • p = point

    • t = text

    • r = raster (can be omitted for data where Code = image)

  • Sub-Code (if applicable): The sub-ode (if applicable) as defined in Dataset Naming Code Table (See below).  For example, for political boundaries sub-codes include: adm1, adm2, adm3, etc.

  • Scale (optional parameter, omitted for tabular data): The denominator for the scale of the dataset in the following form:

    • Example 1 – 1:1,000,000 = 1m

    • Example 2 – 1:250,000 = 250k

    • Example 3 – scale not known or of mixed scales (should be documented in metadata) = unk

    • Example 4 – scale not applicable for this dataset (such as utm zone boundaries or tabular data) = na (or omitted)

    • Example 5 – for raster data, this parameter is the nominal pixel size in kilometers, meters or cm = 30m, 130cm

  • Source: The acronym or short version of the source of the data. 

    • Example 1 – United Nations Cartographic Section = uncs

    • Example 2 – Government of Guinea = govgin

  • Additional Description (optional parameter):  This is a place holder for additional metadata that may make sense for a given type of dataset, such as:

    • a grid designator that may be used with datasets such as scanned toposheets or image datasets where the data is split into different files

    • a date stamp for data where the specific date of publication is critical (such as humanitarian profile or other frequently published datasets)

    • other metadata as needed

    • IMPORTANT NOTE: if the datasets are referenced by filename in other files (such as is common with MXD files) adding the date to the file name will often break the referring file when the date (and therefore the filename) is changed

...

Two sets of population data for a particular country, one has the population for major cities and the other population data for small towns. The data for major cities are labeled with a “1” and the data for small towns are labeled with a “2”.

  • Dataset 1: Major cities in Burundi from Government of Burundi at 1:1M scale

  • Dataset 2: Cities in Burundi from Government of Burundi at 1:M scale

Dataset Names (interim solution):

  • Dataset 1: bdi_pplp1_1m_gov

  • Dataset 2: bdi_pplp2_1m_gov

Feature Class Name (long term solution):

  • Combine the two feature classes to 1 using guidance from Verifying Geometry. The resulting label would be: bdi_pplp_1m_gov.

Special Case 2: Data do not span an entire country or region

...

Datasets not covering an entire country:

  • Dataset 1: IDP Camps in Aceh, Indonesia

  • Dataset 2: IDP Camps Afgooye Cooridor, Somalia

Resulting Dataset Names:

  • Dataset 1: idn_aceh_cmpp_idp_1m_unhcr

  • Dataset 2: som_afgooye_cmpp_idp_1m_unhcr

...

OCHA Field Map names are made of four parts separated by an underscore: 

  1. The catalog number, if in use (a good practice for catalog numbers is to have a three letter code for the country office and a sequential number) 

  2. A short map name (e.g. somalia_3w) 

  3. The paper size (A4, A3, A0, etc)

  4. The date of publication in YYYYMMDD format. 

Examples: 

  • SUM001_aceh_reference_map_a4_20050128

  • LBN001_Lebanon_reference_map_20081029

  • template_sample_a4_20080917

Conventions relatives à l'attribution des noms de fichiers

...

L’objectif d’une convention d’appellation standardisée est de fournir un cadre organisé pour les ensembles de données, assurant l’interopérabilité des données entre les utilisateurs et les plateformes. (Voir ci-dessous pour la convention des produits d’information)

...

Les noms des cartes de terrain produites par OCHA sont composés de quatre parties séparées par un tiret du bas :

  1. Le numéro de catalogue, s’il est utilisé (une bonne pratique pour les numéros de catalogues : avoir un code à trois lettres pour le bureau de pays et un numéro séquentiel)

  2. Un nom court (pour une carte) peut être par exemple : Somalia_3W

  3. Le format papier (A4, A3, A0, etc.)

  4. La date de publication au format AAAAMMJJ

Exemple :

  • SUM001_aceh_reference_map_a4_20050128

  • LBN001_Lebanon_reference_map_20081029

  • template_sample_a4_20080917