Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

L’analyse de référence permet de calculer les temps de trajet et / ou les distances le long des trajets de moindre coût (c’est-à-dire un trajet entre deux lieux qui minimise la durée totale du trajet pour ceux qui le parcourent, voir Ray and Ebener, 2008) entre deux groupes de centres de santé. Ce chemin est différent d’une ligne droite car il prend en compte les contraintes du paysage ainsi que les modes et les vitesses de déplacement de la population.

Par exemple, on voudrait connaître la distance et la durée du trajet entre chaque établissement de soins de santé primaires et l’hôpital de référence le plus proche dans une province donnée, ou s’assurer que la durée du trajet entre chaque structure de soins obstétricaux d’urgence de base (SONUB) et la plus proche structure de soins obstétricaux d’urgence complets (SONUC) est inférieure à 2 heures dans un pays donné.

À partir de la version 5.3.2 d'AccessMod, le module de mise à l'échelle a été amélioré pour fonctionner en mode parallèle, ce qui signifie qu'il peut tirer parti de tous les processeurs alloués à la machine virtuelle AccessMod. Cela accélère le calcul de la référence (voir les détails à l’Annexe 5). Si vous exécutez une analyse de référence avec un grand nombre de ressources, il est donc préférable de configurer d'abord votre machine virtuelle avec un maximum de processeurs et de mémoire (voir Section 4.2).

Dans l'exercice suivant, vous allez calculer les temps de trajet et les distances entre les "centres de santé" et les "hôpitaux" à partir du jeu de données de démonstration.

Les deux captures d'écran suivantes expliquent comment remplir les sections utilisées pour saisir les différentes couches et paramètres permettant d'exécuter l'analyse:

Données en entrée:

(1) Sous “Select merged land cover layer (raster)”, sélectionnez la couche raster contenant l'occupation du sol fusionnée, "land cover merged". Sous «Select scenario table (table)», sélectionnez la table de scénarios de voyage que vous souhaitez utiliser. Celle créée dans le module précédent dans le cas présent

(2) Dans le menu "From:", sous "Select existing health facilities layer (vector)", sélectionnez la couche vecteur contenant l'emplacement de la structure de santé à utiliser comme points de départ (De). Dans cet exercice, c'est "centres de santé".

(3) Dans le même menu, sous «Select facility ID field (unique)» et «Select facility name field (text)», sélectionnez le champ dans la table attributaire de la couche des structures de santé «De» qui contient les identifiants uniques, ainsi que le champ contenant le nom de chaque centre de santé.

(4) Dans le menu "To:", sous "Select existing health facilities layer (vector)", sélectionnez la couche vecteur contenant l'emplacement des structures de santé à utiliser comme points d'arrivée ("To"). Dans cet exercice , c’est «hôpitaux». Dans notre cas, les deux types de structures de santé se trouvent dans la même couche, nous sélectionnons donc la même couche que pour le point (2) ci-dessus (veuillez noter qu’il est possible de sélectionner une autre couche de structures de santé si les points d'arrivée sont stockés dans une couche séparée).

(5) Dans le même menu, sous "Select facility ID field (unique)" et "Select facility name field (text)", sélectionnez le champ dans la table attributaire de la couche des structures de santé "To" qui contient les identifiants uniques ainsi que le champ contenant le nom de chaque hôpital.


Scénario de déplacement:

(6)  Comme pour l'analyse d'accessibilité (voir la section 5.5.3), cette section permet d'importer le contenu d'une table de scénario externe et / ou de modifier manuellement les informations reportées dans les colonnes étiquette, vitesse et / ou mode. Nous allons simplement garder les mêmes valeurs que précédemment pour cet exercice.


Les sections de la deuxième partie du panneau d'analyse peuvent ensuite être remplies comme suit:

Sélection des structures de santé

(1) Dans la table «From», sélectionnez les structures que vous souhaitez utiliser comme points de départ («From»). Vous pouvez le faire «à la main» en cochant les enregistrements ayant la valeur «Health Centre» dans la colonne «hf_type» ou vous pouvez utiliser l'outil de filtrage en haut de la table pour sélectionner automatiquement ces centres. La deuxième option est particulièrement utile quand il y a un grand nombre de structures dans la couche et / ou à sélectionner.

(2) De même, dans le tableau «To», sélectionnez les structures que vous souhaitez utiliser comme points d'arrivée («To»). Cela signifie que les structures qui ont le type “Hospital” dans la colonne “hf_type” sont sélectionnés pour le présent exercice.


Paramètres d'analyse:

 (3)  Under “Type of Analysis”, select the option to do an anisotropic analysis as you did for the previous analysis

(4)  Select the “Limit the analysis to the closest destination point in time” option if you want to restrict the analysis and the output table to the closest health facility, in term of travelling time. We will not use that restriction in the present exercise.

(5)  If you want to limit the travel time for the analysis, you can specify this maximum travel time here under "Maximum travel time (minutes)". If you do so, those health facilities that can be reached in a time that is greater than this specified maximum travel time will not appear in the output tables. We will not use a maximum travel time in the present exercise, and you can therefore specify "0" in the entry field.

(6) Under “(Add short tags)”, give short tags to be attached to the different outputs of the analysis. We will use "referral" for the present exercise.


Validation:

(7)  The validation module should indicate that all fields have been correctly filled in (with a green “OK”). If this is the case, you can hit the "Compute" button to launch the analysis. If this is not the case, the "Compute" button will still be in red, and you will have to go through the warning and error message to find out what needs to be adjusted.


A transparent window with some text and a progress bar will appear in front of the panel while the analysis is being conducted. Please wait until this window disappears to continue using AccessMod. This analysis can take a lot of time to completed especially if the number of health facilities to be processed is high.

 In addition to the processed scenario table, as well as the speed and friction spatial distribution layers, this analysis will generate three output tables that will now be listed in the Available Layers section of the Data module, namely:

  • referral nearest by dist class: Table indicating which one of the selected “Hospitals” ("To" facility) is the closest by distance from each of the selected “health centers” ("From" facility).
  • referral nearest by time class: Table indicating which one of the selected “Hospitals” ("To" facility) is the closest by travel time from each of the selected “health centers”
  • referral class: Table containing all pair-wise results, i.e., the distances and travelling times for each “health facility” - "Hospital" pair

 You can archive these three tables, export them, and open them in Excel to visualize the results. The three tables present the same 6-column structure as presented in the following example (referral nearest by time class):

  • from_cat: unique identifier of the "From" health facility, as per the field selected from the attribute table of the health facility layer.
  • from_name: name of the "From" health facility, as per the field selected from the attribute table of the health facility layer.
  • to_cat: unique identifier of the "To" health facility identified through the analysis, as per the field selected from the attribute table of the health facility layer. In this case, this column contains code of the closest hospital by time from the "From" health facility.
  • to_name: name of the "To" health facility identified through the analysis, as per the field selected from the attribute table of the health facility layer. In this case, this column contains the code of the closest hospital, by time, from the "From" health facility.
  • distance_km: distance in kilometers between the two health facilities ("From" and "To")
  • time_m: travel time in minutes between the two health facilities ("From" and "To")

Note that, while both the distance and the travel time columns are included in the 3 tables, it is important to remember that the content of these columns is only significant for the analysis that each of these files is covering (i.e., closest by distance, closest by time or all possible combinations). In other words, the table shown as an example here above contains the indication of the hospital being the closest by time of each of the 5 selected health centers. The mention of the distance between the two facilities is therefore only included for extra information.

In the above table, for example, you can notice that reaching the Queen Elizabeth Centre Hospital from the Chabvala Health Centre requires about 700 minutes of travel, but these two facilities are separated by only 50 km. If you look at the geographic locations of these two centers in a GIS software, you will see that a river (i.e., a barrier to movement) and the lack of roads in this area leads to a long travel time before reaching the hospital.

This particular pair of health facilities also illustrates the impact that a barrier to movement can have on the output results. This calls for careful considerations when choosing the input layers and defining barriers to movements. For example, it that particular case considering the use of boats to cross the river at some point could have considerably reduced the travel time between the two facilities.

The header for the columns containing the unique identifier and the name of the health facilities will match the label for the field you have selected from the attribute table of the "FROM" and "TO" health facility layers.

 As mentioned here above, the distance and the travel time columns are included in each of the 3 tables, but their content is only significant for the analysis that each of the resulting file covers (closest by distance, closest by time or all possible combinations). In other words:

  • The "distance_km" column is only mentioned for information in the Excel file containing the results for the closest by time analysis (referral nearest by time class)
  • The "time_m" column is only mentioned for information in the Excel file containing the results for the closest by distance analysis (referral nearest by dist class)
  • Both columns are significant in the Excel file containing all the possible combinations (referral class)

 AccessMod generates only two tables when checking the "Limit the analysis to the closest destination point in time" option, namely:

1. The one containing the nearest facility within the given time for each "FROM" health facility (referral nearest by time class)

2. The one containing all pair-wise results (referral class)

In both tables:

  • Empty cells for the " to_cat ", "to  name ", "distance_km" and "time_m" columns indicate that there is no health facility within the given travel time for the "FROM" health facility.
  • A distance is only reported "distance_km" for the pair(s) corresponding to the nearest health facility by time.

    Starting with version 5.3.2. of AccessMod (that output only integer numbers for travel times), the probability of having two (or more) facilities with the same travel time has increased. If this is the case, the two (or more) facilities will be kept in the output tables, and it is the decision of the user to keep all of them or choose only one.

What happens if two facilities are equally "closest by time" ?
Starting with version 5.3.2. of AccessMod (that output only integer numbers for travel times), the probability of having two (or more) facilities with the same travel time has increased. If this is the case, the two (or more) facilities will be kept in the output tables, and it is the decision of the user to keep all of them or choose only one.

  • No labels