Saint-Lô Agglo has decided to draw up its Master Plan of Accessibility of Collective Transport — Agenda of Accessibility Programmed on its Slam Bus network following the enabling law n°2014-789 of 10 July 2014 and its various decrees, orders and orders supplementing it.
The accessibility master plan aims to facilitate the practice and use of the transport network for people suffering from these different disabilities.
A grid listing all the obstacles to be identified and their cost of accessibility was developed in collaboration with the technical services of Saint-Lô Agglo and the associations.
The diagnosis consists of an accurate identification of barriers to accessibility. It was carried out on the 198 stop points in the Slam Bus network. It takes into account the following handicaps: auditory, mental, motor armchair, motor out of armchair, visual blind and visually impaired.
**Collection context**
The 198 stop points in the Slam Bus network have been digitised, and at each point a number of features in terms of the accessibility of the stop point correspond.
**Attributes**
| Champ | Alias | Type |
| — | — | | — |
| ‘gid’ | ‘serial,PrimaryKey’ |
| ‘id_arret’ | Stop ID | ‘varchar’ |
| ‘name_arret’ | Stop name | ‘varchar’ |
| ‘com_arret’ | Common | ‘varchar’ | ‘com_arret’ |
| ‘line_1’ | Line 1 | ‘varchar’ |
| ‘line_2’ | Line 2 | ‘varchar’ |
| ‘line_3’ | Line 3 | ‘varchar’ |
| ‘line_4’ | Line 4 | ‘varchar’ |
| ‘line_5’ | Line 5 | ‘varchar’ |
| ‘line_6’ | Line 6 | ‘varchar’ |
| ‘type_arret’ | Stop Type | ‘varchar’ |
| ‘local_arr’ | Location of the stop | ‘varchar’ |
| ‘vit_voie’ | Track speed | ‘varchar’ |
| ‘type_mob’ | Type of furniture of the stop | ‘varchar’ |
| ‘pres_quai’ | Presence of a quay | ‘varchar’ |
| ‘ht_quai’ | Pier height | ‘int8’ |
| ‘lg_quai’ | Quay length | ‘int8’ |
| ‘photo_arr’ | Photography of the judgment | ‘varchar’ |
| ‘photo_mob’ | Photography of furniture | ‘varchar’ |
| ‘photo_ab1’ | Nearby photography 1 | ‘varchar’ |
| ‘photo_ab2’ | Nearby photography 2 | ‘varchar’ |
| ‘carte_pt’ | Stoppoint map | ‘varchar’ |
| ‘abs_quai’ | ‘int8’ |
| ‘quai_bas’ | ‘int8’ |
| ‘quai_court’ | ‘int8’ |
| ‘sol_aire’ | ‘int8’ |
| ‘dev2_aire’ | ‘int8’ |
| ‘p5_aire’ | ‘int8’ |
| ‘t_inf_350’ | ‘int8’ | ‘t_inf_350’
| ‘t_inf_285’ | ‘int8’ | ‘t_inf_285’
| ‘t_inf_210’ | ‘int8’ | ‘t_inf_210’ |
| ‘t_inf_150’ | ‘int8’ | ‘t_inf_150’
| ‘l_90_dvt’ | ‘int8’ | ‘l_90_dvt’ |
| ‘l_140_dvt’ | ‘int8’ | ‘l_140_dvt’ |
| ‘l_140_der’ | ‘int8’ | ‘l_140_der’
| ‘are_r_150’ | ‘int8’ | ‘are_r_150’
| ‘borne_aire’ | ‘int8’ |
| ‘cvmob_aire’ | ‘int8’ |
| ‘obs220_air’ | ‘int8’ |
| ‘trou2_aire’ | ‘int8’ |
| ‘trou2_r_a’ | ‘int8’ |
| ‘res2_aire’ | ‘int8’ |
| ‘res4_aire’ | ‘int8’ |
| ‘abs_zigzag’ | ‘int8’ |
| ‘abs_b_g’ | ‘int8’ | ‘abs_b_g’
| ‘abs_p_sign’ | ‘int8’ |
| ‘abs_nom_ar’ | ‘int8’ | ‘abs_nom_ar’
| ‘abs_nom_li’ | ‘int8’ |
| ‘abs_des_li’ | ‘int8’ |
| ‘sign_nom_l’ | ‘int8’ |
| ‘sign_nom_a’ | ‘int8’ |
| ‘info_inc’ | ‘int8’ |
| ‘sign_pan_i’ | ‘int8’ | ‘sign_pan_i’
| ‘esp_lib_hn’ | ‘int8’ |
| ‘p_100_175’ | ‘int8’ |
| ‘abs_che’ | ‘int8’ |
| ‘t_inf_90’ | ‘int8’ | ‘t_inf_90’
| ‘t_inf_140’ | ‘int8’ | ‘t_inf_140’
| ‘t_inf_120’ | ‘int8’ | ‘t_inf_120’
| ‘dev2_che’ | ‘int8’ |
| ‘p5_che’ | ‘int8’ |
| ‘p8_12_che’ | ‘int8’ |
| ‘sol_che’ | ‘int8’ |
| ‘abs_tp_che’ | ‘int8’ | ‘abs_tp_che’
| ‘abs_bat_tp’ | ‘int8’ | ‘abs_bat_tp’ |
| ‘bat_tp_hn’ | ‘int8’ |
| ‘abs_bev_tp’ | ‘int8’ | ‘abs_bev_tp’ |
| ‘abs_cv_tp’ | ‘int8’ |
| ‘abs_ds_tp’ | ‘int8’ |
| ‘borne_che’ | ‘int8’ |
| ‘cv_mob_che’ | ‘int8’ |
| ‘obs220_che’ | ‘int8’ |
| ‘trou2_che’ | ‘int8’ |
| ‘trou2_r_c’ | ‘int8’ |
| ‘res2_che’ | ‘int8’ |
| ‘res4_che’ | ‘int8’ |
| ‘conf_arr’ | Judgment Compliance | ‘varchar’ |
| ‘preco_arr’ | Preconisation for Stop | ‘varchar’ |
| ‘estim_trav’ | Estim_trav | ‘int8’ |
| ‘ita_arr’ | ‘varchar’ |
| ‘prog_sda’ | Programming within the framework of the SDA | ‘varchar’ |
| ‘comm’ | Comment | ‘varchar’ |
For more information, see [the metadata on the Isogeo catalog](https://open.isogeo.com/s/7b195c828aa74577afec7d6c223cddaa/RMmVNxgwo1AW7LHH42BuuWFiQGe40/r/256cb6a927164be2bc28b9d7e270df16).
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.