MCPcopy Create free account
hub / github.com/MapIV/eagleye

github.com/MapIV/eagleye @ros2-v1.1.6

Chat with this repo
repository ↗ · DeepWiki ↗ · release ros2-v1.1.6 ↗ · + Follow
258 symbols 306 edges 53 files 0 documented · 0% updated 3mo agov1.7.3-ros2 · 2026-03-26★ 76821 open issues

Browse by type

Functions 195 Types & classes 63
What it actually does AI analysis from the code graph — generated when you open this
loading…
README

(Alpha version)

example workflow

Demo Video

What is Eagleye

Eagleye is an open-source software for vehicle localization utilizing GNSS and IMU[1]. Eagleye provides highly accurate and stable vehicle position and orientation by using GNSS Doppler[2][3][4][5][6]. The flowchart of the algorithm is shown in the figure below. The algorithms in this software are based on the outcome of the research undertaken by Machinery Information Systems Lab (Meguro Lab) in Meijo University.

Flowchart of Eagleye

Recommended Sensors

GNSS receiver * Septentrio Mosaic development kit with GNSS antenna

IMU * Tamagawa Seiki TAG300 Series * ANALOG DEVICES ADIS16475

Wheel speed sensor

  • Eagleye uses vehicle speed acquired from CAN bus.

How to install

RTKLIB

Clone and Build MapIV's fork of RTKLIB. You can find more details about RTKLIB here.

sudo apt-get install gfortran
cd $HOME
git clone -b rtklib_ros_bridge_b34 https://github.com/MapIV/RTKLIB.git
cd $HOME/RTKLIB/lib/iers/gcc/
make
cd $HOME/RTKLIB/app/consapp
make

ROS Packages

Clone and build the necessary packages for Eagleye. (rtklib_ros_bridge, nmea_ros_bridge)

cd $HOME/catkin_ws/src
git clone https://github.com/MapIV/eagleye.git -b ros2-master
git clone https://github.com/MapIV/rtklib_ros_bridge.git -b ros2-v0.1.0
git clone https://github.com/MapIV/nmea_ros_bridge.git -b ros2-v0.1.0
sudo apt-get install -y libgeographic-dev geographiclib-tools geographiclib-doc
rosdep install --from-paths src --ignore-src -r -y
colcon build --cmake-args -DCMAKE_BUILD_TYPE=Release

Configuration

GNSS

Real Time Kinematic by Mosaic

  1. nmea_ros_bridge settings.

Change adress and port of $HOME/ros2_ws/src/nmea_ros_bridge/config/udp_config.yaml according to the serial device you use.

ie)

adress: 192.168.30.10
port: 62001

  1. GNSS receiver settings.

See docs/img/mosaic_setting

IMU

  1. IMU settings.

  2. Output rate 50Hz

  3. Check the rotation direction of z axis of IMU being used. If you look from the top of the vehicle, if the left turn is positive, set "reverse_imu" to true in eagleye/eagleye_rt/config/eagleye_config.yaml.

     reverse_imu: true
    

Eagleye parameters

The parameters of eagleye can be set in the eagleye_config.yaml. The default settings are 5Hz for GNSS and 50Hz for IMU.

The TF between sensors can be set in sensors_tf.yaml. The settings are reflected by describing the positional relationship of each sensor with respect to base_link. If you want to change the base frame, change basic_parent_flame to reflect the change.

How to run

Use sample data

  1. Play the sample data.

    ros2 bag play -s rosbag_v2 eagleye_sample.bag
    
  2. Launch eagleye.

    ros2 launch eagleye_rt eagleye_rt.launch.xml
    

The estimated results will be output about 100 seconds after playing the rosbag. This is because we need to wait for the data to accumulate for estimation.

Running real-time operation

  1. Check if wheel speed (vehicle speed) is published in /can_twist topic.

  2. Topic name: /can_twist

  3. Message type: geometry_msgs/TwistStamped twist.liner.x

  4. Check if the IMU data is published in /imu/data_raw topic.

  5. Start RTKLIB.

    cd $HOME/RTKLIB
    bash rtklib_ros_bridge.sh
    
  6. Check if RTKLIB is working by execute the following command in the terminal. If the RTKLIB is working correctly, positioning information is appeared continuously in the terminal.

    status 0.1
    
  7. Start rtklib_ros_bridge.

    ros2 run rtklib_bridge rtklib_bridge --ros-args --params-file $HOME/ros2_ws/src/rtklib_ros_bridge/rtklib_bridge/param/param.yaml
    
  8. Start nmea_comms.

    ros2 launch nmea_ros_bridge nmea_udp.launch.py
    
  9. Start eagleye.

    ros2 launch eagleye_rt eagleye_rt.launch.xml
    

Note

To visualize the eagleye output location /eagleye/fix, for example, use the following command

ros2 launch eagleye_fix2kml fix2kml.xml

Sample data

ROSBAG(ROS1)

No. Date Place Sensors Link
1 2020/01/27 Moriyama, Nagoya

route|GNSS: Ublox F9P

IMU: Tamagawa AU7684

LiDAR: Velodyne HDL-32E|Download| |2|2020/07/15|Moriyama, Nagoya

route|GNSS: Ublox F9P with RTK

IMU: Tamagawa AU7684

LiDAR: Velodyne VLP-32C|Download

Maps

The 3D maps (point cloud and vector data) of the route is also available from Autoware sample data.

Research Papers for Citation

  1. J Meguro, T Arakawa, S Mizutani, A Takanose, "Low-cost Lane-level Positioning in Urban Area Using Optimized Long Time Series GNSS and IMU Data", International Conference on Intelligent Transportation Systems(ITSC), 2018 Link

  2. Takeyama Kojiro, Kojima Yoshiko, Meguro Jun-ichi, Iwase Tatsuya, Teramoto Eiji, "Trajectory Estimation Based on Tightly Coupled Integration of GPS Doppler and INS" -Improvement of Trajectory Estimation in Urban Area-, Transactions of Society of Automotive Engineers of Japan 44(1) 199-204, 2013 Link

  3. Junichi Meguro, Yoshiko Kojima, Noriyoshi Suzuki, Teramoto Eiji, "Positioning Technique Based on Vehicle Trajectory Using GPS Raw Data and Low-cost IMU", International Journal of Automotive Engineering 3(2) 75-80, 2012 Link

  4. K Takeyama, Y Kojima, E Teramoto, "Trajectory estimation improvement based on time-series constraint of GPS Doppler and INS in urban areas", IEEE/ION Position, Location and Navigation Symposium(PLANS), 2012 Link

  5. Junichi Meguro, Yoshiko Kojima, Noriyoshi Suzuki, Eiji Teramoto, "Automotive Positioning Based on Bundle Adjustment of GPS Raw Data and Vehicle Trajectory", International Technical Meeting of the Satellite Division of the Institute of Navigation (ION), 2011 Link

  6. Yoshiko Kojima, et., al., "Precise Localization using Tightly Coupled Integration based on Trajectory estimated from GPS Doppler", International Symposium on Advanced Vehicle Control(AVEC), 2010 Link

License

Eagleye is provided under the BSD 3-Clause License.

Contacts

If you have further question, email to map4@tier4.jp.

Core symbols most depended-on inside this repo

Shape

Function 185
Class 63
Method 10

Languages

C++100%

Modules by API surface

eagleye_rt/src/monitor_node.cpp50 symbols
eagleye_core/navigation/include/eagleye_navigation/eagleye_navigation.hpp30 symbols
eagleye_rt/src/rtk_heading_node.cpp11 symbols
eagleye_rt/src/heading_node.cpp10 symbols
eagleye_rt/src/trajectory_node.cpp9 symbols
eagleye_rt/src/slip_coefficient_node.cpp9 symbols
eagleye_rt/src/position_node.cpp9 symbols
eagleye_rt/src/heading_interpolate_node.cpp9 symbols
eagleye_rt/src/rtk_deadreckoning_node.cpp8 symbols
eagleye_rt/src/position_interpolate_node.cpp8 symbols
eagleye_rt/src/yawrate_offset_node.cpp7 symbols
eagleye_rt/src/height_node.cpp7 symbols

For agents

$ claude mcp add eagleye \
  -- python -m otcore.mcp_server <graph>

⬇ download graph artifact

Ask about this repo answers extend the page