doc ref #14482

Signed-off-by: m-kro <m.barthauer@t-online.de>

docs/web/docs/Definition_of_Vehicles,_Vehicle_Types,_and_Routes.md

@@ -96,6 +96,7 @@ A vehicle may be defined using the following attributes:
 | arrivalPosLat   | float(m)/string ("default", "left", "right", "center")                                   | The lateral position on the arrival lane at which the vehicle shall arrive; see [Simulation/SublaneModel](Simulation/SublaneModel.md). by default the vehicle does not care about lateral arrival position                                               |
 | speedFactor   | float > 0                                   | Sets custom speedFactor (factor on road speed limit) and overrides the [speedFactor distribution](#speed_distributions) of the vehicle type                                               |
 | insertionChecks  | string list  |  Sets the list of safety checks to perform during vehicle insertion. Possible values are: `all`, `none`, `collision`, `leaderGap`, `followerGap`, `junction`, `stop`, `arrivalSpeed`, `oncomingTrain`, `speedLimit`, `pedestrians`. default *all* |
+| parkingBadges | string list | list of keywords to access restricted parking areas (the default empty list will still allow access to unrestricted parking areas) |
 
 !!! caution
     Any vehicle types or routes referenced by the attributes **type** or **route** must be defined **before** they are used. [Loading order is described here.](sumo.md#loading_order_of_input_files)
@@ -502,6 +503,7 @@ startupDelay        | float >= 0        | 0                | The extra delay tim
 | timeToTeleport       | float   |        | Override option **--time-to-teleport** for vehicles of this type |
 | timeToTeleportBidi   | float   |        | Override option **--time-to-teleport.bidi** for vehicles of this type |
 | speedFactorPremature | float   |        | When set to a positive value, this may cause a train to slow down on approach to a stop whenever the stop has its `arrival` attribut set and the vehicle would otherwise be ahead of schedule. The given value is multiplied with the edge speed limit and used as a lower bound for slowing down. If option **--use-stop-started** is set and the stop defines the `started` attribute, this is used instead of `arrival`. |
+| parkingBadges | string list | \- | list of keywords to access restricted parking areas (the default empty list will still allow access to unrestricted parking areas) |
 
 Besides values which describe the vehicle's car-following properties,
 one can find definitions of the assigned vehicles' shapes, emissions,
@@ -1071,7 +1073,7 @@ following:
 
 ### Using existing types
 
-Multiple distributions can make use of the same types and optionally override their probabilites. 
+Multiple distributions can make use of the same types and optionally override their probabilites.
 Previously defined vehicle type distributions can be referenced as well.
 
 ```xml

docs/web/docs/Simulation/ParkingArea.md

@@ -58,7 +58,8 @@ The parkingArea supports the following attributes:
 | width            | float          | positive                                                                                     | 3.2                                    | The width of the road-side parking spaces                                                                                  |
 | length           | float          | positive                                                                                     | (endPos - startPos) / roadsideCapacity | The length of the road-side parking spaces                                                                                 |
 | angle            | float (degree) |                                                                                              | 0                                      | The angle of the road-side parking spaces relative to the lane angle, positive means clockwise                             |
-| lefthand            | bool |     | *false*    | Whether road-side parking spaces should be drawn on the left side of the lane   |
+| lefthand         | bool           |     | *false*    | Whether road-side parking spaces should be drawn on the left side of the lane   |
+| acceptedBadges   | string list |     |  | The set of keywords which give access to the parking area (an empty value means free access to all) |
 
 ## Custom parking spaces
 
@@ -118,6 +119,18 @@ wait on the road until a space becomes available or [reroute to a new
 parking
 area](../Simulation/Rerouter.md#rerouting_to_an_alternative_parking_area).
 
+# Restricting the access to the parking area
+
+In the real world, the access to parkings may be restricted to different kinds of users, such as residents, customers or employees. As these access rights may vary a lot depending on the location,
+they are modeled using a separate permission system from the vehicle classes. The access to the parking area can be restricted in the following way:
+
+- The parking area defines a set of accepted badges (keywords) which model single access rights in the attribute **acceptedBadges**, e.g. `acceptedBadges="clients_supermarket employees_supermarket"`
+- The vehicles or vehicle types define the set of owned badges which give them access, e.g. `parkingBadges="employees_supermarket home_johndoe"`
+- Any parking area which is not restricted (empty *acceptedBadges** attribute) or where at least one of the accepted badges is present in the vehicle or vehicle type definition can be accessed
+
+!!! caution
+    Parking badges defined in the vehicle definition override vehicle type settings.
+
 # Importing / Generating Parking Areas
 
 The following tools exist to obtain parking area definitions