TOPIC: MODELS TRANSFORMATION AND DATA INTEGRATION IN OPENSTREETMAP FOR ACCESSIBILITY: FEASIBILITY STUDY FROM THE GEOSTANDARD MSc Research Project

Models transformation and data integration in OpenStreetMap for accessibility. (Biagi, Brovelli, and Stucchi 2020) ...

INTRODUCTION

OpenStreetMap (or "OSM") is an international project founded in 2004 with the goal of creating a free map of the world. This map of the world is freely editable and made by Internet users.

OSM data can be used in a variety of ways, including producing paper and electronic maps, geocoding addresses and place names, and route planning. However, there is often a lack of accuracy when it comes to road accessibility for people with reduced mobility. Hence, The French Ministry of Environment has been working since 2020 on the design of a data standard, led by the CNIG and in collaboration with the CEREMA, professionals in the field and representatives of the people concerned for collecting data on road accessibility, for people with disabilities or reduced mobility. It is in this perspective that we will work on the project: "Models transformation and data integration in OpenStreetMap for accessibility: feasibility study from the geostandard". It will be a question of studying the possibilities and measures of merging CNIG data with OpenStreetMap data in order to improve the accessibility of pathways for people with reduced mobility.

Models transformation and data integration in OpenStreetMap for accessibility.

I.1. Context

The setting up of the project of model transformation and data integration into OpenStreetMap for accessibility is justified by the recent initiative of the Ministry of Environment, in application of the law of orientation of mobilities (LOM) to facilitate the constitution of a collaborative database, resulting from a regular and coordinated collection by local communities. This initiative will lead to the establishment by each community of a high precision geostandard database to facilitate road accessibility. Therefore, it will be essential and necessary to be able to transform and integrate these data into OpenStreetMap, which is where our project comes from.

It will contribute in an undeniable way to the resolution of problems such as:

 Road accessibility of people with reduced mobility;  Lack of geographical accuracy of data in OpenStreetMap;

 Heterogeneity of data quality;  Evolution of OpenStreetMap for accessibility.

I.2. Problematic

Moving for people with disabilities is often difficult with a high level of uncertainty due to the lack of geographic accuracy of data in OpenStreetMap. Accessibility is not yet guaranteed on all travel routes. Until now, the only sources that could really be used with a sufficiently high level of accuracy were proprietary databases, hence the Mobility Orientation Law (published in the Official Journal on December 24, 2019) stipulated the obligation for road management authorities to create databases describing the accessibility of the route in order to feed the route planners and allow disabled people to build accessible routes. So, a way must be found to help communities to integrate these data into OpenStreetMap. Designing a tool to transform models and integrate data into OpenStreetMap for accessibility is therefore necessary and imperative.

I.3. Proposed solution

There is a need to improve the autonomy, safety and fluidity of travel for people with reduced mobility. To achieve this, the need for an accurate, comprehensive and universally accessible route planner is clear.

On one hand, it is urgent to collect data from local authorities in the CNIG accessibility standard.

On the other hand, it is necessary to integrate these data into OpenStreetMap in order to:

 Create a safer route calculation for people with disabilities or reduced mobility;  Reduce the uncertainty and lack of precision of geographical data in OpenStreetMap; Models transformation and data integration in OpenStreetMap for accessibility.

 Ensure the accessibility of routes to anyone in need.

We therefore thought of the project: Models Transformation and Data Integration in OpenStreetMap for Accessibily, which fits perfectly with the impetus given by the Ministry of the Environment to design a collaborative database that meets the needs of people with disabilities or reduced mobility. This project will help communities to integrate their data directly into OpenStreetMap in order to make them accessible and usable by all.

II.

PRIOR RELATED WORK

II.1. Industrial solutions

II.1.1. Presentation

Until now, the only sources that can really be used to calculate routes for people with reduced mobility with sufficient accuracy are proprietary databases.

Wegoto develops solutions for capturing geographical and topographical data in the field. It assists local authorities in modelling their accessibility databases and creates mobility databases for pedestrian, scooter and bicycle, for private and shared use. Wegoto has several applications to its credit, including:

 Wegoto: a mobile application to help with soft navigation that allows each user profile to calculate the most suitable multimodal itinerary and to be guided according to its profile.

It is an itinerary calculator adapted for pedestrians, cyclists, PRMs, the disabled and transport.

 WegoTrack: the software WegoTrack collects all the cartographic data of the outdoor pedestrian travel chain in the field. It has an input interface designed as a metaphor of reality allowing a clear and fast input of the collected data.

 OSM converter: the program converts the data from the WegoTrack collection software to OSM format.

We also have the application "Acceslibre": a collaborative platform for accessibility. It allows everyone to inform and consult the accessibility data of ERP and thus facilitate the movements of people with disabilities.

II.1.2. Limits

The solutions developed so far are proprietary and therefore still not accessible to all.

The applications developed by Wegoto undeniably contribute to the improvement of soft mobility, but are nevertheless limited in certain aspects:

Models transformation and data integration in OpenStreetMap for accessibility.

8

 Wegoto is not complete, the territories where they have actually made the acquisition are Grenoble and Isère.

 WegoTrack is a proprietary application, so it is not accessible to all communities and it is the same for their OSM converter.

 Acceslibre is limited and then not sufficient to guarantee the safe travel of persons with reduced mobility because it is just concentrate on the accessibility of ERP and it don't describe the pathway inside those ERP. walking along streets and paths, and around areas recording their every move using Global

II

Positioning System (GPS) receivers [START_REF] Brovelli | Openness and Community Geospatial Science for Monitoring SDGs -An Example From Tanzania[END_REF]. OpenStreetMap contains details of much more than just roads. All mappers are free to add any geographic object they find, so people have added phone boxes, bus stop, parks, public toilets, places of worship, and much more. The data and the project are both intended to give mappers as much flexibility as possible, so they can map features as accurately as they can.

The OpenStreetMap (OSM) geographic data model has three principal object types: nodes (points), ways (polygons and polylines), and relations (logical grouping of all three object types to express real-world geographical relationships) completed by tags which describes every object [START_REF] Pruvost | Exploring Data Model Relations in OpenStreetMap[END_REF].

 Tags: They are "key=value" pairs that can be linked to each geographic feature in OpenStreetMap. These attributes describe the geometric object. Both the key and the value are strings, with a maximum length of 255 characters (including spaces), with one constraint: each key must be unique for the same element. If a geographic object has no attributes, most rendering engines will not represent it at all.

 Nodes: a geographic point is called a node, and it is represented by its latitude, longitude, and as many attributes as necessary. For example, nodes are used to represent stores, bus stops, benches, vertices and mailboxes. A node without attributes will always be a subelement of another element.

Models transformation and data integration in OpenStreetMap for accessibility. We shall now provide a more formalized representation of OpenStreetMap.

 In OSM, a node N is a geographic coordinate with tags Nt where the set of tags can be empty.

 A way w is an ordered set of nodes (N0, N1, . . . Nn-1). If the way w represents a polyline feature such as a road or path, then N0 is different from Nn-1. However, if the way w represents a closed polygon feature such as a building or a lake then N0=Nn-1. For polyline ways, there should always be a minimum of two nodes while for closed polygon features there should always be a minimum of three nodes. A way can also have a set of tags Wt. The set Wt can be empty, but normally it is encouraged that this is not the case.

 Finally, in OSM a relation R is an element representing the logical relationship between objects. A relation r is represented by a set containing at least one object. A relation can contain any combination of existing nodes, ways and even relations themselves. These are called members. As is the case with nodes and ways relations can also have a set of tags Rt associated with them. As before this set can be empty but this is discouraged.

II.2.1.3. Types of relations

According to both the OSM Wiki and TagInfo, the five most frequently occurring types of relations (where Rt contains the tag for type) are outlined as follows:

 Multipolygon: a multipolygon relation can have any number of ways and these ways must somehow form valid rings to build a multipolygon from. Multipolygon relations are used to represent complex areas. Generally, the multipolygon relation can be used to build multipolygons in compliance with the OGC Simple Feature standard. Subsequently multipolygons allows for the expression of arbitrarily complex relations within OSM.

 Restriction: relations with the type=restriction key allows the modeling of different types of traffic flow restrictions at junctions, intersections, etc. A turn restriction at a junction is represented by a relation that has a set of tags describing the type of turn restriction.

This turn restriction relation is not necessarily limited to turns. It can also be used in a number of other situations.

 Route: this type of relation models a regular known line or path of travel. According to the OSM Wiki routes can consist of paths taken repeatedly by people and vehicles: a ship on the predefined shipping route, a car on a numbered road, a bus on its route or a cyclist on a national route.

 Public Transport: relations with this type=public_transport allow for the description of relations used in the public transport tagging scheme in OSM. This relation corresponds Models transformation and data integration in OpenStreetMap for accessibility.

to the description of all types of public transport stops, stations, halts, areas or similar. As stated in the OSM Wiki pages "A stop area consists of everything regarding the embarkation and disembarkation of a specific public transport vehicle or service" (OSM Wiki, OpenStreetMap Relation Type-Public Transport). In the example of a specific railway line, this includes the adjacent platform, services on that platform, buildings, and information describing it (platform number, identification, etc.).

 Route Master: relations of type type=route_master contain all the direction and variant routes and information belonging to a whole route service. Routes or services are represented by vehicles that always run the same way with the same reference number.

Each direction of a route should be tagged as a separate relation. If a route has several variants (e.g., different way at weekend), these variants should also be in separate relations.

In addition to relations with the type tag key assigned to one of the five values above, there are other frequently occurring types of relations in OSM including boundary, associatedStreet, site, waterway and bridge. However, these types of relations appear much less frequently within the global OSM database.

II.2.2. Geostandard

The CNIG Accessibility Standard, also known as geostandard, is a standard for collecting data on road accessibility for people with reduced mobility or disabilities. The accessibility information is particularly interested in:

 the path on the road and in the public space;

 Access routes to public transport stations and stops, whatever the mode, including connecting routes;

 Access to public administrative and social services and more generally to all establishments open to the public.

The CNIG Accessibility standard defines the data model and the catalogue of objects required to describe accessibility for the travel chain in the areas of roads and public spaces, and the built environment, here restricted to establishments open to the public (ERP).

It proposes a base of essential data to ensure a non-blocking path for disabled people or people with reduced mobility. It includes all the technical and organisational specifications for storing and exchanging the corresponding geographical data in digital format.

The geostandard defines 09 main types of objects:

Models transformation and data integration in OpenStreetMap for accessibility.

12  Paths: it describes physical paths to get from one point to another on foot (or in a wheelchair, etc.).

 Path_Trunk: a space opens to the public in which the person moves. The pathway section combines physical and PRM -DSP traffic-related characteristics.

 Node: extremities of a pathway section.

 Obstacle: an element in the pathway that may impede or prevent movement.

 Circulation: a "standard" path on a regular surface, without access equipment. For example: a path on a sidewalk, a place, a pedestrian area, etc.

 Access equipment: includes all access equipment:

 Crossing: any marked area allowing pedestrians to cross at level the lanes reserved for road, cycle or public transport traffic.

 Ramp: a sloping structure used to cross a difference in level or a change of level or floor.

 Staircase: a structure for going up or down, consisting of a succession of steps.

 Escalator

 Conveyor belt: flat surface with a translational movement, used to transport people.

 Lift: vertical transport system used to move people up and down.

 Elevator: system for overcoming a difference in level, equipped with a platform or a nacelle.

 Entrance: opening allowing passage.

 Selective passage: device allowing the passage of pedestrians, but discouraging that of cycles and motorised vehicles.

 Quai: equipment of a transport mode allowing access to the vehicle.

 PMR parking: vehicle parking space on a road reserved for people with reduced mobility.

 ERP: establishment receiving the public or installation open to the public (IOP).

 ERP pathway: pedestrian pathway within the site of an ERP, starting from an entrance or PRM parking space and ending at an entrance or reception area of the ERP.

Models transformation and data integration in OpenStreetMap for accessibility. Models transformation and data integration in OpenStreetMap for accessibility.

14

II.2.3. Data integration

Data are different in source, acquisition approach, data model, data format, coordinate and projection, semantic expression and other aspects. So the multi-source data can't be used to do data fusion directly, we have to perform data integration first.

The task of data integration is to eliminate the differences among multi-source spatial data.

According to certain standards, those multi-source data are integrated into one uniform system, through which the direct management and structure of multisource data can be realized.

Content and techniques of multi-source data integration (chen et al. 2013)

 Unified Coordinates: different data use different coordinates and the current coordinates in using includes: old BJ54, new BJ54, CD80, WGS84 and CGCS2000 coordinate. The using of CGCS2000 would influence the geometry precision of data in old coordinates, so unified coordinates is necessary and the coordinates can be transferred through three parameters or seven parameters models. Geostandard data use Lambert 93 coordinates and OSM data use WGS84. In order to unify these coordinates, we will use the tool POSTGIS in which unified coordinates methods have already been implemented.

 Projection Transformation: according to the mapping purposes and locations, the existing multi-source data use different projections. It is necessary to set up the corresponding Models transformation and data integration in OpenStreetMap for accessibility.

relationship of the points from different planes through projection transformation. For vector data, the projection can be transferred through certain equation. But for raster data, the new image can't be built through point-by-point conversion, because point-by-point conversion may lead to slot and overlap in the new image. So the projection transformation of image is through reversed calculation (Shaomei Li, 2004). All these methods are theoretical, so we will use POSTGIS in order to perform projection transformation.

 Data Format Exchange: Different software and system use different data models to describe the world, which leads to different data formats. The common used data models are: Arc/InfoMapInfo, MapGIS, AutoCAD, SuperMap and so on. Each data model has its own data format and the exchange methods are ripe, but in our case we will use the OSM format, and the CNIG standard format which is completely new. Hence There is not yet an exchange method for these two formats.

 Data Compression: For the GPS data, the sampling interval is short, so large numbers of redundant points exist in GPS data, which makes the lines not smoothing after symbolization and hard to edit. So the redundant points need to be compressed, simplified and generalized according to the standards of certain scale. The common compression algorithms include: Ramer-Douglas-Peucker and vertical distance which is used to simplify a polygon or polyline by removing points. This method is theoretical and doesn't take in account the semantic associated to the graph, in our solution, we will combine semantics and geometry.

II.2.4. Data matching

Different data has different ways of expression, and data matching is just to identify the same feature in different datasets through similarity measurement of geometry, semantics and topology and build the corresponding relationships [START_REF] Feng | A detailed investigation on the methods of object matching[END_REF].

In general, the matching process of vector data can be categorized in three ways: geometric, topological and semantic matching.

Models transformation and data integration in OpenStreetMap for accessibility.

16  Topological similarity is often combined with geometric measurement and depends on the relationship of features. Therefore, approved approaches are the Spider-Function [START_REF] Rosen | Match criteria for automatic alignment[END_REF] and the Round-Trip-Walk [START_REF] Filin | The Detection of Corresponding Objects in a Linear-Based Map Conflation[END_REF], both depending on matched nodes and adjacent edges.

 Current research on similarity measurement often deals with semantic matching, usually based on thematic attributes, data structure or geo-ontologies [START_REF] Weis | Detecting Duplicate Objects in XML Documents[END_REF]Naumann 2004, Giunchiglia et al., 2007).

All these methods are theoretical, hence our solution.

Furthermore, for different kinds of geographical entities, the corresponding matching algorithms are different. The point feature is comparative simple which is through location, structure and semantic similarity. For linear feature, the factors of location, shape, dimension, direction, and topology are considered synthetically [START_REF] Xiaoya | A shape multilevel description method and application in measuring geometry similarity of multi-scale spatial data[END_REF]. While the areal feature seldom uses topology comparing to the linear feature. But the accurate rate of the matching algorithms at present is still has a long way to go, so we have to improve this in our project. Once the data matching is finished, the work of data fusion is relatively simple to develop.

II.2.5. Data fusion

Multi-source data integration eliminates differences and data matching builds the corresponding relationship of the same feature in different datasets, these processing don't change the existing data qualitatively and still keep their own characters as before. The data fusion is just the qualitative change step, which gathers the advantages of existing data extremely to obtain better new data through certain processing.

Models transformation and data integration in OpenStreetMap for accessibility.

Spatial data fusion describes any kind of combination of spatial data from multiple sources. It targets either the generation of a new data source that is superior to any of the inputs or the extraction of meaningful information with regards to a specific application (J. Zhang 2010).

A spatial data relation is any kind of connection that exists between spatial data. This includes all associations between spatial datasets and between different feature views. Spatial data relations are essential to the fusion process, because they determine how data can be combined and which conclusions can be drawn from that combination.

The conventional way to solve a specific spatial data fusion task is to load the desired input data into a GIS software tool that offers corresponding processing capabilities. Basic fusion functionality is already provided by major GIS vendors, e.g. available in ArcGIS or the Feature Manipulation Engine (FME). More specialized tools include the Java Conflation Suite [START_REF] Blasby | GIS Conflation using Open Source Tools[END_REF], the Data Fusion System (Stankute and Asche 2012), FAGI-gis [START_REF] Giannopoulos | FAGI-gis: A Tool for Fusing Geospatial RDF Data[END_REF] or Hootenanny9. We also have QGIS which functions as Geographic Information System (GIS) software, allowing users to analyze and edit spatial information, in addition to compose and export graphical maps. Moreover, there is GDAL, a translator library for raster and vector geospatial data formats that is released under an X/MIT style Open Source License by the Open Source Geospatial Foundation. In our case, in order to perform the fusion of OSM and Geostandard data, we will use the tool POSTGIS which is a spatial database extender for PostgreSQL object-relational database. It adds support for geographic objects allowing location queries to be run in SQL.

II.2.6. Data coverage

A coverage is a mapping of one aspect of data in space. It represents a "domain" (the universe of extent) in terms of characteristics expressing a range of values.

II.2.6.2. Degree of information

Geostandard takes into account more attributes and fields than OpenStreetMap. It includes fields for hearing aids, for the presence of visual, tactile and sound guidance systems, and even for PRM parking lots.

OpenStreetMap is less informative in this sense and just provides basic characteristics of places.

II.2.6.3. Degree of geographical accuracy

In OSM, the accuracy of the cadaster is of the order of one meter. Orthophotos used for plotting often have a precision of the order of 20 to 50 cm for a pixel.

The degree of geographical precision in the geostandard is 10 cm.

III. PROJECT PLANNING

III.1. Gantt diagram

IV. MATCHING STUDY BETWEEN OPENSTREETMAP AND CNIG

Here, we will study in detail the similarities and differences between OpenStreetMap data and CNIG data in terms of geometry and semantics.

IV.1. Geometry overview

Geometries, coordinates and references to coordinates, locate objects in space.

IV.1.1. Coordinate system

Geographers use coordinate systems to identify locations, and these systems use abscissa and ordinate coordinates. Points on the globe are often referenced by longitude (East-West) and latitude (North-South). For GPS receivers, the most common standard for determining the coordinate system and origin of a point is WGS84.

However, units of measure in degrees are not appropriate for measuring surfaces, shapes, distances and/or directions. Therefore, a projected coordinate system is generally used. This system allows to perform analyses on distances or angles and to obtain accurate measurements.

OpenStreetMap is based on GPS measurements and is therefore able to detect and read the WGS84 system. The projected coordinate system is WGS84/EPSG:4326 measured in meters.

Indeed, there are different types of projections that focus on different aspects of the world. Some projections are better suited to a small area, describing it more accurately, while others are more respectful of distances. Some projections preserve directions, while others better preserve shape.

Distortion, or distorted representation of the earth, is always a problem. Because of concerns about distortion, particular projections, such as the Lambert Projection and the Universal Transverse Mercator (UTM) Projection, are used for small local areas, while other projections, such as Mercator, are better suited for global projections, while minimizing distortion.

OpenStreetMap is a world map, which justifies the use of the spherical Mercator projection for map rendering. The CNIG accessibility standard was created to represent the geographical data of local authorities, hence the use of the Lambert 93 projection.

Data from OpenStreetMap can be reprojected or converted to any projection system and vice versa. In this project, we will use QGIS software to bring both types of data to the EPSG:4326 coordinate system.

IV.1.2. Study of the geometries

In the data format, PostGIS allows several types of geometries. These types include point, line string, polygon, multipoint, multiline string, multipolygon and geometrycollection (L. Zhang and Yi 2010).

 POINT: a point represents a single location on the Earth. It is represented by a single coordinate (including either 2, 3 or 4 dimensions). Points are used to represent objects when exact contour detail is not important at a given scale. In OpenStreetMap, geometries are defined by the data type (Node, Way, Relation). In the CNIG accessibility standard, geometries are explicitly specified for each type of object; there are three main types of geometry: point, linestring and surface.

The following table shows a correspondence study between the geometries of OpenStreetMap objects and those of the CNIG accessibility standard.

Models transformation and data integration in OpenStreetMap for accessibility.

IV.2. Study of semantics of OSM and CNIG data

The aim here is to make a correspondence study on the semantic level between OpenStreetMap data and the CNIG accessibility standard data. To do so, we will first list the tags specific to disabled people or people with reduced mobility present in OpenStreetMap and their correspondences in the CNIG accessibility model. Then, for each object of the CNIG standard we will give the OSM tags equivalent to each of its attributes when they exist.

The appendixes used in this section were produced in collaboration with Cyril from the company Wegoto.

IV.2.1. OpenStreetMap accessibility model → CNIG accessibility standard

IV.2.1.1. Sidewalks

The presence of sidewalks in a street can be defined with a specific tag ("sidewalk = no/left/right/both") of the street: however, this simple way does not allow to store several attributes that are needed to quantify the accessibility of the sidewalks (Biagi, Brovelli, and Stucchi 2020).

A sidewalk can therefore be added as an independent way that is parallel to the street and intersect it and other streets in the crossings. The used tags are "highway = footway" combined with "footway = sidewalk"; it corresponds to the object "Circulation" in the CNIG accessibility standard. The tag "width = m", in meters, provides the fundamental information on the sidewalk width; it corresponds to the attribute "largeurPassageUtile" in the CNIG accessibility standard.

The surface is an important aspect of sidewalk. it is described by two different keys: "surface"

and "smoothness". When referred to sidewalks, "surface" can assume the following values:

 "paved" just indicates that the way is paved with some material;

 "asphalt" means that is composed of asphalt concrete;

 "paving stones" means that it is covered by blocks well connected, and the surface is smooth;

 "sett" means that it is covered by natural stones, even with large gaps and a rougher surface than the previous one.

The tag surface corresponds to the attribute "typeSol" of the object "Circulation" in the CNIG accessibility standard.

Smoothness corresponds to the attribute "etatRevetement" of the object "Circulation" in the CNIG accessibility standard and really describes the accessibility of the sidewalks, since quantify the quality of the way. The values can be:

 "excellent": for very new asphalt surface without holes and gaps; the way is suitable even for small wheels like skateboards;

 "good": still an excellent accessibility for all the users, however, some imperfection can be present;

 "intermediate": the quality of the paved is compromised, but the presence of some holes does not compromise the usability of a wheelchair user;

 "bad": the way is not accessible to wheelchairs, due to the presence of wide or deep holes.

The longitudinal slope is another important to characterized the accessibility of sidewalks. The tagging in the OSM is possible by the keys "incline". The tag has to be inserted on the way of the sidewalks or on the nodes of the kerbs. The value is expressed as a percentage "%". it is positive or negative if the way is upward or downward respectively. The transverse inclination has also to be considered: it is almost imperceptible for ordinary people walking on the sidewalk but it can influence and create problems for wheelchairs, especially for electrics ones. It is quantified by the key "incline:across"; considering the direction of the way, it is positive for a downward slope toward the right, negative in the opposite case. The key "incline" corresponds to the attribute "pente" of the object "Troncon_Cheminement" in the CNIG accessibility standard.

IV.2.1.2. Crossing

A crossing is mapped as a separate way from the sidewalks that it connects: it can be represented with a new way with five nodes, as shown in Figure 14. This is the simplest case, but more complex cases are based on different combinations of it.

Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) Models transformation and data integration in OpenStreetMap for accessibility.

26

In the white boxes, there are the letters of the nodes and in the red/blue boxes, the numbers of the ways.

The crossing (4) shares the first node (A) with the sidewalk (1); node (B) is simply the kerb from sidewalk (1) to the street, the node (C) is the connection between the crossing and the street (2).

The node (D) is the kerb between the street and the other sidewalk (3), and finally (E) is the connection between the crossing and the sidewalk (3).

The different nodes require different tagging schema accordingly to their meaning. B and D are the nodes that represent the kerbs. Note that in OSM standards, kerbs with steps bigger than 3 cm are considered non accessible to wheelchairs and bicycles. They need the use of the key "kerb" with a value that can be:

 "raised": the step is more than 3 cm and does not guarantee accessibility;

 "lowered": the step is approximately 3 centimeters or less, and a structure (ramp) exist to ease the passage from the sidewalk to the street;

 "flush": there is not a significant step between the street and the sidewalk (Biagi, Brovelli, and Stucchi 2020).

In the CNIG standard, the OSM tag kerb is equivalent to the attribute "hauteurRessaut" of the object "Noeud". The CNIG accessibility standard takes into account only crossing for pedestrian mapped with the combination of the tags "highway = footway" and "footway = crossing" and it corresponds to the CNIG object "Traversée".

Appendix 1 shows the PAM tags which are attributes for people with visual impairments or other disabilities and their equivalents in the CNIG accessibility standard. In this case the elements of interest are the tactile paving and the sound traffic lights.

 The tactile paving is represented with the tag "tactile paving = yes": when present, it should be added on the sidewalks and on the nodes that represent the kerbs. It can take different values (yes, no, incorrect) indicating respectively the presence, absence or anomaly of the podotactile surfaces on either side of the crosswalk. This tag corresponds to the "bandeEveilVigilance" attribute of the object "Noeud" in the CNIG accessibility standard, when it indicates the presence or absence of a podotactile surface; and to the "controleBEV" attribute when the podotactile surface has an anomaly.

 For the sound traffic lights, the tag to be used is "traffic signals:sound = yes" on the way where the tag "crossing = traffic signals" is present. In some cases, the signals do not start automatically, but only by pushing a button: this situation can be mapped with the Models transformation and data integration in OpenStreetMap for accessibility.

tag "button operated = yes". The different values of the crossing tag define the characteristics of pedestrian crossings specific to blind, autistic or reduced mobility people, and correspond to different attributes of the object "Traversée" in the CNIG accessibility standard.

IV.2.1.3. Obstacles

Barriers or obstacles are mapped in OSM as single nodes. It is better to do not add this node as  Storm drain: using the tag "manhole = drain" with the possibility of adding the size of the holes, if they are larger than 2 cm: this can be tagged with the key "obstacle:

description";

Models transformation and data integration in OpenStreetMap for accessibility.

28

 Tree: described with the tag "natural = tree".

All obstacles are modeled in the CNIG accessibility standard thanks to the object "Obstacle".

Obstacles can represent a problem just for some specific type of users. This can be tagged with the key "obstacle: <type of transport>", one example can be "obstacle: wheelchair = yes" for obstacles that stop wheelchairs (Biagi, Brovelli, and Stucchi 2020).

Appendix 2 presents the different possible values (yes, no, limited or bad) of the wheelchair tag, that help to define whether a crosswalk is accessible to people in wheelchairs or not. It corresponds to the attributes "hauteurRessaut" and "abaisseTrottoir" of the object "Noeud" in the CNIG accessibility standard. For each value of the wheelchair tag, the two nodes of the crossing in the CNIG model must be taken into account.

IV.2.1.4. Parkings

A parking for cars is mapped in OSM as an area with the tag "amenity = parking". An important tag associated to it is the tag "capacity" and a particular subkey is "capacity: disabled" to specify the number of lots reserved for people with disability. Generally, this tagging schema is not sufficient to identify the reserved lots, in particular in huge parking areas. This issue can be solved inserting individually the reserved lots inside a parking area. A closed area is created and the tag "amenity = parking space" and "parking space = disabled" are associated; This corresponds to the object "Stationnement_PMR" in the CNIG model. Figure 16 shows how to map PMR parking spaces. we used this tool to study the geometry of OSM data.

V.2. Creation of the CNIG database

 The CNIG database geosm1 is created in command line in Psql with the command: create database geosm1;

 Later on, the POSTGIS extension is added for the manipulation of spatial data with the commands: \c geosm1 create extension postgis;

 The creation of tables and constraints is done on dbeaver: to do this, you have to connect to the database through the dbeaver interface and create the tables either by writing SQL queries or in graphical mode. This is how we obtain the CNIG database show in Figure 17. The purpose here is to present the algorithms for processing and transforming OpenStreetMap data in order to prepare their fusion with CNIG data.

To transform and integrate the OSM data, in particular the path sections, their nodes and their obstacles in the CNIG database, the following 03 models must be executed in order. To do this, we apply the algorithm download OSM data from a raw query. It allows to insert the Overpass query to download the areas corresponding to the footpaths ("highway"="footway") as shown in figure 21.

V.3.2.1. Model for the generation

Models transformation and data integration in OpenStreetMap for accessibility.

34 Once the pedestrian paths are downloaded, we apply the Extract vertices algorithm which takes in these paths and extracts all the path nodes.

In fact, the treatment Extract vertices takes a vector layer and generates a point layer with points representing the vertices in the input geometries. The attributes associated to each point are the same ones associated to the feature that the vertex belongs to. Additional fields are added to the vertices indicating the vertex index (beginning at 0), the feature's part and its index within the part (as well as its ring for polygons), distance along original geometry and bisector angle of vertex for original geometry. Figure 22 shows how the vertices are extracted from a line and a polygon layer.

. Models transformation and data integration in OpenStreetMap for accessibility.

 Step 4 & 5: join nodes and remove duplicates

Now we need to join the paths from the Download OSM data from a raw query algorithm and their vertices previously extracted with the Extract vertices algorithm based on their OSM id.

Then apply the Delete duplicate geometries algorithm to remove duplicates.

 Step 6: add an automatic increment field

It allows to add a new integer field to the vector layer resulting from the previous step, with a sequential value for each entity. This field will be used as a unique ID for the entities of the layer.

 Step 7: extract by attribute

Create two vector layers from an input layer: in our case the layer from the Add auto incremented field algorithm; one will contain only entities matching the selection attribute 'osm_id_count > 1' while the second will contain all non-matching entities.

 Step 8: make path sections

Once the relevant path nodes are obtained, we can now make path segments by cutting the pedestrian paths downloaded from OSM at the extracted nodes obtained in the previous step. To do this, we apply the Cut lines with points algorithm.

The Cut lines with points algorithm is a processing model that takes as input a layer of lines and a layer of points and produces as output cut lines as shown in figure 23.

Figure 23: Model cut lines with points

To be able to cut the lines, we have a QGIS treatment Cut with lines, so it is necessary to transform the layer of points into a layer of lines. Therefore, the model first transforms the layer Models transformation and data integration in OpenStreetMap for accessibility.

36 of points into small lines similar to the points by means of a QGIS geometry expression provided by the Geometry by expression algorithm as can be seen in figure 24.

Figure 24: Transforming points into lines

Now that the points have been transformed into thin lines, we can unambiguously apply the QGIS processing Cut with lines as seen in figure 25. Allows editing the structure of the attribute table of a vector layer. Fields can be modified in their type and name, using a fields mapping. The original layer is not modified. A new layer is generated, which contains a modified attribute table, according to the provided fields mapping.

Here we refactor the fields of the vector layer from the Add an auto-incremented field algorithm in order to clear all the fields to join them later with the footpath nodes downloaded from OSM.

Models transformation and data integration in OpenStreetMap for accessibility.  The Buffer algorithm creates a buffer of fixed width (50 cm) for each feature in the "troncon" layer.

 After, the Join attributes by location treatment is applied to attach the obstacles which are located at a distance of 50 cm or less from the path trunks to the created buffer.

 Now that we got relevant obstacles, we can apply the Refactor fields algorithm to add fields corresponding to the obstacles in the CNIG accessibility standard as shown in figure 32. Figure 35 illustrates the PostgreSQL running SQLNode algorithm, with the SQL query used to integrate the data from the node_tmp table into the " Noeud " table of the geosm1 database.

Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database

Models transformation and data integration in OpenStreetMap for accessibility.

V.3.3. Presentation of the results

To simulate our models, we used an area of OSM where the pedestrian paths are well documented, notably a part of the Orange territory in France. However, for the values that lacked precision in OpenStreetMap, we created a value notably "88" to stipulate that the OSM tag lacks precision.

The models generated 225 pedestrian nodes, 03 obstacles and 110 ways as you will see in figures 46

CONCLUSION AND PERSPECTIVES

The movement of people with reduced mobility or in a situation of disability is, until now, a real obstacle course. The solutions developed so far do not take into account all the territories and are proprietary. The only way to guarantee accessibility to all is to improve the level of accuracy of OpenStreetMap which is public by finding a way to merge OSM data with CNIG data that will be produced by each community in application of the LOM (Mobility Orientation Law).

In this project, we provided models for the transformation of OSM data into CNIG data. These models can help communities when collecting CNIG data, by providing them with CNIG data already represented in OpenStreetMap and are a good basis for merging OSM data with CNIG data.

However, it should be pointed out that there are areas on OpenStreetMap where pedestrian paths are not represented, so the question arises as how to make the paths in this case? One answer would be to create pedestrian paths parallel to a highway; this would be an excellent perspective to our work.

Figure 1 :

 1 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 5 :

 5 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 6 :

 6 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 7 :

 7 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 8 :

 8 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 9 :

 9 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 10 :

 10 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 12 :

 12 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 14 :

 14 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 15 :

 15 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 16 :

 16 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 17 :

 17 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 18 :

 18 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 19 :

 19 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 20 :

 20 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 21 :

 21 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 22 :

 22 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 23 :

 23 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 24 :

 24 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 25 :

 25 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 29 :

 29 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 30 :

 30 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 31 :

 31 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 32 :

 32 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 33 :

 33 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 34 :

 34 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 35 :

 35 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 36 :

 36 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 37 :

 37 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 38 :

 38 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 40 :

 40 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 41 :

 41 Figure 1 : OpenStreetMap Data Model (Mericskay 2017) .......................................................... Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021) .................................................................................................................................................... Figure 3 : Conceptual Data Model of access equipment (CNIG Accessibility Standard 2021) Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021) .................... Figure 5 : Differentiation of matching ....................................................................................... Figure 6 : Gantt diagram ............................................................................................................Figure 7 : Pert chart ...................................................................................................................Figure 8: Point ...........................................................................................................................Figure 9: Simple non-closed linestring ......................................................................................Figure 10: Polygon defined by exterior ring .............................................................................Figure 11: Multipoint with 4 parts ............................................................................................. Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements .................................. Figure 13: Multipolygon consisting of two elements defined by exterior rings and three interior rings ............................................................................................................................................ Figure 14: Simple schema of the mapping of crossings (Biagi, Brovelli, and Stucchi 2020) ...Figure 15: Example of mapping the height of a traffic sign (Biagi, Brovelli, and Stucchi 2020) ....................................................................................................................................................Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020) ........................................................................................................ Figure 17: CNIG database .........................................................................................................Figure 18: Loading OSM data from Orange .............................................................................Figure 19: Download of Orange's footways ..............................................................................Figure 20: Generation of pathway trunks ..................................................................................Figure 21: Downloading pedestrian paths on OSM ..................................................................Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.) .............................................................................Figure 23: Model cut lines with points ......................................................................................Figure 24: Transforming points into lines .................................................................................Figure 25: Cut with lines ........................................................................................................... Figure 26: Geostandardization of nodes .................................................................................... Figure 27: Selection of initial and final path nodes ................................................................... Figure 28: Joining of pedestrian paths with initial and final nodes ...........................................Figure 29: Creation of the geostandard path trunks ..................................................................Figure 30: Generate obstacles of pathways in the CNIG format ...............................................Figure 31: Downloading of obstacles in OSM ..........................................................................Figure 32: Geostandardization of obstacles ..............................................................................Figure 33: Model for integrating OSM data into the CNIG database .......................................Figure 34: Exportation of nodes into the node_tmp table .........................................................Figure 35: Insertion of nodes data into the "Noeud" table of the CNIG database ....................Figure 36: Pathway nodes represented according to the CNIG accessibility standard .............Figure 37: Attribute values of pathway nodes according to the CNIG accessibility standard ..Figure 38: Obstacles represented according to the CNIG accessibility standard ...................... Figure 39: Attribute values of obstacles according to the CNIG accessibility standard ...........Figure 40: Pathway sections represented according to the CNIG accessibility standard ..........Figure 41: Attribute values of pathway sections according to the CNIG accessibility standard ....................................................................................................................................................

Figure 2 :Figure 3 :

 23 Figure 2 : Conceptual Data Model for road accessibility (CNIG Accessibility Standard 2021)

Figure 4 :

 4 Figure 4 : Conceptual Data Model of ERP (CNIG Accessibility Standard 2021)

Figure 5 :

 5 Figure 5 : Differentiation of matching

Figure

  Figure 6 : Gantt diagram

Figure 8 :

 8 Figure 8: Point

Figure 9 :

 9 Figure 9: Simple non-closed linestring

Figure 10 :

 10 Figure 10: Polygon defined by exterior ring

Figure 11 :

 11 Figure 11: Multipoint with 4 parts

Figure 12 :Figure 13 :

 1213 Figure 12: Simple multilinestring defined by 4 endpoints of 2 elements

  part of the way of the sidewalks, but instead, a node closer to it since they are external elements and part of the sidewalks. The different types of obstacles have different tags:  Traffic signals: use the key "traffic sign" with different values according to the signal, and the tag "support = pole" to indicate the presence of the pole; The height of traffic signals or advertising panels on sidewalks are also an important element, in particular for blind people. The tagging schema in OSM starts by creating the obstacle. Height can be tagged by the combination of "support = pole" and "height = m", as shown in Figure 15. It corresponds to the attribute "hauteurObsPoseSol" of the object "Obstacle" in the CNIG model.

Figure 15 :

 15 Figure 15: Example of mapping the height of a traffic sign(Biagi, Brovelli, and Stucchi 2020)

Figure 16 :

 16 Figure 16: Example of mapping the parking spaces reserved for people with disability(Biagi, Brovelli, and Stucchi 2020)

Figure 17 :

 17 Figure 17: CNIG database

Figure 18 :

 18 Figure 18: Loading OSM data from Orange

Figure 19 :

 19 Figure 19: Download of Orange's footways

  of pedestrian paths V.3.2.1.1. Presentation of the model This model allows to obtain path sections and their start and end nodes as modeled in the CNIG accessibility standard from the raw data of OSM. Figure 20 illustrates the different stages of data transformation.Models transformation and data integration in OpenStreetMap for accessibility.

Figure 20 :

 20 Figure 20: Generation of pathway trunks

Figure 21 :

 21 Figure 21: Downloading pedestrian paths on OSM

Figure 22 :

 22 Figure 22: Vertices extracted for line and polygon layer ("Géométrie Vectorielle -Documentation QGIS Documentation" n.d.)

Figure 25 :

 25 Figure 25: Cut with lines

Figure 29 :

 29 Figure 29: Creation of the geostandard path trunks

Figure 30 :

 30 Figure 30: Generate obstacles of pathways in the CNIG format

Figure 31 :

 31 Figure 31: Downloading of obstacles in OSM

Figure 32 :

 32 Figure 32: Geostandardization of obstacles

Figure 33 :

 33 Figure 33: Model for integrating OSM data into the CNIG database

Figure 34 :

 34 Figure 34: Exportation of nodes into the node_tmp table

Figure 36 :Figure 37 :

 3637 Figure 36: Pathway nodes represented according to the CNIG accessibility standard

Figure 38 :Figure 39 :Figure 40 :Figure 41 :

 38394041 Figure 38: Obstacles represented according to the CNIG accessibility standard

.2. Literature review II.2.1. OpenStreetMap II.2.1.1. Presentation

	OpenStreetMap is a free, editable map of the whole world that is being built by volunteers largely
	from scratch and released with an open-content license. OpenStreetMap is built by contributors,
	usually called mappers within OpenStreetMap, who gather information by driving, cycling, or

2.1.2. Formalised representation (H. Pruvost and P. Mooney, 2017)

	 Way: an ordered list of nodes is called a way. A way has a maximum of 2000 nodes, to
	ensure that tools and users are not overwhelmed by huge objects that are too difficult to
	manipulate. Ways are used to represent linear objects such as paths, roads, railroad lines,
	coastlines, and boundaries.
	Polygons are not a special type of data at this time: they are simply closed ways, i.e., the
	last point is merged with the first. They are used to represent buildings, parks, and areas
	of a land use plan.
	 Relations: a relation is an ordered list of nodes, ways, and relations. Each member of a
	relation has an optional role that adds information to that sub-element. Like tags, these
	roles are stored in strings (limited to 255). Relations can represent road or bike routes,
	administrative boundaries or rivers, again depending on the tags attached to them.
	 Identifiers: an element in the OpenStreetMap database, whether it is a node, a way, or a
	relation, is identified by a unique numeric identifier. This identifier has no particular
	Figure 1 : OpenStreetMap Data Model (Mericskay 2017)
	Models transformation and data integration
	in OpenStreetMap for accessibility.

meaning; it is only used to uniquely identify an element. A relation and a way use these identifiers to reference each of its sub-elements. Two ways meet only if they reference at least one node identifier (not two nodes with identical coordinates). Similarly, a closed way representing a surface must reference the same node identifier twice.

10 II.

"

  Coverage" is the term typically applied to the legacy ARC/INFO feature data format developed by Esri. The ARC/INFO coverage data model was a revolutionary concept, by storing graphical information with arc-node topology ("ARC") with features linked to attributes stored a simple, single-user RDBMS ("INFO"). In ARC/INFO, the BUILD and CLEAN commands and overlay tools such as INTERSECT and IDENTITY construct and maintain planar arc-node topology. However, in our case, we don't use the ARC/INFO feature data format, so we will study the data coverage between OpenStreetMap and the geostandard on different criteria: OpenStreetMap has a global extent and covers all areas accessible to humans including airspace, aviation areas, borders, etc... The geostandard focuses on collecting data for the mobility of people with disabilities and on the French territory. It covers only the areas and services accessible by PRM.

Models transformation and data integration in OpenStreetMap for accessibility.

18 II.2.6.1. Territory

REFERENCES ...........................................................................................................................

APPENDIXES ............................................................................................................................ 50

Obstacle

The additional attributes and their values come from a second vector layer: those of the nodes from the Download OSM data from a raw query algorithm. A spatial criterion is applied to select the values from the second layer that are added to each feature in the first layer.