#2 recommending GTFS import with OSM stops

Author: namdre

docs/web/docs/Tutorials/GTFS.md

@@ -80,11 +80,13 @@ From OSM you can (sometimes) get abstract schedules ("line runs every 10 minutes
 While it may be desirable to choose for every of the three data types individually whether it should be imported from OSM
 or from GTFS, currently, only the following scenarios are possible:
 
+- Import [Stops from OSM](GTFS.md#stops_from_osm). This will map each GTFS stop location to the most appropriate OSM stop location. This is the recommended approach.
 - Ignore the OSM and route data completely, see [Routes from shortest path](GTFS.md#routes_from_shortest_path).
   - This approach works with every network (not only OSM) and is the default if you do not have ptline output or your GTFS does not contain a shapes.txt file
 - Import [Routes from OSM](GTFS.md#routes_from_osm).
   - This will try to find for every GTFS route the corresponding OSM route by using geometrical distance (stop information from OSM is not used)
 
+
 ## Routes from shortest path
 
 In this case, the route for each public transport vehicle will be defined by
@@ -157,6 +159,9 @@ python tools/import/gtfs/gtfs2pt.py -n osm.net.xml.gz --gtfs GTFS_VBB_Juni-Dezem
 
 The generated simulation inputs are the same as [above](#routes_from_osm) and thus the same call to sumo/sumo-gui can be used.
 
+!!! note
+    It is recommended that the stops are imported with netconvert options **--ptstop-output <stops> --ptline-output <lines>**, because importing lines improves the localization of stops.
+
 # Using the outputs in a simulation
 
 Below an example of using the mapped stops and buses in a simulation by calling sumo-gui: