[QGIS Commit] r12138 - docs/trunk/english_us/user_guide

[svn_qgis at osgeo.org]

Author: dassau
Date: 2009-11-16 05:10:39 -0500 (Mon, 16 Nov 2009)
New Revision: 12138

Modified:
   docs/trunk/english_us/user_guide/plugins_openstreetmap.tex
Log:
finished revision 


Modified: docs/trunk/english_us/user_guide/plugins_openstreetmap.tex
===================================================================
--- docs/trunk/english_us/user_guide/plugins_openstreetmap.tex	2009-11-16 07:59:57 UTC (rev 12137)
+++ docs/trunk/english_us/user_guide/plugins_openstreetmap.tex	2009-11-16 10:10:39 UTC (rev 12138)
@@ -23,7 +23,7 @@
 The following subsection gives a brief introduction to principles of the OSM 
 project. If you are not interested in information on OSM just skip the next 
 section. Parts of the following paragraphs are copied from the 
-OpenStreetMap web site.
+OpenStreetMap web site at \url{http://www.openstreetmap.org}.
 
 \minisec{The OpenStreetMap project}
 
@@ -48,13 +48,13 @@
 logs and edit the vector data using the given editing tools.
 
 OSM data primitive is an object class that can be stored via the API in the
-server. Three supported types of data are: \textbf{Node}, \textbf{Way} and 
-\textbf{Relation}. 
+server. The three supported types of data are: \textbf{Node}, \textbf{Way} 
+and \textbf{Relation}. 
 
 \begin{itemize}
 \item \textbf{A node} is a latitude/longitude pair of coordinates. It is 
-used as building a block for other features and a feature itself (Points Of 
-Interest) if they are tagged as required. 
+used as building a block for other features and as a feature itself (Points 
+Of Interest), if they are tagged as required. 
 \item \textbf{A way} is a list of at least two nodes that describe a linear
 feature such as a street, or similar. Nodes can be members of multiple ways.
 \item \textbf{A relation} is a group of zero or more primitives with 
@@ -68,57 +68,53 @@
 based of a key and a value. OSM is usually distibuted in XML format. XML 
 payload is used for the communication with the OSM server as well.
 
-For more information visit the project website at:
-\url{http://www.openstreetmap.org}.
-
 \minisec{QGIS - OSM Connection}\label{qgis-osm-connection}
 
-The first part of this subsection describes the way how OSM data primitives 
-are displayed in QGIS vector layers.
+The first part of this subsection describes how OSM data primitives 
+are displayed in QGIS vector layers. As written above, OSM data consist of 
+Nodes, Ways and Relations. In QGIS they are displayed in three diffrent 
+layer types: Point layer, Line layer and Polygon layer. It's not possible 
+to remove any of these layers and work with the other ones.
 
-As written above, OSM data consist of Nodes, Ways and Relations. In QGIS they 
-are displayed in three diffrent layer types: Point layer, Line layer and 
-Polygon layer. It's not possible to remove any of these layers and work with 
-the other ones.
-
 \begin{itemize}
-\item \textbf{Point layer} displays all features of type Node that stands 
+\item A \textbf{Point layer} displays all features of type Node that stands 
 alone. That means that only Nodes that are not included in any Way belongs 
 to the Point layer.
-\item \textbf{Line layer} displays those OSM features of type Way that are 
-not closed. That means that none of these Ways starts and ends with the 
+\item A \textbf{Line layer} displays those OSM features of type Way that are 
+not closed. That means, none of these Ways starts and ends with the 
 same Node.
-\item \textbf{Polygon layer} displayes all Ways that are not included in 
+\item A \textbf{Polygon layer} displays all Ways that are not included in 
 Line layer.
 \end{itemize}
 
 OpenStreetMap has one more data primitive except for the three mentioned
-above - Relation. In our design there is purposely no vector layer to display
-Relations. Relation defines relation between any number of data primitives.
-After Point, Line or Polygon is identified on map, plugin shows a list of all
-relations the identified feature is part of.
+above. This is called \textbf{Relation}. There is purposely no vector layer 
+to display Relations. A Relation defines relation between any number of 
+data primitives. After Point, Line or Polygon is identified on a map, 
+the plugin shows a list of all relations, the identified feature is part of.
 
-Challenging was designing the interconnection between OSM data and the 
+Challenging was to design the connection between OSM data and the 
 standard QGIS editing tools. These tools are made to edit a single vector 
-layer at a time, no matter of what feature types it displays. It means 
+layer at a time, no matter of what feature types it displays. This means 
 that if OSM data are loaded to QGIS through the plugin, you could 
 (theoretically) edit Point layer, Line layer or Polygon layer with these 
 standard tools separately.
 
-The problem is that Line layer consists of two different types of OSM
-features - Ways and Nodes. Why? Because in OSM format a \texttt{Way} is 
-composed of Nodes. If you start editing a Line layer and change the 
-shape of some line, your action must affect not only the OSM Way but 
-also the OSM Nodes that are part of it. \\
-QGIS standard editing tools cannot tell the OSM Provider which members
+The problem is, that Line layer consists of two different types of OSM
+features - Ways and Nodes. Why? Because in OSM format a Way is composed of 
+Nodes. If you start editing a Line layer and change the shape of some line, 
+your action must affect not only the OSM Way but also the OSM Nodes that 
+are part of it.
+
+QGIS standard editing tools cannot tell the OSM provider, which members
 of which line has changed and how. It can tell only what's the new geometry
-of which line, and that's not enough to propagate changes to OSM database
-correctly. The Line layer does also not know identifiers of line members.
-The same problem occurs when you try to edit the Polygon layer.
+of which line, and that's not enough to propagate changes to the OSM database
+correctly. The Line layer does also not know the identifiers of the line 
+members. The same problem occurs when you try to edit the Polygon layer.
 
-For this reason, the OSM plugin need its own simple tools for editing 
-OSM data. While they are used, the OSM layers can be changed correctly. 
-The Plugin editing set consists of tools for Point, Line, Polygon and 
+For this reason, the OSM plugin need its own tools for editing OSM data. 
+While they are used, the OSM layers can be changed correctly. The Plugin 
+editing tools consists of tools for Point, Line, Polygon and 
 Relation creation, deletion and moving.
 
 \textbf{Note:} To create a connection between the OSM plugin and standard 
@@ -126,9 +122,9 @@
 
 \subsubsection{Installation}
 
-The OpenStreetMap plugin is a core plugin inside the QGIS environment. If 
-you have python support enabled, the 'OpenStreetMap' plugin can be selected 
-in the Plugin Manager as described in section \ref{sec:load_core_plugin}). 
+The OpenStreetMap plugin is a core plugin inside QGIS. If you have python 
+support enabled, the 'OpenStreetMap' plugin can be selected in the Plugin 
+Manager as described in section \ref{sec:load_core_plugin}). 
 
 \subsubsection{Basic user interface}
 
@@ -146,19 +142,19 @@
 
 \minisec{OSM Features widget}
 
-This widget helps to identify OSM features. It
-shows basic information on features type and identifier as well as info on
-who and when changed feature lately. OSM Feature widget holds all editing
-tools also (in the top part of it). More information on those tools can be
-found in section focused on editing. Widget is initially disabled. It
-activates itself after successfull loading of some OSM data.
+The OSM Feature widget helps to identify OSM features. It
+shows basic information on feature type and identifier as well as info on
+who has when changed a feature. The OSM Feature widget also provides all 
+editing tools (in the top part of it). More information on those tools can be
+found in the sections below. The widget is initially disabled. It
+activates itself after successfull loading some OSM data.
 
 \minisec{OSM Undo/Redo widget}
 
-This widget is used to undo and redo edit actions. It consists not only 
-of clasical Undo button and Redo button, it shows a list with brief 
-description of edit actions that were done. The OSM Undo/Redo widget
-is initially closed. You can show it using special button on OSM Feature
+This Undo/Redo widget is used to undo and redo edit actions. It consists 
+not only of a classical Undo and Redo button, it also shows a list with a 
+brief description of the edit actions that were done. The OSM Undo/Redo 
+widget is initially closed. You can show it using a button on OSM Feature
 widget.
 
 \minisec{Toolbar menu icons}
@@ -181,15 +177,17 @@
 \end{description}
 
 More detailed information on all the widgets, buttons and dialogs can be
-found in appropriate sections of this Guide according to their functionality
-(editing, identification, etc.).
+found in appropriate sections of this plugin section according to their 
+functionality (editing, identification, etc.).
 
 \subsubsection{Loading OSM data}
 
-The first action that should be done after starting OSM Plugin is opening
-data from OSM file, import them from the shapefile or downloading data from
-OpenStreetMap server. Here we are focusing on the first mentioned action.
-To load data from file use the \toolbtntwo{osm_load}{Load OSM from file} 
+The first action that should be done after starting the OSM Plugin is 
+opening data from an OSM file. OSM data can be import as shapefile or 
+downloaded directly from the OpenStreetMap server. Here we are focusing 
+on the first mentioned method.
+
+To load data from a file use the \toolbtntwo{osm_load}{Load OSM from file} 
 icon. If there is no such button, maybe someone disabled OpenStreetMap 
 toolbar in your QGIS instalation. You can enable it again selecting
 \mainmenuopt{Settings} > \mainmenuopt{Toolbars} > \dropmenuopt{OpenStreetMap}.
@@ -206,49 +204,49 @@
 \begin{description}
 \item \textbf{OpenStreetMap file to load}: Click on the button to select 
 the .osm file you want to load data from.
-\item \textbf{Add columns for tags}: This option determines 
-inter connection between OSM and QGIS data. Each feature of OSM data has 
+\item \textbf{Add columns for tags}: This option determines a connection 
+between OSM and QGIS data. Each feature of OSM data has 
 some tags (pairs of key and value), that define the feature properties. 
 Each feature of a QGIS vector layer also has its attributes (key and value). 
 With this option you can define which properties of OSM objects should 
-be visible when displaying detailed info about QGIS features.
+be visible when displaying detailed information about QGIS features.
 \item \textbf{Replace current data}: Checking this option means that 
-new data should replace current data user is working with. Layers of 
+new data should replace current data the user is working with. Layers of 
 current data will be removed and new ones will be loaded. When loading 
-first OSM data, this option is not active, because there is nothing 
-to replace.
-\item \textbf{Use custom renderer}: This option determines how rich will 
-be the map in detail. The are three pre-defined OSM styles for map 
-displaying. Use 'Small scale' if you want to view OSM data at low level, 
+OSM data for the first time, this option is not active, because there is 
+nothing to replace.
+\item \textbf{Use custom renderer}: This option determines how many details 
+of the map will be used. There are three pre-defined OSM styles for map 
+displaying. Use \button{Small scale} if you want to view OSM data at low level, 
 to see all details and to edit something. If not you can use 
-'Medium scale' or 'Large scale'. At present days QGIS doesn't support 
-changing renderer style dynamically.
+\button{Medium scale} or \button{Large scale}. QGIS \CURRENT doesn't 
+support changing the renderer style dynamically.
 \end{description}
 
 Click \button{Ok} to load your data. If this is the first time OSM 
-file is loaded, plugin must first parse it into database.
-This may take few seconds or minutes - it depends on amount of loaded data.
+file is loaded, the plugin must first parse the database. This may take few 
+seconds or minutes - it depends on the amount of loaded data.
 
 \subsubsection{Viewing OSM data}
 
-After OSM data were loaded you can identify map features using the
+After OSM data are loaded, you can identify map features using the
 appropriate tool. Use the \toolbtntwo{osm_identify}{Identify feature} 
 button on the top-left of OSM Feature widget. Using this tool you can 
-easily explore map objects. When the mouse cursor is over an object, 
-you can see all information on it directly in the OSM Feature widget. 
+easily explore all map objects. When the mouse cursor is placed over an 
+object, you can see all information on it directly in the OSM Feature widget. 
 There is also a dynamic rubberband displayed on the map so that the user 
 is able to determine which feature is currently identified.
 
-The Properties table of the widget contains of all feature tags. Clicking on 
-the \tab{Relation tab} shows you list of all relations connected with
-identified feature.
+The \tab{Properties} tab of the widget contains of all feature tags. 
+Clicking on the \tab{Relation} tab shows you a list of all relations 
+connected with identified feature.
 
 If you want to hold a feature for a while to be able to read its properties 
 and relations, move the mouse cursor at the same time, try left-clicking 
-while you are over it. Identification process will stop until next 
+while you are over the feature. Identification process will stop until next 
 left-clicking.
 
-Sometimes there are more than one feature at the point where left-clicking
+Sometimes there are more than one feature at a point where left-clicking
 was performed. This happens especially when clicking on cross-roads or if 
 you didn't zoom enough into the map. In this situation only one of such 
 features is identified (and marked with the rubberband) but the plugin 
@@ -258,20 +256,20 @@
 \subsubsection{Editing basic OSM data}
 
 In the title of this section 'basic data' means non-relation OSM features -
-nodes and ways. If you prefer reading information on relations editing just
+nodes and ways. If you prefer reading information on relation editing, just
 skip this section and read the next one.
  
-Basic data editing is key part of OSM Plugin. You can change property,
-position or shape of any existing basic feature, you can remove features or
-add some new ones. All such changes on nodes and ways are remembered - both
-for comfortable usage of Undo/Redo operations and for easy upload of  changes
+Basic data editing is a key part of OSM Plugin. You can change property,
+position or shape of any existing basic feature. You can remove features or
+add new ones. All such changes on nodes and ways are remembered for 
+comfortable usage of Undo/Redo operations and for easy upload of all changes
 to OpenStreetMap server.
 
 \minisec{Changing feature tags}
 
-Changing property/tag of OSM feature can be done directly in table of feature
-tags. Tags table of basic feature can be found on OSM Feature widget. Don't
-forget to identify feature first.
+Changing the property/tag of an OSM feature can be done directly in 
+the table of feature tags. The Tags table of basic features can be found 
+on the OSM Feature widget. Don't forget to identify feature first.
 
 \begin{figure}[ht]
    \begin{center}
@@ -280,25 +278,26 @@
 \end{center}
 \end{figure}
 
-If you want to change tag value, just double-click in the appropriate row of
-column Value and type or select new value. If you want to remove tag click in
-its row, then use button on the right under the table - "Remove selected
-tags"
+If you want to change a tag value, just double-click in the appropriate row of
+column 'Value' and type or select a new value. If you want to remove a tag, 
+click in its row, then use button \button{Remove selected tags} on the right 
+bottom under the table.
 
-To add new tag just type its key and value into the last row of the table -
-where '<next tag value>' is written. Notice that you cannot change key of
-existing tag pair. For comfortable usage there are some combo boxes of all
+To add new tags just type its key and value into the last row of the table -
+where '<next tag value>' is written. Notice that you cannot change the key of 
+an existing tag pair. For comfortable usage, there are some combo boxes of all
 existing tag keys and their typical values.
 
-\minisec{Point creation}
+\minisec{Point creation,}
 
 For point creation there is a \toolbtntwo{osm_createPoint}{Create point} 
-button on OSM Feature widget. To create some points just click on the 
+button on the OSM Feature widget. To create some points just click on the 
 button and start clicking on the map. If your cursor is over some map 
 feature, the feature is marked/identified immediately. If you click on 
-the map when line/polygon is marked, new point is created directly on 
-such line/polygon - as its new member. If your cursor is over an existing 
-point, new point cannot be created. In such case OSM plugin will tell you:
+the map when a line or polygon is marked, a new point is created directly on 
+such line or polygon - as its new member. If your cursor is over an existing 
+point, new point cannot be created. In such case the OSM plugin will show
+following message:
 
 \begin{figure}[ht]
    \begin{center}
@@ -307,139 +306,145 @@
 \end{center}
 \end{figure}
 
-The mechanism of helping user to hit the line or polygon is called snapping
-and is enabled by default. If you want to create point very close to some
-line (but not on it) you must disable snapping by holding Ctrl key first.
+The mechanism of helping a user to hit the line or polygon is called snapping
+and is enabled by default. If you want to create a point very close to some
+line (but not on it) you must disable snapping by holding the
+\keystroke{Ctrl} key first.
 
 \minisec{Line creation}
 
-For line creation there is \toolbtntwo{osm_createLine}{Create line} button 
-on OSM Feature widget. To create a line just click the button and start 
-left-clicking on the map. Each your left-click is remembered as member 
-vertex of new line. Line creation ends when first right-click is performed. 
-New line will immediately appear on the map.
+For line creation there is a \toolbtntwo{osm_createLine}{Create line} button 
+on the OSM Feature widget. To create a line just click the button and start 
+left-clicking on the map. Each of your left-clicks is remembered as a member 
+vertex of the new line. Line creation ends when first right-click is performed. 
+The new line will immediately appear on the map.
 
-A Line with less than two members cannot be created. In such case the 
-operation is ignored.
+\textbf{Note}: A Line with less than two members cannot be created. In 
+such case the operation is ignored.
 
-Snapping is performed to all map vertexes - points from Point vector layer
-and all Line and Polygon members. Snapping can be disabled by holding 
+Snapping is performed to all map vertices - points from Point vector layer
+and all Line and Polygon members. Snapping can be disabled by holding the 
 \keystroke{Ctrl} key.
 
 \minisec{Polygon creation}
 
-For polygon creation there is \toolbtntwo{osm_createPolygon}{Create polygon} 
-button on OSM Feature widget. To create a polygon just click the button 
-and start left-clicking on the map. Each your left-click is remembered as 
-member vertex of new polygon. Polygon creation ends when first right-click 
-is performed. New polygon will immediately appear on the map.
+For polygon creation there is a \toolbtntwo{osm_createPolygon}{Create polygon} 
+button on the OSM Feature widget. To create a polygon just click the button 
+and start left-clicking on the map. Each of your left-clicks is remembered as 
+a member vertex of the new polygon. The Polygon creation ends when first 
+right-click is performed. The new polygon will immediately appear on the map.
 Polygon with less than three members cannot be created. In such case
 operation is ignored. Snapping is performed to all map vertexes - points 
 (from Point vector layer) and all Line and Polygon members. Snapping can be 
-disabled by holding \keystroke{Ctrl} key.
+disabled by holding the \keystroke{Ctrl} key.
 
 \minisec{Map feature moving}
 
-If you want to move a feature (no matter what's its type) please use the
-\toolbtntwo{osm_move}{Move feature} button from OSM Feature widget menu. 
+If you want to move a feature (no matter what type) please use the
+\toolbtntwo{osm_move}{Move feature} button from the OSM Feature widget menu. 
 Then you can browse the map (features are identified dynamically when you 
-go over them) and click on the feature you want to move. If wrong feature is
-selected after your click, don't move from the place. Repeat right-clicking
-till the right feature is identified. When selection is done and you move
-cursor you are no more able to change your decision what to move.
-To confirm moving click with left mouse button. To cancel moving click 
-with another one.
+go over them) and click on the feature you want to move. If a wrong feature is
+selected after your click, don't move it from the place. Repeat right-clicking
+until the correct feature is identified. When selection is done and you move
+the cursor, you are no more able to change your decision what to move.
+To confirm the move, click on the left mouse button. To cancel a move, click 
+another mouse button.
 
-If you are moving a feature that is connected to other features, these
+If you are moving a feature that is connected to another features, these
 connections won't be damaged. Other features will just adapt themselves to
-new position of moved feature.
+a new position of a moved feature. 
 
-Snapping is supported in this operation.
+Snapping is also supported in this operation, this means: 
 
-When moving a standalone (not part of any line/polygon) point, snapping to
-all map segments and vertexes is performed.
+\begin{itemize}
+\item When moving a standalone (not part of any line/polygon) point, 
+snapping to all map segments and vertices is performed.
+\item When moving a point that is a member of some lines/polygons, 
+snapping to all map segments and vertices is performed, except for 
+vertices of point parents.
+\item When moving a line/polygon, snapping to all map vertices is performed. 
+Note that the OSM Plugin tries to snap only to the 3 closest-to-cursor 
+vertices of a moved line/polygon, otherwise the operation would by very slow.
+Snapping can be disabled by holding \keystroke{Ctrl} key during the operation.
+\end{itemize}
 
-When moving a point that is member of some lines/polygons, snapping to all
-map segments and vertexes is performed, except for vertexes of point parents.
+\minisec{Map feature removing}
 
-When moving a line/polygon, snapping to all map vertexes is performed. Note
-that OSM Plugin tries to snap only 3 closest-to-cursor vertexes of moved
-line/polygon, otherwise operation would by very slow.
-Snapping can be disabled by holding Ctrl key during the operation.
+If you want to remove a feature, you must identify it first. To remove 
+an identified feature, use the \toolbtntwo{osm_removeFeat}{Remove this 
+feature} button on the OSM Feature widget. When removing a line/polygon, 
+the line/polygon itself is deleted, so are all its member points that 
+doesn't belong to any other line/polygon. 
 
-\minisec{Map feature removing}
+When removing a point that is member of some lines/polygons, the point is 
+deleted and the geometries of parent lines/polygons are changed. The new 
+parent geometry has less vertices than the old one.
 
-If you want to remove feature, you must identify it first. To remove 
-identified feature use \toolbtntwo{osm_removeFeat}{Remove this feature} button 
-on the OSM Feature widget. When removing a line/polygon, the line/polygon 
-itself is deleted, so are all its member points that doesn't belong to any 
-other line/polygon. When removing a point that is member of some 
-lines/polygons, point is deleted and geometries of parent lines/polygons 
-are changed. New parent geometries has less vertexes than the old ones.
+If the parent feature was a polygon with three vertexes, its new geometry 
+has only two vertexes. And because there cannot exist polygon with only two 
+vertices, as described above, the feature type is automatically changed to 
+Line.
 
-If parent was a polygon with three vertexes, its new geometry has only two
-vertexes. And because there cannot exist polygon with only two vertexes,
-feature type is automatically changed to Line.
+If the parent feature was a line with two vertexes, its new geometry has 
+only one vertex. And because there cannot exist a line with only one vertex, 
+the feature type is automatically changed to Point.
 
-If parent was a line with two vertexes, its new geometry has only one vertex.
-And because there cannot exist line with only one vertex, feature type is
-automatically changed to Point.
-
 \subsubsection{Editing relations}\label{editing_osm_relation}
 
 Thanks to existency of OSM relations we can join OSM features into groups and
 give them common properties - in such way we can model any possible map
-object: borders of a region (as group of ways and points), road of a bus,
-etc. Each member of relation has its specific role.
-There is a pretty good support for OSM Relations in our plugin.
-Let's see how to examine, create, update or remove them.
+object: borders of a region (as group of ways and points), roads of a bus,
+etc. Each member of a relation has its specific role. There is a pretty good 
+support for OSM Relations in our plugin. Let's see how to examine, create, 
+update or remove them.
 
-\minisec{Examining relation}
+\minisec{Examining relation}\label{examrelation}
 
 If you want to see relation properties, first identify one of its members.
-After that open tab "Relations" on OSM Feature widget. At the top of the tab
-you can see a list of all relations the identified feature is part of. Please
-choose the one you want to examine and look at information thereunder.
-In the first table called "Relation tags" there are properties of selected
-relation.
-In table called "Relation members" you can see brief info on relation
-members.
-If you click on a member, plugin will make a rubberband on it in map.
+After that open the \tab{Relations} tab on the OSM Feature widget. At the 
+top of the tab you can see a list of all relations the identified feature 
+is part of. Please choose the one you want to examine and look at its 
+information below. In the first table called 'Relation tags' you find the 
+properties of the selected relation. In the table called 'Relation members' 
+you see brief information on the relation members. If you click on a member, 
+the plugin will make a rubberband on it in the map.
 
 \minisec{Relation creation}
 
-There are 2 ways of creating a relation. 
+There are 2 ways to create a relation: 
 
-\begin{itemize}
+\begin{enumerate}
 \item You can use the \toolbtntwo{osm_createRelation}{Create relation} 
 button on OSM Feature widget.
-\item You can create it from the Relation tab of OSM Feature widget by 
+\item You can create it from the \tab{Relation} tab of OSM Feature widget 
 using the \toolbtntwo{osm_addRelation}{Add relation} button.   
-\end{itemize}
+\end{enumerate}
 
-In both cases dialog will appear. In second case feature that is currently
-identified is automatically considered to be the first relation member, so
-dialog is pre-filled a little. When creating relation please select its 
-type first. You can select one of predefined relation types or write your 
-own type. After that fill relation tags and choose its members.
+In both cases a dialog will appear. For the second case, the feature that 
+is currently identified is automatically considered to be the first 
+relation member, so the dialog is prefilled a little. When creating 
+a relation, please select its type first. You can select one of 
+predefined relation types or write your own type. After that fill the 
+relation tags and choose its members.
 
-If you have relation type already selected try using the 
-\toolbtntwo{osm_generateTags}{Generate tags} button. It will 
-generate typical tags to your relation type. Then you are expected to 
-enter values to the keys. Choosing relation members can 
-be done either simply by writting member identifiers, types and roles or 
-by using the \toolbtntwo{osm_identify}{identify} tool and clicking on map.
-Finally when type, tags and members are chosen dialog can be submitted - in
-such case plugin creates new relation for you.
+If you have already selected a relation type, try using the 
+\toolbtntwo{osm_generateTags}{Generate tags} button. It will generate typical 
+tags to your relation type. Then you are expected to enter values to the 
+keys. Choosing relation members can be done either by writing member 
+identifiers, types and roles or using the \toolbtntwo{osm_identify}{identify} 
+tool and clicking on map.
 
+Finally when type, tags and members are chosen, the dialog can be submitted.
+In such case the plugin creates a new relation for you.
+
 \minisec{Changing relation}
 
 If you want to change an existing relation, identify it first (follow steps
-written above in Examining relation). After that click on the 
-\toolbtntwo{osm_editRelation}{Edit relation} button, you will find it 
-on OSM Feature widget. A new dialog appears, nearly the same as for the 
-Create relation action. The dialog is pre-filled with information on 
-given relation. You can change relation tags, members or even its type. 
+written above in Section 'Examining relation'). After that click on the 
+\toolbtntwo{osm_editRelation}{Edit relation} button. You will find it 
+on the OSM Feature widget. A new dialog appears, nearly the same as for the 
+'create relation' action. The dialog is pre-filled with information on 
+given relations. You can change relation tags, members or even its type. 
 After submiting the dialog your changes will be commited.
 
 \subsubsection{Downloading OSM data}  
@@ -449,7 +454,7 @@
 such button, the OSM toolbar may be disabled in your QGIS instalation.
 You can enable it again at \mainmenuopt{Settings} > 
 \mainmenuopt{Toolbars} > \dropmenuopt{OpenStreetMap}. After clicking the 
-button a dialog occurs:
+button a dialog occurs and provides following functionalities:
 
 \begin{figure}[ht]
    \begin{center}
@@ -459,53 +464,54 @@
 \end{figure}
 
 \begin{description}
-\item \textbf{Extent}: Specifies area to download data from - intervals 
+\item \textbf{Extent}: Specifies an area to download data from intervals 
 of latitude and longitude degrees. Because there is some restriction of 
 OpenStreetMap server on how much data can be downloaded, the intervals 
-mustn't be too wide. More detailed info on extent specification can is 
+must not be too wide. More detailed info on extent specification can is 
 shown after clicking the \toolbtntwo{osm_questionMark}{help} button on 
 the right.
-\item \textbf{Download to}: Here you are expected to write path to the file 
-where data will be stored. If you can't remember structure of your disk, 
-don't panic. The browse button will help you.
-\item \textbf{Open data automatically after download}: Determines if 
-download process should be followed by loading data process or not. If you 
+\item \textbf{Download to}: Here you are expected to write a path to the 
+file where data will be stored. If you can't remember the structure of 
+your disk, don't panic. The \button{browse} button will help you.
+\item \textbf{Open data automatically after download}: Determines, if the 
+download process should be followed by loading the data process or not. If you 
 prefer not to load data now, you can do it later by using 
 the \toolbtntwo{osm_load}{Load OSM from file} button.
-\item \textbf{Replace current data}: This option is active only if the 
-'Open data automatically after download' is checked. Checking this option 
-means that downloaded data should replace
-current data we are working with now. Layers of current data will be removed
-and new ones will be loaded. When starting QGIS and downloading first data
-this option is initially inactive, because there is nothing to replace.
+\item \textbf{Replace current data}: This option is active only if 
+\radiobuttonon{Open data automatically after download} is checked. 
+Checking this option means that downloaded data should replace
+current data we are working with now. Layers of the current data will be 
+removed and new ones will be loaded. When starting QGIS and downloading 
+OSM data for the first time, this option is initially inactive, because 
+there is nothing to replace.
 \item \textbf{Use custom renderer}: This option is active only if the 
-'Open data automatically after download' checkbox is checked. It determines 
-how rich will be the map in detail. The
-are three predefined OSM styles for map displaying. Use 'Small scale' if you
-want to view OSM data at low level, to see all details and to edit something.
-If not you can use 'Medium scale' or 'Large scale'. At present days QGIS
-doesn't support changing renderer style dynamically.
+\radiobuttonon{Open data automatically after download} checkbox is checked. 
+It determines how many details will be in the map. There are three predefined 
+OSM styles for map displaying. Use \button{Small scale} if you want to view 
+OSM data at low level, to see all details and to edit something. If not you 
+can use \button{Medium scale} or \button{Large scale}. QGIS \CURRENT does 
+not support changing the renderer style dynamically.
 \end{description}
 
 Click the \button{Download} button to start the download process.
 
 A progress dialog will continuously inform you about how much of data is
-already downloaded. When an error occure during download process dialog tell
-you its details. When action finishes succesfully both the progress dialog
+already downloaded. When an error occures during the download process, a 
+dialog tells you why. When action finishes succesfully both the progress dialog
 and download dialog will close themselves.
 
 \subsubsection{Uploading OSM data}  
 
-Note that upload is always done on current OSM data. Before opening OSM
-Upload dialog, please be sure that you really have the right active layer ~
-OSM data.
+Note that the upload is always done on current OSM data. Before opening the 
+OSM Upload dialog, please be sure that you really have the right active 
+layer ~ OSM data.
 
-To upload current data to OSM server click on the 
+To upload current data to the OSM server click on the 
 \toolbtntwo{osm_upload}{Upload OSM data} button. If there is no such button, 
-OSM toolbar in your QuantumGIS instalation is disabled. You can enable it 
-again at \mainmenuopt{Settings} > \mainmenuopt{Toolbars} > 
-\dropmenuopt{OpenStreetMap}. After clicking on upload button a new dialog 
-will appear.
+OSM toolbar in your QGIS installation is disabled. You can enable it 
+again in \mainmenuopt{Settings} > \mainmenuopt{Toolbars} > 
+\dropmenuopt{OpenStreetMap}. After clicking the \button{upload} button a 
+new dialog will appear.
 
 \begin{figure}[ht]
    \begin{center}
@@ -514,25 +520,26 @@
 \end{center}
 \end{figure}
 
-At the top of dialog you can check if you are uploading correct data. There
-is a short name of current database. In the table there is information on how
-many changes will be uploaded. Statistics are displayed separately for each
-feature type.
-In 'Comment on your changes' box you can write brief information on meaning
-of your upload operation. Just write in brief what data changes you've done
-or let the box empty.
-Fill 'OSM account' arrays so that server could authenticate you. If you don't
-have account on OSM server, it's the best time to create one. Please visit
-www.openstreetmap.org.
-Use Upload to start an upload operation.
+At the top of the dialog you can check, if you are uploading the correct data. 
+There is a short name of a current database. In the table you find information 
+on how many changes will be uploaded. Statistics are displayed separately 
+for each feature type.
 
+In the 'Comment on your changes' box you can write brief information on 
+meaning of your upload operation. Just write in brief what data changes 
+you've done or let the box empty.
+Fill 'OSM account' arrays so that the server could authenticate you. If 
+you don't have an account on the OSM server, it's the best time to create 
+one at \url{http://www.openstreetmap.org}. Finally use \button{Upload} to 
+start an upload operation.
+
 \subsubsection{Saving OSM data}  
 
-To save data from current map extent to XML file click on 
+To save data from a current map extent to an XML file click on the
 \toolbtntwo{osm_save}{Save OSM to file} button. If there is no such button, 
-OSM toolbar in your QuantumGIS instalation is disabled. You can enable it 
-again at \mainmenuopt{Settings} > \mainmenuopt{Toolbars} >
-\dropmenuopt{OpenStreetMap}. After click on the button a new dialog appears.
+the OSM toolbar in your QuantumGIS installation is probably disabled. You can 
+enable it again in \mainmenuopt{Settings} > \mainmenuopt{Toolbars} >
+\dropmenuopt{OpenStreetMap}. After clicking on the button a new dialog appears.
 
 \begin{figure}[ht]
    \begin{center}
@@ -541,29 +548,29 @@
 \end{center}
 \end{figure}
 
-Select features you want to save into XML file and the file itself.
-Use Ok button to start the operation.
-The process will create an XML file, in which OSM data from your current map
-extent are represented. OSM version of the output file is 0.6. Elements of
-OSM data (<node>, <way>, <relation>) do not contain information on their
-changesets and uids. These informations are not compulsory yet, see DTD for
-OSM XML version 0.6.
-In the output file OSM elements are not ordered.
-Notice that not only data from current extent are saved. Into the output file
-the whole polygons and lines are saved even if only small part of them is
-visible in current extent. For each saved line/polygon all its member nodes
-are saved too.
+Select features you want to save into XML file and the file itself. Use 
+the \button{Ok} button to start the operation. The process will create an 
+XML file, in which OSM data from your current map extent are represented. 
+The OSM version of the output file is 0.6. Elements of OSM data 
+(<node>, <way>, <relation>) do not contain information on their changesets 
+and uids. These informations are not compulsory yet, see DTD for
+OSM XML version 0.6. In the output file OSM elements are not ordered.
 
+Notice that not only data from the current extent are saved. Into the output 
+file the whole polygons and lines are saved even if only a small part of them 
+is visible in the current extent. For each saved line/polygon all its member 
+nodes are saved too.
+
 \subsubsection{Import OSM data}  
 
-To import OSM data from opened non-OSM vector layer follow this instructions:
-Choose current OSM data by clicking on one of their layers. Click on the 
-\toolbtntwo{osm_import}{Import data from a layer} button. If there is no 
-such button, someone has disable OpenStreetMap toolbar in your
-QGIS installation. You can enable it again at \mainmenuopt{Settings} > 
-\mainmenuopt{Toolbars} > \dropmenuopt{OpenStreetMap}. 
+To import OSM data from an opened non-OSM vector layer follow this 
+instructions: Choose current OSM data by clicking on one of their layers. 
+Click on the \toolbtntwo{osm_import}{Import data from a layer} button. If 
+there is no such button, someone has probably disable the OpenStreetMap 
+toolbar in your QGIS installation. You can enable it again in 
+\mainmenuopt{Settings} > \mainmenuopt{Toolbars} > \dropmenuopt{OpenStreetMap}. 
 
-After clicking on button following message may show up:
+After clicking on the button following message may show up:
 
 \begin{figure}[ht]
    \begin{center}
@@ -572,10 +579,10 @@
 \end{center}
 \end{figure}
 
-In such case there is no vector layer currently loaded. Import must be done
-from an opened layer - please open vector layer from which you want to import
-data. After layer is opened your second try should give you better result
-(don't forget to mark current OSM layer again):
+In such case there is no vector layer currently loaded. The import must be d
+one from a loaded layer - please load a vector layer from which you want to 
+import data. After a layer is opened, your second try should give you a 
+better result (don't forget to mark the current OSM layer again):
 
 \begin{figure}[ht]
    \begin{center}
@@ -584,7 +591,6 @@
 \end{center}
 \end{figure}
 
-Submit dialog to start the process of OSM data importing.
+Use the submit dialog to start the process of OSM data importing.
 Reject it if you are not sure you want to import something.
 
-