rviz_satellite

Plugin for rviz for displaying satellite maps loaded from the internet.

In the near future this plugin will not add support for ROS 2. For an unofficial ROS 2 fork see blacksoul000/rviz_satellite.

In order to use rviz_satellite, add this package to your catkin workspace.

Demo

The package contains a launch file for demonstration purposes. Use it to verify your installation and to get started:

roslaunch rviz_satellite demo.launch

The launch file will fake a GPS position in Philadelphia, USA and display Wikimedia Maps nearby. You can edit the longitude and latitude values in launch/demo.gps to change the position.

Check the Usage section below to learn how to use the position of your robot and a satellite map.

See demo file launch/demo_utm.launch for an example of using this plugin in the UTM frame mode (see below).

Usage

Add an instance of AerialMapDisplay to your rviz config.

The Topic field must point to a publisher of sensor_msgs/NavSatFix.

Map tiles will be cached to $HOME/.cache/rviz_satellite. At present the cache does not expire automatically - you should delete the files in the folder if you want the images to be reloaded.

Currently, we only support the OpenStreetMap convention for tile URLs. This e.g. implies that only raster tiles (no vector tiles) are supported.

Transformation of tiles to RViz fixed frame can be done in two ways that are configured using Map Transform Type option:

1. Specify a Map frame, which is an ENU-oriented frame in which your robot localizes. This mode expects that the frame of the subscribed NavSatFix messages is consistent with the measured latitude/longitude in this map frame. In this mode, the tiles go through an intermediate transform to the map frame.
2. Specify UTM frame (and possibly UTM zone). In this mode, no map frame is required and the tiles are directly placed on their UTM positions. This mode expects UTM frame is represented in your transform tree. The subscribed NavSatFix messages are only used to determine the tiles to download, so small inconsistencies between the NavSatFix frame and the measured latitude/longitude is not a big problem. In this mode, you can also change the XY and Z position references from the NavSatFix message to a TF frame. This means the point around which the tiles are displayed is determined by UTM pose of the specified frame instead of the NavSatFix messages.

Tile servers

You must provide a tile URL (Object URI) from which the satellite images are loaded. The URL should have the form http://server.tld/{z}/{x}/{y}.jpg. Where the tokens {z}, {x}, {y} represent the zoom level, x coordinate, and y coordinate respectively. If your API requires a pair of latitude and longitude values instead of x and y tile coordinates, use an URL of the form http://server.tld/{z}/{lat}/{lon}.jpg, where {lat} and {lon} represent the latitude and longitude values of the requested location. All these will automatically be substituted by rviz_satellite when making HTTP requests.

rviz_satellite doesn’t come with any preconfigured tile URL. For example, you could use one of the following tile servers:

• OpenStreetMap: https://tile.openstreetmap.org/{z}/{x}/{y}.png
• TomTom: https://api.tomtom.com/map/1/tile/basic/main/{z}/{x}/{y}.png?tileSize=512&key=[TOKEN]
• Mapbox: https://api.mapbox.com/styles/v1/mapbox/satellite-v9/tiles/256/{z}/{x}/{y}?access_token=[TOKEN]
• GoogleMaps: https://maps.googleapis.com/maps/api/staticmap?maptype=satellite&center={lat},{lon}&zoom={z}&size=256x256&key=[TOKEN]

For some of these, you have to request an access token first. Please refer to the respective terms of service and copyrights.

Options

• Topic is the topic of the GPS measurements.
• Map Transform Type selects between the Map frame mode and UTM frame mode (see section Usage).
• Alpha is simply the display transparency.
• Draw Under will cause the map to be displayed below all other geometry.
• Zoom is the zoom level of the map. Recommended values are 16-19, as anything smaller is very low resolution. 22 is the current max.
• Blocks number of adjacent blocks to load. rviz_satellite will load the central block, and this many blocks around the center. 8 is the current max.
• Z Offset specifies offset of the displayed tiles in the Z coordinate from their default pose (in meters).

Options available in Map frame mode

• Map Frame is the map frame rigidly attached to the world with ENU convention.

Options available in UTM frame mode

• UTM Frame is the frame that represents UTM coordinate frame.
• UTM Zone is the zone used by the UTM frame. Value -1 triggers autodetection of zone and this property is then overridden with the autodetected zone.
• XY Position Reference specifies how to determine the point around which tiles are centered. It can be either <NavSatFix Message>, which uses global coordinates from the received fix messages. Or it can be a TF frame name. In such case, the tiles are centered around the XY position of the specified frame in UTM coordinates.
  • Please note that selecting the UTM frame for this reference is invalid. Position of the UTM frame in UTM is (0, 0), which is an invalid UTM coordinate (supported range is 100 km - 900 km in most zones).
• Z Position Reference specifies how to determine the Z coordinate of the displayed tiles. The meaning of the values is similar to XY Position Reference. Z Offset is applied after computing the reference height.

Support and Contributions

In case of questions or problems, do not hesitate to open an issue.

Contributions are welcomed. Please add a summary of your changes to the changelog under the section Forthcoming.

Changelog for package rviz_satellite

3.1.0 (2023-02-20)

• Add possibility to specify TF frames as position reference in UTM mode.
• Turn map and UTM selection UI into TfFrameProperty.
• Simplify UTM frame mode integration.
• Improved map transform type wording.
• Added UTM frame mode.
• Added option to configure the map frame.
• Added missing header file

3.0.3 (2021-01-19)

• Pragmatic URI check
• Enable catkin_lint in CI
• Enable ros industrial CI
• Update maintainer info

3.0.2 (2020-10-13)

• Fix time synchronization of NavSat transform lookup

3.0.1 (2020-08-03)

• Fix cleanup bug breaking the navsat-tile transforms (#84, #85)

3.0.0 (2020-05-26)

• Code cleanup (#76, #75)
• Remove the 'resolution' property (#74)
• Fix frame jitter by splitting map and fixed-frame transforms (#56)
• Cleanup cmake (#70)
• Remove NED and NWU frame conversion options

2.0.0 (2020-04-17)

• Drop Qt4 support

1.3.0 (2020-04-17)

• Fix setting the fixed frame
• Fix race when reading the blocks property
• Set tile fetching preference to cache
• Remove the robot frame property. Instead use the frame from the NavSatFix topic
• Fix demo.launch
• Fix uninitialized variable

1.2.0 (2019-03-07)

• Rewrite of the tile loader
• Display an error if the tile server is invalid
• Move map towards the robot's z-position
• Use XDG cache path for caching tiles
• Incorporate orientation of tile frame when rendering map

1.1.0 (2018-12-04)

• Integrate package version via CMake
• Detect Qt 5 automatically, adding support for ROS Lunar, Melodic, et al
• Remove unused opencv linking

1.0.0 (2018-11-08)

• Initial release