Revert changes

content/development/algorithms/trace-address-search-issues.md

@@ -3,28 +3,32 @@ title: Trace Address Search Issues
 versions: '*'
 ---
 
-## Issue: street or house is found in another city
+## Issue: street or house is found in another city 
 
-Examples on Github: [1](https://github.com/osmandapp/OsmAnd/issues/10679), [2](https://github.com/osmandapp/OsmAnd/issues/10677), [3](https://github.com/osmandapp/OsmAnd/issues/10699).
+Examples when address was find in another city: [1](https://github.com/osmandapp/OsmAnd/issues/10679), [2](https://github.com/osmandapp/OsmAnd/issues/10677), [3](https://github.com/osmandapp/OsmAnd/issues/10699), [4](https://github.com/osmandapp/OsmAnd/issues/10921).
 
-This situation is typical and associated with the processing of borders for cities. It can be seen if you search for STREET or STREET + HOUSE without a city name, then a full-text search will find a house from another city.
+These issues are related to the algorithm of connecting cities to its boundaries in OpenStreetMap. It can be seen if you search for STREET or STREET + HOUSE without a city name, then a full-text search will find a house from another city.
 
-How to OsmAnd is finding city boundaries (relation):
-- OsmAnd searches for relations where admin_center / admin_centre refers to a node with place = city, town, village, etc.
-- Otherwise, the link is checked for an exact match of the name. 
+How to OsmAnd is finding a boundary (relation) to a specific city:
+- Boundary Relation should have following tags **boundary** (*administrative*, *postal_code*) and **place**.
+  - Boundary should have a relation member **label**, **admin_centre** or **admin_center** pointing to a place-node.
+  - Boundary should have **exact same name** as place-node
+  - Otherwise boundary relation is not used as a city boundary
+- Among boundaries the biggest is selected 
 - Ways of relation are the boundaries. Inner / outer ways are supported.
 
-## Possible causes
+### Possible causes
 
 In OpenStreetMap:
 - The city's boundaries are broken. How to fix [here](https://help.openstreetmap.org/questions/1053/how-do-i-fix-inconsistent-boundaries).
 - The city has no borders ([example](https://github.com/osmandapp/OsmAnd/issues/10699)).
 - City boundaries don't overlap correctly. OsmAnd must include the street in both cities. You can fix it in OpenStreetMap.
+- No required tags for relation (**boundary** or **place**) - [4](https://github.com/osmandapp/OsmAnd/issues/10921).
 
 In OsmAnd
 - The address begins to belong to the neighboring city. These cities are often villages, suburbs, districts. Or belong to the general area. Github: [1](https://github.com/osmandapp/OsmAnd/issues/10559),[2](https://github.com/osmandapp/OsmAnd/issues/10679),[3](https://github.com/osmandapp/OsmAnd/issues/10730)
 
-## Examples
+### Examples
 
 Using only OSM: You found - Wolności 223 Zabrze
 

content/osmand/map/interact-with-map.md

@@ -9,21 +9,34 @@ Special words about my location / radius of my location. Shortly about map inter
 
 ## Gestures
 
-**_TODO: This section is incomplete_**
+* Zoom in and out map on the main screen by using two fingers.
+* There is an additional option for iOS to adjust the slope of the map. User have to put two fingers on the map and swipe down the screen to change the slope and swipe up to change to default state.
+* Clicking with two fingers on the map will zoom out the map.
+* Set from and to navigation directions in {% data variables.android-values.shared_string_menu %} → {% data variables.android-values.get_directions %}. The elevation chart will appear at the bottom of the screen. User can zoom in and zoom out the elevation chart that will change chart borders accordingly by using two fingers.
+
+There are three wake-up options that user can find in {% data variables.product.android_button_seq %} {% data variables.android-values.shared_string_menu %} → {% data variables.android-values.shared_string_settings%} → {% data variables.android-values.shared_string_profiles %} → {% data variables.android-values.general_settings_2 %} → {% data variables.android-values.shared_string_other %} → {% data variables.android-values.screen_control %} → {% data variables.android-values.turn_screen_on%}.
+
+Note: The OsmAnd should be in the foreground when the device is locked.
 
 
 ## Map orientation
-**_TODO: Same picture as in Compass widget_**
+
+![Compass widget](/assets/images/widgets/compass_widget.png)
 
 There are 3 different **Map orientation** modes which are switched by click on the [Compass widget](/osmand/widgets/map-buttons/#compass).
-- **{% data variables.android-values.rotate_map_none_opt %}** - map is not being rotated by any external movements and it could be rotated only by **2 pointer gesture** (2 double tap & rotate).
-- **{% data variables.android-values.rotate_map_bearing_opt %}** - map is being rotated by bearing, i.e. direction of your movement (GPS direction) is synchronized with the map. Map will be oriented so that head looking view will be strictly above (higher) my location icon on the map. Without movement map won't be rotated. In this mode center of the map will be located slightly below center of the device, so it allows to see more map information ahead of your movement which is usable in navigation mode. It can be disabled by setting **_TODO: add 2 paths android / ios to General Settings -> Display position always in center _**.
+- **{% data variables.android-values.rotate_map_none_opt %}** - map is not being rotated by any external movements, and it could be rotated only by **2 pointer gesture** (2 double tap & rotate).
+- **{% data variables.android-values.rotate_map_bearing_opt %}** - map is being rotated by bearing, i.e. direction of your movement (GPS direction) is synchronized with the map. The map will be oriented, so that head looking view will be strictly above (higher) my location icon on the map. Without movement the map won't be rotated. In this mode the center of the map will be located slightly below the center of the device. It allows seeing more map information ahead of your movement which is usable in navigation mode. It can be disabled by setting
+{% data variables.product.android_button_seq %} {% data variables.android-values.shared_string_menu %} → {% data variables.android-values.shared_string_settings%} → {% data variables.android-values.shared_string_profiles %} → {% data variables.android-values.general_settings_2 %} → {% data variables.android-values.always_center_position_on_map %};
+{% data variables.product.ios_button_seq %} {% data variables.ios-values.menu %} → {% data variables.ios-values.shared_string_settings %} → {% data variables.ios-values.m_style_overview %} → {% data variables.ios-values.general_settings_2 %} → {% data variables.ios-values.always_center_position_on_map %}.
 - **{% data variables.android-values.rotate_map_compass_opt %}** - map is being synchornized with device compass orientation. So, [Compass widget](/osmand/widgets/map-buttons/#compass) will point to actual Earth North if device is hold flat. In case compass sensor is not present on device, map orientation won't change.
 
 Extra compass settings (Android):
-- **_TODO: Use Kalman filter (Android)_** - smoothen rotation of the map with a slower rotation animation though it introduces a small delay (< 1 second) till  
-- **_TODO: Use Magnetic sensor_** - smoothen rotation of the map with a slower rotation animation though it introduces a small delay (< 1 second) till  
+- ** Use Kalman filter (Android)** - smoothen rotation of the map with a slower rotation animation though it introduces a small delay (< 1 second) till.  
+{% data variables.product.android_button_seq %} {% data variables.android-values.shared_string_menu %} → {% data variables.android-values.shared_string_settings%} → {% data variables.android-values.shared_string_profiles %} → {% data variables.android-values.general_settings_2 %} → {% data variables.android-values.shared_string_other %} → {% data variables.android-values.use_kalman_filter_compass %}
+- ** Use Magnetic sensor** - smoothen rotation of the map with a slower rotation animation though it introduces a small delay (< 1 second) till.
+{% data variables.product.android_button_seq %} {% data variables.android-values.shared_string_menu %} → {% data variables.android-values.shared_string_settings%} → {% data variables.android-values.shared_string_profiles %} → {% data variables.android-values.general_settings_2 %} → {% data variables.android-values.shared_string_other %} → {% data variables.android-values.use_magnetic_sensor %}
 
 **Map orientation** could also be changed in Profile settings.
 
-**_TODO: add 2 paths android / ios to General Settings -> Map Orientation _**
+{% data variables.product.android_button_seq %} {% data variables.android-values.shared_string_menu %} → {% data variables.android-values.configure_profile%} → {% data variables.android-values.general_settings_2 %}  → {% data variables.android-values.shared_string_appearance %}→ {% data variables.android-values.always_center_position_on_map %};
+{% data variables.product.ios_button_seq %} {% data variables.ios-values.menu %} → {% data variables.ios-values.shared_string_settings %} → {% data variables.ios-values.m_style_overview %} → {% data variables.ios-values.general_settings_2 %} → {% data variables.ios-values.map_settings_appearance %} → {% data variables.ios-values.always_center_position_on_map %}.