Maps - Revision history

Flixr: /* Bad SRTM data issue */

2013-08-19T21:28:14Z

Bad SRTM data issue

← Older revision		Revision as of 15:28, 19 August 2013
Line 91:		Line 91:

	# stop the Simulator agent,		# stop the Simulator agent,
	# add the "-noground" option to the command		# add the "--noground" option to the pprzsim-launch command
	# and restart.		# and restart.

Loic drumettaz: /* Intoduction */

2013-07-26T12:56:46Z

Intoduction

← Older revision		Revision as of 06:56, 26 July 2013
Line 64:		Line 64:
	The Paparazzi GCS can use this elevation data. The [http://srtm.usgs.gov/ SRTM] option from the ''Nav'' menu in the GCS displays the ground altitude of the mouse in the top right hand corner.		The Paparazzi GCS can use this elevation data. The [http://srtm.usgs.gov/ SRTM] option from the ''Nav'' menu in the GCS displays the ground altitude of the mouse in the top right hand corner.

	To start the GCS with the ground altitude feature enabled, the command line option is:		To start the GCS with the ground altitude feature enabled, the command line option is -srtm:
	sw/ground_segment/cockpit/gcs -srtm
			<tt><nowiki><path_to_paparazzi>/sw/ground_segment/cockpit/gcs -srtm</nowiki></tt>

	=== Getting and using SRTM Data ===		=== Getting and using SRTM Data ===

Loic drumettaz: /* Satellite photo map tiles */

2013-07-26T12:53:46Z

Satellite photo map tiles

← Older revision		Revision as of 06:53, 26 July 2013
Line 4:		Line 4:
	The Paparazzi GCS can automatically download satellite photo tiles from Google, MS Maps and Openstreetmap for the area defined in the flight plan. The tiles of Openstreetmap are not real photos (YET!) but rendered tiles. These tiles are fully calibrated and automatically stitched together by the GCS. To load the map tiles simply select Maps->Google Maps Fill (Ctrl-G) from the GCS pulldown menu and the tiles corresponding to the GPS coordinates defined in the [[Flight_Plans\|flight plan]] will begin downloading. Pan or zoom the map and re-fill to get more tiles. Tiles are saved in <tt>var/maps/</tt> for off-line use. Checking ''Maps->Google Maps Auto'' will automatically fill the map with tiles while paning and zooming. There is also a command line option to start the GCS with the Auto-fill feature enabled:		The Paparazzi GCS can automatically download satellite photo tiles from Google, MS Maps and Openstreetmap for the area defined in the flight plan. The tiles of Openstreetmap are not real photos (YET!) but rendered tiles. These tiles are fully calibrated and automatically stitched together by the GCS. To load the map tiles simply select Maps->Google Maps Fill (Ctrl-G) from the GCS pulldown menu and the tiles corresponding to the GPS coordinates defined in the [[Flight_Plans\|flight plan]] will begin downloading. Pan or zoom the map and re-fill to get more tiles. Tiles are saved in <tt>var/maps/</tt> for off-line use. Checking ''Maps->Google Maps Auto'' will automatically fill the map with tiles while paning and zooming. There is also a command line option to start the GCS with the Auto-fill feature enabled:

	sw/ground_segment/cockpit/gcs -maps_fill		<tt><nowiki><path_to_paparazzi>/sw/ground_segment/cockpit/gcs -maps_fill</nowiki></tt>

	In v5.0 and master you can also further specify a higher maps zoom level by adding the -maps_zoom <level> option to the gcs invocation.		In v5.0 and master you can also further specify a higher maps zoom level by adding the -maps_zoom <level> option to the gcs invocation.
	The default <level> is 18, you can go up to 22.		The default <level> is 18, you can go up to 22. For example:

	~~For example:~~ sw/ground_segment/cockpit/gcs -maps_zoom 20 -maps_fill -srtm		<tt><nowiki><path_to_paparazzi>/sw/ground_segment/cockpit/gcs -maps_zoom 20 -maps_fill -srtm </nowiki></tt>

	(see ~~description~~ [http://paparazzi.enac.fr/wiki/Maps#Elevation_Data Elevation Data] below for the -srtm option)		(see [http://paparazzi.enac.fr/wiki/Maps#Elevation_Data Elevation Data] below for the -srtm option)

	If you are behind a firewall, you can use a proxy by setting the <tt>http_proxy</tt> environment variable:		If you are behind a firewall, you can use a proxy by setting the <tt>http_proxy</tt> environment variable:

Loic drumettaz: /* Intoduction */

2013-07-26T12:32:12Z

Intoduction

← Older revision		Revision as of 06:32, 26 July 2013
Line 65:		Line 65:

	To start the GCS with the ground altitude feature enabled, the command line option is:		To start the GCS with the ground altitude feature enabled, the command line option is:
			sw/ground_segment/cockpit/gcs -srtm
	~~PAPARAZZI_directory~~/ground_segment/cockpit/gcs -srtm

	=== Getting and using SRTM Data ===		=== Getting and using SRTM Data ===

Loic drumettaz: /* Satellite photo map tiles */

2013-07-26T12:31:34Z

Satellite photo map tiles

← Older revision		Revision as of 06:31, 26 July 2013
Line 4:		Line 4:
	The Paparazzi GCS can automatically download satellite photo tiles from Google, MS Maps and Openstreetmap for the area defined in the flight plan. The tiles of Openstreetmap are not real photos (YET!) but rendered tiles. These tiles are fully calibrated and automatically stitched together by the GCS. To load the map tiles simply select Maps->Google Maps Fill (Ctrl-G) from the GCS pulldown menu and the tiles corresponding to the GPS coordinates defined in the [[Flight_Plans\|flight plan]] will begin downloading. Pan or zoom the map and re-fill to get more tiles. Tiles are saved in <tt>var/maps/</tt> for off-line use. Checking ''Maps->Google Maps Auto'' will automatically fill the map with tiles while paning and zooming. There is also a command line option to start the GCS with the Auto-fill feature enabled:		The Paparazzi GCS can automatically download satellite photo tiles from Google, MS Maps and Openstreetmap for the area defined in the flight plan. The tiles of Openstreetmap are not real photos (YET!) but rendered tiles. These tiles are fully calibrated and automatically stitched together by the GCS. To load the map tiles simply select Maps->Google Maps Fill (Ctrl-G) from the GCS pulldown menu and the tiles corresponding to the GPS coordinates defined in the [[Flight_Plans\|flight plan]] will begin downloading. Pan or zoom the map and re-fill to get more tiles. Tiles are saved in <tt>var/maps/</tt> for off-line use. Checking ''Maps->Google Maps Auto'' will automatically fill the map with tiles while paning and zooming. There is also a command line option to start the GCS with the Auto-fill feature enabled:

	~~PAPARAZZI_directory~~/ground_segment/cockpit/gcs -maps_fill		sw/ground_segment/cockpit/gcs -maps_fill

			In v5.0 and master you can also further specify a higher maps zoom level by adding the -maps_zoom <level> option to the gcs invocation.
			The default <level> is 18, you can go up to 22.

			For example: sw/ground_segment/cockpit/gcs -maps_zoom 20 -maps_fill -srtm

			(see description [http://paparazzi.enac.fr/wiki/Maps#Elevation_Data Elevation Data] below for the -srtm option)

	If you are behind a firewall, you can use a proxy by setting the <tt>http_proxy</tt> environment variable:		If you are behind a firewall, you can use a proxy by setting the <tt>http_proxy</tt> environment variable:

Loic drumettaz: /* Intoduction */

2013-07-26T12:10:31Z

Intoduction

← Older revision		Revision as of 06:10, 26 July 2013
Line 56:		Line 56:

	The Paparazzi GCS can use this elevation data. The [http://srtm.usgs.gov/ SRTM] option from the ''Nav'' menu in the GCS displays the ground altitude of the mouse in the top right hand corner.		The Paparazzi GCS can use this elevation data. The [http://srtm.usgs.gov/ SRTM] option from the ''Nav'' menu in the GCS displays the ground altitude of the mouse in the top right hand corner.

			To start the GCS with the ground altitude feature enabled, the command line option is:

			PAPARAZZI_directory/ground_segment/cockpit/gcs -srtm

	=== Getting and using SRTM Data ===		=== Getting and using SRTM Data ===

Openuas: /* Satellite photo map tiles */

2013-07-26T10:47:24Z

Satellite photo map tiles

← Older revision		Revision as of 04:47, 26 July 2013
Line 3:		Line 3:

	The Paparazzi GCS can automatically download satellite photo tiles from Google, MS Maps and Openstreetmap for the area defined in the flight plan. The tiles of Openstreetmap are not real photos (YET!) but rendered tiles. These tiles are fully calibrated and automatically stitched together by the GCS. To load the map tiles simply select Maps->Google Maps Fill (Ctrl-G) from the GCS pulldown menu and the tiles corresponding to the GPS coordinates defined in the [[Flight_Plans\|flight plan]] will begin downloading. Pan or zoom the map and re-fill to get more tiles. Tiles are saved in <tt>var/maps/</tt> for off-line use. Checking ''Maps->Google Maps Auto'' will automatically fill the map with tiles while paning and zooming. There is also a command line option to start the GCS with the Auto-fill feature enabled:		The Paparazzi GCS can automatically download satellite photo tiles from Google, MS Maps and Openstreetmap for the area defined in the flight plan. The tiles of Openstreetmap are not real photos (YET!) but rendered tiles. These tiles are fully calibrated and automatically stitched together by the GCS. To load the map tiles simply select Maps->Google Maps Fill (Ctrl-G) from the GCS pulldown menu and the tiles corresponding to the GPS coordinates defined in the [[Flight_Plans\|flight plan]] will begin downloading. Pan or zoom the map and re-fill to get more tiles. Tiles are saved in <tt>var/maps/</tt> for off-line use. Checking ''Maps->Google Maps Auto'' will automatically fill the map with tiles while paning and zooming. There is also a command line option to start the GCS with the Auto-fill feature enabled:
	~~<tt>path_to_ground_segment~~/cockpit/gcs -~~google_fill</tt>.~~
			PAPARAZZI_directory/ground_segment/cockpit/gcs -maps_fill

	If you are behind a firewall, you can use a proxy by setting the <tt>http_proxy</tt> environment variable:		If you are behind a firewall, you can use a proxy by setting the <tt>http_proxy</tt> environment variable:
	<tt>export http_proxy=<nowiki>http://squid:3128</nowiki></tt>		<tt>export http_proxy=<nowiki>http://squid:3128</nowiki></tt>
Line 19:		Line 21:
	=== Google Restrictions ===		=== Google Restrictions ===

	==== ~~Wrong~~ Maptiles ====		==== Corrupted Maptiles ====

	Sometimes wrong Google maptiles are downloaded due to the beginning of the bandwidth restriction enforced by Google. If this happen and you do not wan to re-download all of you tiles, close the GCS type the following in a command prompt:		Sometimes wrong Google maptiles are downloaded due to the beginning of the bandwidth restriction enforced by Google. If this happen and you do not wan to re-download all of you tiles, close the GCS type the following in a command prompt:

Openuas: add a link

2013-07-26T10:42:18Z

add a link

← Older revision		Revision as of 04:42, 26 July 2013
Line 64:		Line 64:

	They can be downloaded from [http://dds.cr.usgs.gov/srtm/version2_1/SRTM3 http://dds.cr.usgs.gov/srtm/version2_1/SRTM3].		They can be downloaded from [http://dds.cr.usgs.gov/srtm/version2_1/SRTM3 http://dds.cr.usgs.gov/srtm/version2_1/SRTM3].

			Or get some new data here http://www.viewfinderpanoramas.org/dem3.html

	=== Better and more ===		=== Better and more ===

Scdwyer: /* Manually Defined Maps */ need to calibrate from Flight Plan Editor, not GCS

2012-11-22T23:33:42Z

Manually Defined Maps: need to calibrate from Flight Plan Editor, not GCS

← Older revision		Revision as of 17:33, 22 November 2012
Line 46:		Line 46:
	</map></tt>		</map></tt>

	These maps can be created from any image (many are available from various websites). Save the file as a jpeg and place it in the <tt>data/maps/</tt> folder. From the ~~GCS~~ select Maps->Calibrate. After loading the image (which is displayed), you will have to choose at least two reference points, name them with their geographic coordinates (in WGS84 or UTM) and save. The created map (an XML file describing the geographical position of your original bitmap) can then be loaded (Maps->Load).		These maps can be created from any image (many are available from various websites). Save the file as a jpeg and place it in the <tt>data/maps/</tt> folder. From the Flight Plan Editor select Maps->Calibrate. After loading the image (which is displayed), you will have to choose at least two reference points, name them with their geographic coordinates (in WGS84 or UTM) and save. The created map (an XML file describing the geographical position of your original bitmap) can then be loaded (Maps->Load).

	== Elevation Data ==		== Elevation Data ==

Openuas at 17:59, 5 September 2012

2012-09-05T17:59:04Z

← Older revision		Revision as of 11:59, 5 September 2012
Line 68:		Line 68:

	Some areas, for example high latitudes, are not well covered by official NASA SRTM data. Some additional data and data with higher accuracy has been compiled in the same format: [http://www.viewfinderpanoramas.org/dem3.html http://www.viewfinderpanoramas.org/dem3.html].		Some areas, for example high latitudes, are not well covered by official NASA SRTM data. Some additional data and data with higher accuracy has been compiled in the same format: [http://www.viewfinderpanoramas.org/dem3.html http://www.viewfinderpanoramas.org/dem3.html].

			==== Bad SRTM data issue ====

			You can have bad luck with SRTM data set quality. Sometimes there is a strong discontinuity in the SRTM model at a launching point location you want to use, for real and in the sim. If you load the SRTM model in the GCS (from the Nav menu), the ground altitude of the location of the pointer is displayed on the top right. You can read 131m on your HOME location, and 146m immediately to the north of this point. On takeoff, the simulator gets immediately an altitude of -15m and considers it as a '''crash'''.

			The simplest way to avoid this is to disable the ground detection in the simulator:

			# stop the Simulator agent,
			# add the "-noground" option to the command
			# and restart.

			You will read a -15m AGL during the first seconds but it won't stop. The current threshold for crash detection is -3m (sw/simulator/flightModel.ml:178 an awful numeric constant in the middle of the code, sad but true.

	=== Automating script ===		=== Automating script ===