|
gdrive_ros package from jsk_3rdparty repovoicevox zdepth chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools nfc_ros respeaker_ros ros_speech_recognition rospatlite rosping sesame_ros switchbot_ros zdepth_image_transport |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-18 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Shingo Kitagawa
Authors
- Shingo Kitagawa
gdrive_ros
Google Drive file uploader for ROS: a server node which uploads local files to Google Drive (with PyDrive) on a service call and returns their URLs, and Python / EusLisp clients. The same script runs on ROS 1 and ROS 2.
Requirements
- A Google account and an OAuth 2.0 client of the Google Drive API: follow steps 1-5 of the
PyDrive quickstart (create a project in the
Google Cloud console, enable the Google Drive API, create an OAuth client ID and download it as
client_secrets.json). - A PyDrive settings yaml (format), for example:
client_config_file: /your/client/secrets/json/path
save_credentials: True
save_credentials_backend: file
save_credentials_file: /your/credentials/json/path
get_refresh_token: True
oauth_scope:
- https://www.googleapis.com/auth/drive.file
A relative client_config_file / save_credentials_file which is not found is looked up relative to the directory
of the settings yaml.
- At the first start the node runs PyDrive’s
LocalWebserverAuth(): it opens a web browser to log in to the Google account, so run it once on a machine with a browser. Withsave_credentials: Truethe token is saved tosave_credentials_fileand later starts need no login. - Python dependencies: PyDrive is not available from apt. On ROS 1 it is installed into a virtualenv by
catkin_virtualenv(requirements.txt); on ROS 2 into a uv venv (share/gdrive_ros/venv) frompyproject.toml/uv.lockat build time (jsk_ros1_ros2_compat_generate_uv_venv()). Runuv lockafter changingpyproject.toml.
Usage
ROS 2
ros2 launch gdrive_ros gdrive_server.launch.xml settings_yaml:=/your/settings/yaml/path
ros2 service call /gdrive_server/upload gdrive_ros/srv/Upload \
"{file_path: /tmp/test.txt, parents_path: example_folder}"
ros2 service call /gdrive_server/upload_multi gdrive_ros/srv/MultipleUpload \
"{file_paths: [/tmp/a.txt, /tmp/b.txt], file_titles: [a.txt, b.txt], use_timestamp_folder: true}"
The sample client uploads one file with both services:
ros2 run gdrive_ros sample_gdrive_rospy_client.py --ros-args \
-p file_name:=/tmp/test.txt -p file_title:=test.txt -p parents_path:=/example_folder
ROS 1
export GOOGLE_DRIVE_SETTINGS_YAML=/your/settings/yaml/path
roslaunch gdrive_ros gdrive_server.launch
rosservice call /gdrive_server/upload "{file_path: /tmp/test.txt, parents_path: example_folder}"
Samples, which start the server and upload a file with the Python or the EusLisp client:
roslaunch gdrive_ros sample_rospy_client.launch file_name:=/tmp/test.txt file_title:=test.txt
roslaunch gdrive_ros sample_roseus_client.launch file_name:=/tmp/test.txt file_title:=test.txt
Launch arguments
launch/gdrive_server.launch (ROS 1) and launch/gdrive_server.launch.xml (ROS 2):
| Argument | Default | Description |
|---|---|---|
settings_yaml |
$GOOGLE_DRIVE_SETTINGS_YAML, or /var/lib/robot/pydrive_settings.yaml
|
The PyDrive settings yaml |
respawn |
false |
Respawn the node |
node_name |
gdrive_server |
The node name (and so the namespace of the services) |
machine |
localhost |
ROS 1 only: the machine to run the node |
Clients
- Python:
gdrive_ros.gdrive_ros_client.GDriveROSClient(node)withwait_for_gdrive_server(),upload_file()andupload_multiple_files()(ROS 1 and ROS 2; seenode_scripts/sample_gdrive_rospy_client.py). - EusLisp (ROS 1):
euslisp/gdrive-ros-utils.lwithwait-for-gdrive-server,upload-fileandupload-multiple-files(seeeuslisp/sample-gdrive-roseus-client.l).
Both call /gdrive_server/upload and /gdrive_server/upload_multi, i.e. the server with the default node_name.
Interface
gdrive_server_node.py
Services
-
~upload(gdrive_ros/Upload): upload a file. -
~upload_multi(gdrive_ros/MultipleUpload): upload files into one folder.
File truncated at 100 lines see the full file
Changelog for package gdrive_ros
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[gdrive_ros] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the gdrive_ros python package, so gdrive_ros_client.py is installed into it. The installed ROS2 copies of the node scripts get a python3 shebang.
- package.xml: format 3 for conditions. catkin_virtualenv has no ROS2 port, so ROS2 gets PyDrive from the pydrive-pip rosdep key.
- gdrive_server_node.py, sample_gdrive_rospy_client.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only). ~upload and ~upload_multi keep their /gdrive_server/... names on ROS2.
- gdrive_ros_client.py: GDriveROSClient takes an optional rclpy node; on ROS2 it calls the services through ros_compat.call_service(). The ROS1 code path is unchanged.
- launch/gdrive_server.launch.xml: ROS2 version of gdrive_server.launch.
sample/*.launchand the euslisp client stay ROS1-only.- The ROS2 scripts are installed with jsk_ros1_ros2_compat's jsk_ros1_ros2_compat_install_python() (python3 shebang), from jsk-ros-pkg/jsk_common#1832, as a ROS2-only buildtool_depend (>= 3.0.2) that stays off rosidl's build dependencies.
- PyDrive (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), which gdrive_server_node.py runs with. This also avoids a pip rosdep key in package.xml, which bloom can not release. pyOpenSSL is in the venv too, since oauth2client imports it when present and the system one does not match the venv's cryptography.
- gdrive_server_node.py / sample_gdrive_rospy_client.py: main with ros_compat.init_node()/spin(); UploadResponse/MultipleUploadResponse
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| google_chat_ros |
Launch files
- launch/gdrive_server.launch
-
- machine [default: localhost]
- settings_yaml [default: $(optenv GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
- sample/sample_roseus_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- sample/sample_rospy_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- launch/gdrive_server.launch.xml
-
- settings_yaml [default: $(env GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
Messages
Services
Plugins
Recent questions tagged gdrive_ros at Robotics Stack Exchange
|
gdrive_ros package from jsk_3rdparty repovoicevox zdepth chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools nfc_ros respeaker_ros ros_speech_recognition rospatlite rosping sesame_ros switchbot_ros zdepth_image_transport |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-18 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Shingo Kitagawa
Authors
- Shingo Kitagawa
gdrive_ros
Google Drive file uploader for ROS: a server node which uploads local files to Google Drive (with PyDrive) on a service call and returns their URLs, and Python / EusLisp clients. The same script runs on ROS 1 and ROS 2.
Requirements
- A Google account and an OAuth 2.0 client of the Google Drive API: follow steps 1-5 of the
PyDrive quickstart (create a project in the
Google Cloud console, enable the Google Drive API, create an OAuth client ID and download it as
client_secrets.json). - A PyDrive settings yaml (format), for example:
client_config_file: /your/client/secrets/json/path
save_credentials: True
save_credentials_backend: file
save_credentials_file: /your/credentials/json/path
get_refresh_token: True
oauth_scope:
- https://www.googleapis.com/auth/drive.file
A relative client_config_file / save_credentials_file which is not found is looked up relative to the directory
of the settings yaml.
- At the first start the node runs PyDrive’s
LocalWebserverAuth(): it opens a web browser to log in to the Google account, so run it once on a machine with a browser. Withsave_credentials: Truethe token is saved tosave_credentials_fileand later starts need no login. - Python dependencies: PyDrive is not available from apt. On ROS 1 it is installed into a virtualenv by
catkin_virtualenv(requirements.txt); on ROS 2 into a uv venv (share/gdrive_ros/venv) frompyproject.toml/uv.lockat build time (jsk_ros1_ros2_compat_generate_uv_venv()). Runuv lockafter changingpyproject.toml.
Usage
ROS 2
ros2 launch gdrive_ros gdrive_server.launch.xml settings_yaml:=/your/settings/yaml/path
ros2 service call /gdrive_server/upload gdrive_ros/srv/Upload \
"{file_path: /tmp/test.txt, parents_path: example_folder}"
ros2 service call /gdrive_server/upload_multi gdrive_ros/srv/MultipleUpload \
"{file_paths: [/tmp/a.txt, /tmp/b.txt], file_titles: [a.txt, b.txt], use_timestamp_folder: true}"
The sample client uploads one file with both services:
ros2 run gdrive_ros sample_gdrive_rospy_client.py --ros-args \
-p file_name:=/tmp/test.txt -p file_title:=test.txt -p parents_path:=/example_folder
ROS 1
export GOOGLE_DRIVE_SETTINGS_YAML=/your/settings/yaml/path
roslaunch gdrive_ros gdrive_server.launch
rosservice call /gdrive_server/upload "{file_path: /tmp/test.txt, parents_path: example_folder}"
Samples, which start the server and upload a file with the Python or the EusLisp client:
roslaunch gdrive_ros sample_rospy_client.launch file_name:=/tmp/test.txt file_title:=test.txt
roslaunch gdrive_ros sample_roseus_client.launch file_name:=/tmp/test.txt file_title:=test.txt
Launch arguments
launch/gdrive_server.launch (ROS 1) and launch/gdrive_server.launch.xml (ROS 2):
| Argument | Default | Description |
|---|---|---|
settings_yaml |
$GOOGLE_DRIVE_SETTINGS_YAML, or /var/lib/robot/pydrive_settings.yaml
|
The PyDrive settings yaml |
respawn |
false |
Respawn the node |
node_name |
gdrive_server |
The node name (and so the namespace of the services) |
machine |
localhost |
ROS 1 only: the machine to run the node |
Clients
- Python:
gdrive_ros.gdrive_ros_client.GDriveROSClient(node)withwait_for_gdrive_server(),upload_file()andupload_multiple_files()(ROS 1 and ROS 2; seenode_scripts/sample_gdrive_rospy_client.py). - EusLisp (ROS 1):
euslisp/gdrive-ros-utils.lwithwait-for-gdrive-server,upload-fileandupload-multiple-files(seeeuslisp/sample-gdrive-roseus-client.l).
Both call /gdrive_server/upload and /gdrive_server/upload_multi, i.e. the server with the default node_name.
Interface
gdrive_server_node.py
Services
-
~upload(gdrive_ros/Upload): upload a file. -
~upload_multi(gdrive_ros/MultipleUpload): upload files into one folder.
File truncated at 100 lines see the full file
Changelog for package gdrive_ros
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[gdrive_ros] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the gdrive_ros python package, so gdrive_ros_client.py is installed into it. The installed ROS2 copies of the node scripts get a python3 shebang.
- package.xml: format 3 for conditions. catkin_virtualenv has no ROS2 port, so ROS2 gets PyDrive from the pydrive-pip rosdep key.
- gdrive_server_node.py, sample_gdrive_rospy_client.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only). ~upload and ~upload_multi keep their /gdrive_server/... names on ROS2.
- gdrive_ros_client.py: GDriveROSClient takes an optional rclpy node; on ROS2 it calls the services through ros_compat.call_service(). The ROS1 code path is unchanged.
- launch/gdrive_server.launch.xml: ROS2 version of gdrive_server.launch.
sample/*.launchand the euslisp client stay ROS1-only.- The ROS2 scripts are installed with jsk_ros1_ros2_compat's jsk_ros1_ros2_compat_install_python() (python3 shebang), from jsk-ros-pkg/jsk_common#1832, as a ROS2-only buildtool_depend (>= 3.0.2) that stays off rosidl's build dependencies.
- PyDrive (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), which gdrive_server_node.py runs with. This also avoids a pip rosdep key in package.xml, which bloom can not release. pyOpenSSL is in the venv too, since oauth2client imports it when present and the system one does not match the venv's cryptography.
- gdrive_server_node.py / sample_gdrive_rospy_client.py: main with ros_compat.init_node()/spin(); UploadResponse/MultipleUploadResponse
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| google_chat_ros |
Launch files
- launch/gdrive_server.launch
-
- machine [default: localhost]
- settings_yaml [default: $(optenv GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
- sample/sample_roseus_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- sample/sample_rospy_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- launch/gdrive_server.launch.xml
-
- settings_yaml [default: $(env GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
Messages
Services
Plugins
Recent questions tagged gdrive_ros at Robotics Stack Exchange
|
gdrive_ros package from jsk_3rdparty repovoicevox zdepth chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools nfc_ros respeaker_ros ros_speech_recognition rospatlite rosping sesame_ros switchbot_ros zdepth_image_transport |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-18 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Shingo Kitagawa
Authors
- Shingo Kitagawa
gdrive_ros
Google Drive file uploader for ROS: a server node which uploads local files to Google Drive (with PyDrive) on a service call and returns their URLs, and Python / EusLisp clients. The same script runs on ROS 1 and ROS 2.
Requirements
- A Google account and an OAuth 2.0 client of the Google Drive API: follow steps 1-5 of the
PyDrive quickstart (create a project in the
Google Cloud console, enable the Google Drive API, create an OAuth client ID and download it as
client_secrets.json). - A PyDrive settings yaml (format), for example:
client_config_file: /your/client/secrets/json/path
save_credentials: True
save_credentials_backend: file
save_credentials_file: /your/credentials/json/path
get_refresh_token: True
oauth_scope:
- https://www.googleapis.com/auth/drive.file
A relative client_config_file / save_credentials_file which is not found is looked up relative to the directory
of the settings yaml.
- At the first start the node runs PyDrive’s
LocalWebserverAuth(): it opens a web browser to log in to the Google account, so run it once on a machine with a browser. Withsave_credentials: Truethe token is saved tosave_credentials_fileand later starts need no login. - Python dependencies: PyDrive is not available from apt. On ROS 1 it is installed into a virtualenv by
catkin_virtualenv(requirements.txt); on ROS 2 into a uv venv (share/gdrive_ros/venv) frompyproject.toml/uv.lockat build time (jsk_ros1_ros2_compat_generate_uv_venv()). Runuv lockafter changingpyproject.toml.
Usage
ROS 2
ros2 launch gdrive_ros gdrive_server.launch.xml settings_yaml:=/your/settings/yaml/path
ros2 service call /gdrive_server/upload gdrive_ros/srv/Upload \
"{file_path: /tmp/test.txt, parents_path: example_folder}"
ros2 service call /gdrive_server/upload_multi gdrive_ros/srv/MultipleUpload \
"{file_paths: [/tmp/a.txt, /tmp/b.txt], file_titles: [a.txt, b.txt], use_timestamp_folder: true}"
The sample client uploads one file with both services:
ros2 run gdrive_ros sample_gdrive_rospy_client.py --ros-args \
-p file_name:=/tmp/test.txt -p file_title:=test.txt -p parents_path:=/example_folder
ROS 1
export GOOGLE_DRIVE_SETTINGS_YAML=/your/settings/yaml/path
roslaunch gdrive_ros gdrive_server.launch
rosservice call /gdrive_server/upload "{file_path: /tmp/test.txt, parents_path: example_folder}"
Samples, which start the server and upload a file with the Python or the EusLisp client:
roslaunch gdrive_ros sample_rospy_client.launch file_name:=/tmp/test.txt file_title:=test.txt
roslaunch gdrive_ros sample_roseus_client.launch file_name:=/tmp/test.txt file_title:=test.txt
Launch arguments
launch/gdrive_server.launch (ROS 1) and launch/gdrive_server.launch.xml (ROS 2):
| Argument | Default | Description |
|---|---|---|
settings_yaml |
$GOOGLE_DRIVE_SETTINGS_YAML, or /var/lib/robot/pydrive_settings.yaml
|
The PyDrive settings yaml |
respawn |
false |
Respawn the node |
node_name |
gdrive_server |
The node name (and so the namespace of the services) |
machine |
localhost |
ROS 1 only: the machine to run the node |
Clients
- Python:
gdrive_ros.gdrive_ros_client.GDriveROSClient(node)withwait_for_gdrive_server(),upload_file()andupload_multiple_files()(ROS 1 and ROS 2; seenode_scripts/sample_gdrive_rospy_client.py). - EusLisp (ROS 1):
euslisp/gdrive-ros-utils.lwithwait-for-gdrive-server,upload-fileandupload-multiple-files(seeeuslisp/sample-gdrive-roseus-client.l).
Both call /gdrive_server/upload and /gdrive_server/upload_multi, i.e. the server with the default node_name.
Interface
gdrive_server_node.py
Services
-
~upload(gdrive_ros/Upload): upload a file. -
~upload_multi(gdrive_ros/MultipleUpload): upload files into one folder.
File truncated at 100 lines see the full file
Changelog for package gdrive_ros
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[gdrive_ros] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the gdrive_ros python package, so gdrive_ros_client.py is installed into it. The installed ROS2 copies of the node scripts get a python3 shebang.
- package.xml: format 3 for conditions. catkin_virtualenv has no ROS2 port, so ROS2 gets PyDrive from the pydrive-pip rosdep key.
- gdrive_server_node.py, sample_gdrive_rospy_client.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only). ~upload and ~upload_multi keep their /gdrive_server/... names on ROS2.
- gdrive_ros_client.py: GDriveROSClient takes an optional rclpy node; on ROS2 it calls the services through ros_compat.call_service(). The ROS1 code path is unchanged.
- launch/gdrive_server.launch.xml: ROS2 version of gdrive_server.launch.
sample/*.launchand the euslisp client stay ROS1-only.- The ROS2 scripts are installed with jsk_ros1_ros2_compat's jsk_ros1_ros2_compat_install_python() (python3 shebang), from jsk-ros-pkg/jsk_common#1832, as a ROS2-only buildtool_depend (>= 3.0.2) that stays off rosidl's build dependencies.
- PyDrive (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), which gdrive_server_node.py runs with. This also avoids a pip rosdep key in package.xml, which bloom can not release. pyOpenSSL is in the venv too, since oauth2client imports it when present and the system one does not match the venv's cryptography.
- gdrive_server_node.py / sample_gdrive_rospy_client.py: main with ros_compat.init_node()/spin(); UploadResponse/MultipleUploadResponse
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| google_chat_ros |
Launch files
- launch/gdrive_server.launch
-
- machine [default: localhost]
- settings_yaml [default: $(optenv GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
- sample/sample_roseus_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- sample/sample_rospy_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- launch/gdrive_server.launch.xml
-
- settings_yaml [default: $(env GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
Messages
Services
Plugins
Recent questions tagged gdrive_ros at Robotics Stack Exchange
|
gdrive_ros package from jsk_3rdparty repovoicevox zdepth chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools nfc_ros respeaker_ros ros_speech_recognition rospatlite rosping sesame_ros switchbot_ros zdepth_image_transport |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-18 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Shingo Kitagawa
Authors
- Shingo Kitagawa
gdrive_ros
Google Drive file uploader for ROS: a server node which uploads local files to Google Drive (with PyDrive) on a service call and returns their URLs, and Python / EusLisp clients. The same script runs on ROS 1 and ROS 2.
Requirements
- A Google account and an OAuth 2.0 client of the Google Drive API: follow steps 1-5 of the
PyDrive quickstart (create a project in the
Google Cloud console, enable the Google Drive API, create an OAuth client ID and download it as
client_secrets.json). - A PyDrive settings yaml (format), for example:
client_config_file: /your/client/secrets/json/path
save_credentials: True
save_credentials_backend: file
save_credentials_file: /your/credentials/json/path
get_refresh_token: True
oauth_scope:
- https://www.googleapis.com/auth/drive.file
A relative client_config_file / save_credentials_file which is not found is looked up relative to the directory
of the settings yaml.
- At the first start the node runs PyDrive’s
LocalWebserverAuth(): it opens a web browser to log in to the Google account, so run it once on a machine with a browser. Withsave_credentials: Truethe token is saved tosave_credentials_fileand later starts need no login. - Python dependencies: PyDrive is not available from apt. On ROS 1 it is installed into a virtualenv by
catkin_virtualenv(requirements.txt); on ROS 2 into a uv venv (share/gdrive_ros/venv) frompyproject.toml/uv.lockat build time (jsk_ros1_ros2_compat_generate_uv_venv()). Runuv lockafter changingpyproject.toml.
Usage
ROS 2
ros2 launch gdrive_ros gdrive_server.launch.xml settings_yaml:=/your/settings/yaml/path
ros2 service call /gdrive_server/upload gdrive_ros/srv/Upload \
"{file_path: /tmp/test.txt, parents_path: example_folder}"
ros2 service call /gdrive_server/upload_multi gdrive_ros/srv/MultipleUpload \
"{file_paths: [/tmp/a.txt, /tmp/b.txt], file_titles: [a.txt, b.txt], use_timestamp_folder: true}"
The sample client uploads one file with both services:
ros2 run gdrive_ros sample_gdrive_rospy_client.py --ros-args \
-p file_name:=/tmp/test.txt -p file_title:=test.txt -p parents_path:=/example_folder
ROS 1
export GOOGLE_DRIVE_SETTINGS_YAML=/your/settings/yaml/path
roslaunch gdrive_ros gdrive_server.launch
rosservice call /gdrive_server/upload "{file_path: /tmp/test.txt, parents_path: example_folder}"
Samples, which start the server and upload a file with the Python or the EusLisp client:
roslaunch gdrive_ros sample_rospy_client.launch file_name:=/tmp/test.txt file_title:=test.txt
roslaunch gdrive_ros sample_roseus_client.launch file_name:=/tmp/test.txt file_title:=test.txt
Launch arguments
launch/gdrive_server.launch (ROS 1) and launch/gdrive_server.launch.xml (ROS 2):
| Argument | Default | Description |
|---|---|---|
settings_yaml |
$GOOGLE_DRIVE_SETTINGS_YAML, or /var/lib/robot/pydrive_settings.yaml
|
The PyDrive settings yaml |
respawn |
false |
Respawn the node |
node_name |
gdrive_server |
The node name (and so the namespace of the services) |
machine |
localhost |
ROS 1 only: the machine to run the node |
Clients
- Python:
gdrive_ros.gdrive_ros_client.GDriveROSClient(node)withwait_for_gdrive_server(),upload_file()andupload_multiple_files()(ROS 1 and ROS 2; seenode_scripts/sample_gdrive_rospy_client.py). - EusLisp (ROS 1):
euslisp/gdrive-ros-utils.lwithwait-for-gdrive-server,upload-fileandupload-multiple-files(seeeuslisp/sample-gdrive-roseus-client.l).
Both call /gdrive_server/upload and /gdrive_server/upload_multi, i.e. the server with the default node_name.
Interface
gdrive_server_node.py
Services
-
~upload(gdrive_ros/Upload): upload a file. -
~upload_multi(gdrive_ros/MultipleUpload): upload files into one folder.
File truncated at 100 lines see the full file
Changelog for package gdrive_ros
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[gdrive_ros] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the gdrive_ros python package, so gdrive_ros_client.py is installed into it. The installed ROS2 copies of the node scripts get a python3 shebang.
- package.xml: format 3 for conditions. catkin_virtualenv has no ROS2 port, so ROS2 gets PyDrive from the pydrive-pip rosdep key.
- gdrive_server_node.py, sample_gdrive_rospy_client.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only). ~upload and ~upload_multi keep their /gdrive_server/... names on ROS2.
- gdrive_ros_client.py: GDriveROSClient takes an optional rclpy node; on ROS2 it calls the services through ros_compat.call_service(). The ROS1 code path is unchanged.
- launch/gdrive_server.launch.xml: ROS2 version of gdrive_server.launch.
sample/*.launchand the euslisp client stay ROS1-only.- The ROS2 scripts are installed with jsk_ros1_ros2_compat's jsk_ros1_ros2_compat_install_python() (python3 shebang), from jsk-ros-pkg/jsk_common#1832, as a ROS2-only buildtool_depend (>= 3.0.2) that stays off rosidl's build dependencies.
- PyDrive (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), which gdrive_server_node.py runs with. This also avoids a pip rosdep key in package.xml, which bloom can not release. pyOpenSSL is in the venv too, since oauth2client imports it when present and the system one does not match the venv's cryptography.
- gdrive_server_node.py / sample_gdrive_rospy_client.py: main with ros_compat.init_node()/spin(); UploadResponse/MultipleUploadResponse
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| google_chat_ros |
Launch files
- launch/gdrive_server.launch
-
- machine [default: localhost]
- settings_yaml [default: $(optenv GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
- sample/sample_roseus_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- sample/sample_rospy_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- launch/gdrive_server.launch.xml
-
- settings_yaml [default: $(env GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
Messages
Services
Plugins
Recent questions tagged gdrive_ros at Robotics Stack Exchange
|
gdrive_ros package from jsk_3rdparty repovoicevox zdepth chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools nfc_ros respeaker_ros ros_speech_recognition rospatlite rosping sesame_ros switchbot_ros zdepth_image_transport |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-18 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Shingo Kitagawa
Authors
- Shingo Kitagawa
gdrive_ros
Google Drive file uploader for ROS: a server node which uploads local files to Google Drive (with PyDrive) on a service call and returns their URLs, and Python / EusLisp clients. The same script runs on ROS 1 and ROS 2.
Requirements
- A Google account and an OAuth 2.0 client of the Google Drive API: follow steps 1-5 of the
PyDrive quickstart (create a project in the
Google Cloud console, enable the Google Drive API, create an OAuth client ID and download it as
client_secrets.json). - A PyDrive settings yaml (format), for example:
client_config_file: /your/client/secrets/json/path
save_credentials: True
save_credentials_backend: file
save_credentials_file: /your/credentials/json/path
get_refresh_token: True
oauth_scope:
- https://www.googleapis.com/auth/drive.file
A relative client_config_file / save_credentials_file which is not found is looked up relative to the directory
of the settings yaml.
- At the first start the node runs PyDrive’s
LocalWebserverAuth(): it opens a web browser to log in to the Google account, so run it once on a machine with a browser. Withsave_credentials: Truethe token is saved tosave_credentials_fileand later starts need no login. - Python dependencies: PyDrive is not available from apt. On ROS 1 it is installed into a virtualenv by
catkin_virtualenv(requirements.txt); on ROS 2 into a uv venv (share/gdrive_ros/venv) frompyproject.toml/uv.lockat build time (jsk_ros1_ros2_compat_generate_uv_venv()). Runuv lockafter changingpyproject.toml.
Usage
ROS 2
ros2 launch gdrive_ros gdrive_server.launch.xml settings_yaml:=/your/settings/yaml/path
ros2 service call /gdrive_server/upload gdrive_ros/srv/Upload \
"{file_path: /tmp/test.txt, parents_path: example_folder}"
ros2 service call /gdrive_server/upload_multi gdrive_ros/srv/MultipleUpload \
"{file_paths: [/tmp/a.txt, /tmp/b.txt], file_titles: [a.txt, b.txt], use_timestamp_folder: true}"
The sample client uploads one file with both services:
ros2 run gdrive_ros sample_gdrive_rospy_client.py --ros-args \
-p file_name:=/tmp/test.txt -p file_title:=test.txt -p parents_path:=/example_folder
ROS 1
export GOOGLE_DRIVE_SETTINGS_YAML=/your/settings/yaml/path
roslaunch gdrive_ros gdrive_server.launch
rosservice call /gdrive_server/upload "{file_path: /tmp/test.txt, parents_path: example_folder}"
Samples, which start the server and upload a file with the Python or the EusLisp client:
roslaunch gdrive_ros sample_rospy_client.launch file_name:=/tmp/test.txt file_title:=test.txt
roslaunch gdrive_ros sample_roseus_client.launch file_name:=/tmp/test.txt file_title:=test.txt
Launch arguments
launch/gdrive_server.launch (ROS 1) and launch/gdrive_server.launch.xml (ROS 2):
| Argument | Default | Description |
|---|---|---|
settings_yaml |
$GOOGLE_DRIVE_SETTINGS_YAML, or /var/lib/robot/pydrive_settings.yaml
|
The PyDrive settings yaml |
respawn |
false |
Respawn the node |
node_name |
gdrive_server |
The node name (and so the namespace of the services) |
machine |
localhost |
ROS 1 only: the machine to run the node |
Clients
- Python:
gdrive_ros.gdrive_ros_client.GDriveROSClient(node)withwait_for_gdrive_server(),upload_file()andupload_multiple_files()(ROS 1 and ROS 2; seenode_scripts/sample_gdrive_rospy_client.py). - EusLisp (ROS 1):
euslisp/gdrive-ros-utils.lwithwait-for-gdrive-server,upload-fileandupload-multiple-files(seeeuslisp/sample-gdrive-roseus-client.l).
Both call /gdrive_server/upload and /gdrive_server/upload_multi, i.e. the server with the default node_name.
Interface
gdrive_server_node.py
Services
-
~upload(gdrive_ros/Upload): upload a file. -
~upload_multi(gdrive_ros/MultipleUpload): upload files into one folder.
File truncated at 100 lines see the full file
Changelog for package gdrive_ros
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[gdrive_ros] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the gdrive_ros python package, so gdrive_ros_client.py is installed into it. The installed ROS2 copies of the node scripts get a python3 shebang.
- package.xml: format 3 for conditions. catkin_virtualenv has no ROS2 port, so ROS2 gets PyDrive from the pydrive-pip rosdep key.
- gdrive_server_node.py, sample_gdrive_rospy_client.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only). ~upload and ~upload_multi keep their /gdrive_server/... names on ROS2.
- gdrive_ros_client.py: GDriveROSClient takes an optional rclpy node; on ROS2 it calls the services through ros_compat.call_service(). The ROS1 code path is unchanged.
- launch/gdrive_server.launch.xml: ROS2 version of gdrive_server.launch.
sample/*.launchand the euslisp client stay ROS1-only.- The ROS2 scripts are installed with jsk_ros1_ros2_compat's jsk_ros1_ros2_compat_install_python() (python3 shebang), from jsk-ros-pkg/jsk_common#1832, as a ROS2-only buildtool_depend (>= 3.0.2) that stays off rosidl's build dependencies.
- PyDrive (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), which gdrive_server_node.py runs with. This also avoids a pip rosdep key in package.xml, which bloom can not release. pyOpenSSL is in the venv too, since oauth2client imports it when present and the system one does not match the venv's cryptography.
- gdrive_server_node.py / sample_gdrive_rospy_client.py: main with ros_compat.init_node()/spin(); UploadResponse/MultipleUploadResponse
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| google_chat_ros |
Launch files
- launch/gdrive_server.launch
-
- machine [default: localhost]
- settings_yaml [default: $(optenv GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
- sample/sample_roseus_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- sample/sample_rospy_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- launch/gdrive_server.launch.xml
-
- settings_yaml [default: $(env GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
Messages
Services
Plugins
Recent questions tagged gdrive_ros at Robotics Stack Exchange
|
gdrive_ros package from jsk_3rdparty repovoicevox zdepth chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools nfc_ros respeaker_ros ros_speech_recognition rospatlite rosping sesame_ros switchbot_ros zdepth_image_transport |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-18 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Shingo Kitagawa
Authors
- Shingo Kitagawa
gdrive_ros
Google Drive file uploader for ROS: a server node which uploads local files to Google Drive (with PyDrive) on a service call and returns their URLs, and Python / EusLisp clients. The same script runs on ROS 1 and ROS 2.
Requirements
- A Google account and an OAuth 2.0 client of the Google Drive API: follow steps 1-5 of the
PyDrive quickstart (create a project in the
Google Cloud console, enable the Google Drive API, create an OAuth client ID and download it as
client_secrets.json). - A PyDrive settings yaml (format), for example:
client_config_file: /your/client/secrets/json/path
save_credentials: True
save_credentials_backend: file
save_credentials_file: /your/credentials/json/path
get_refresh_token: True
oauth_scope:
- https://www.googleapis.com/auth/drive.file
A relative client_config_file / save_credentials_file which is not found is looked up relative to the directory
of the settings yaml.
- At the first start the node runs PyDrive’s
LocalWebserverAuth(): it opens a web browser to log in to the Google account, so run it once on a machine with a browser. Withsave_credentials: Truethe token is saved tosave_credentials_fileand later starts need no login. - Python dependencies: PyDrive is not available from apt. On ROS 1 it is installed into a virtualenv by
catkin_virtualenv(requirements.txt); on ROS 2 into a uv venv (share/gdrive_ros/venv) frompyproject.toml/uv.lockat build time (jsk_ros1_ros2_compat_generate_uv_venv()). Runuv lockafter changingpyproject.toml.
Usage
ROS 2
ros2 launch gdrive_ros gdrive_server.launch.xml settings_yaml:=/your/settings/yaml/path
ros2 service call /gdrive_server/upload gdrive_ros/srv/Upload \
"{file_path: /tmp/test.txt, parents_path: example_folder}"
ros2 service call /gdrive_server/upload_multi gdrive_ros/srv/MultipleUpload \
"{file_paths: [/tmp/a.txt, /tmp/b.txt], file_titles: [a.txt, b.txt], use_timestamp_folder: true}"
The sample client uploads one file with both services:
ros2 run gdrive_ros sample_gdrive_rospy_client.py --ros-args \
-p file_name:=/tmp/test.txt -p file_title:=test.txt -p parents_path:=/example_folder
ROS 1
export GOOGLE_DRIVE_SETTINGS_YAML=/your/settings/yaml/path
roslaunch gdrive_ros gdrive_server.launch
rosservice call /gdrive_server/upload "{file_path: /tmp/test.txt, parents_path: example_folder}"
Samples, which start the server and upload a file with the Python or the EusLisp client:
roslaunch gdrive_ros sample_rospy_client.launch file_name:=/tmp/test.txt file_title:=test.txt
roslaunch gdrive_ros sample_roseus_client.launch file_name:=/tmp/test.txt file_title:=test.txt
Launch arguments
launch/gdrive_server.launch (ROS 1) and launch/gdrive_server.launch.xml (ROS 2):
| Argument | Default | Description |
|---|---|---|
settings_yaml |
$GOOGLE_DRIVE_SETTINGS_YAML, or /var/lib/robot/pydrive_settings.yaml
|
The PyDrive settings yaml |
respawn |
false |
Respawn the node |
node_name |
gdrive_server |
The node name (and so the namespace of the services) |
machine |
localhost |
ROS 1 only: the machine to run the node |
Clients
- Python:
gdrive_ros.gdrive_ros_client.GDriveROSClient(node)withwait_for_gdrive_server(),upload_file()andupload_multiple_files()(ROS 1 and ROS 2; seenode_scripts/sample_gdrive_rospy_client.py). - EusLisp (ROS 1):
euslisp/gdrive-ros-utils.lwithwait-for-gdrive-server,upload-fileandupload-multiple-files(seeeuslisp/sample-gdrive-roseus-client.l).
Both call /gdrive_server/upload and /gdrive_server/upload_multi, i.e. the server with the default node_name.
Interface
gdrive_server_node.py
Services
-
~upload(gdrive_ros/Upload): upload a file. -
~upload_multi(gdrive_ros/MultipleUpload): upload files into one folder.
File truncated at 100 lines see the full file
Changelog for package gdrive_ros
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[gdrive_ros] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the gdrive_ros python package, so gdrive_ros_client.py is installed into it. The installed ROS2 copies of the node scripts get a python3 shebang.
- package.xml: format 3 for conditions. catkin_virtualenv has no ROS2 port, so ROS2 gets PyDrive from the pydrive-pip rosdep key.
- gdrive_server_node.py, sample_gdrive_rospy_client.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only). ~upload and ~upload_multi keep their /gdrive_server/... names on ROS2.
- gdrive_ros_client.py: GDriveROSClient takes an optional rclpy node; on ROS2 it calls the services through ros_compat.call_service(). The ROS1 code path is unchanged.
- launch/gdrive_server.launch.xml: ROS2 version of gdrive_server.launch.
sample/*.launchand the euslisp client stay ROS1-only.- The ROS2 scripts are installed with jsk_ros1_ros2_compat's jsk_ros1_ros2_compat_install_python() (python3 shebang), from jsk-ros-pkg/jsk_common#1832, as a ROS2-only buildtool_depend (>= 3.0.2) that stays off rosidl's build dependencies.
- PyDrive (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), which gdrive_server_node.py runs with. This also avoids a pip rosdep key in package.xml, which bloom can not release. pyOpenSSL is in the venv too, since oauth2client imports it when present and the system one does not match the venv's cryptography.
- gdrive_server_node.py / sample_gdrive_rospy_client.py: main with ros_compat.init_node()/spin(); UploadResponse/MultipleUploadResponse
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| google_chat_ros |
Launch files
- launch/gdrive_server.launch
-
- machine [default: localhost]
- settings_yaml [default: $(optenv GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
- sample/sample_roseus_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- sample/sample_rospy_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- launch/gdrive_server.launch.xml
-
- settings_yaml [default: $(env GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
Messages
Services
Plugins
Recent questions tagged gdrive_ros at Robotics Stack Exchange
|
gdrive_ros package from jsk_3rdparty repovoicevox zdepth chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools nfc_ros respeaker_ros ros_speech_recognition rospatlite rosping sesame_ros switchbot_ros zdepth_image_transport |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-18 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Shingo Kitagawa
Authors
- Shingo Kitagawa
gdrive_ros
Google Drive file uploader for ROS: a server node which uploads local files to Google Drive (with PyDrive) on a service call and returns their URLs, and Python / EusLisp clients. The same script runs on ROS 1 and ROS 2.
Requirements
- A Google account and an OAuth 2.0 client of the Google Drive API: follow steps 1-5 of the
PyDrive quickstart (create a project in the
Google Cloud console, enable the Google Drive API, create an OAuth client ID and download it as
client_secrets.json). - A PyDrive settings yaml (format), for example:
client_config_file: /your/client/secrets/json/path
save_credentials: True
save_credentials_backend: file
save_credentials_file: /your/credentials/json/path
get_refresh_token: True
oauth_scope:
- https://www.googleapis.com/auth/drive.file
A relative client_config_file / save_credentials_file which is not found is looked up relative to the directory
of the settings yaml.
- At the first start the node runs PyDrive’s
LocalWebserverAuth(): it opens a web browser to log in to the Google account, so run it once on a machine with a browser. Withsave_credentials: Truethe token is saved tosave_credentials_fileand later starts need no login. - Python dependencies: PyDrive is not available from apt. On ROS 1 it is installed into a virtualenv by
catkin_virtualenv(requirements.txt); on ROS 2 into a uv venv (share/gdrive_ros/venv) frompyproject.toml/uv.lockat build time (jsk_ros1_ros2_compat_generate_uv_venv()). Runuv lockafter changingpyproject.toml.
Usage
ROS 2
ros2 launch gdrive_ros gdrive_server.launch.xml settings_yaml:=/your/settings/yaml/path
ros2 service call /gdrive_server/upload gdrive_ros/srv/Upload \
"{file_path: /tmp/test.txt, parents_path: example_folder}"
ros2 service call /gdrive_server/upload_multi gdrive_ros/srv/MultipleUpload \
"{file_paths: [/tmp/a.txt, /tmp/b.txt], file_titles: [a.txt, b.txt], use_timestamp_folder: true}"
The sample client uploads one file with both services:
ros2 run gdrive_ros sample_gdrive_rospy_client.py --ros-args \
-p file_name:=/tmp/test.txt -p file_title:=test.txt -p parents_path:=/example_folder
ROS 1
export GOOGLE_DRIVE_SETTINGS_YAML=/your/settings/yaml/path
roslaunch gdrive_ros gdrive_server.launch
rosservice call /gdrive_server/upload "{file_path: /tmp/test.txt, parents_path: example_folder}"
Samples, which start the server and upload a file with the Python or the EusLisp client:
roslaunch gdrive_ros sample_rospy_client.launch file_name:=/tmp/test.txt file_title:=test.txt
roslaunch gdrive_ros sample_roseus_client.launch file_name:=/tmp/test.txt file_title:=test.txt
Launch arguments
launch/gdrive_server.launch (ROS 1) and launch/gdrive_server.launch.xml (ROS 2):
| Argument | Default | Description |
|---|---|---|
settings_yaml |
$GOOGLE_DRIVE_SETTINGS_YAML, or /var/lib/robot/pydrive_settings.yaml
|
The PyDrive settings yaml |
respawn |
false |
Respawn the node |
node_name |
gdrive_server |
The node name (and so the namespace of the services) |
machine |
localhost |
ROS 1 only: the machine to run the node |
Clients
- Python:
gdrive_ros.gdrive_ros_client.GDriveROSClient(node)withwait_for_gdrive_server(),upload_file()andupload_multiple_files()(ROS 1 and ROS 2; seenode_scripts/sample_gdrive_rospy_client.py). - EusLisp (ROS 1):
euslisp/gdrive-ros-utils.lwithwait-for-gdrive-server,upload-fileandupload-multiple-files(seeeuslisp/sample-gdrive-roseus-client.l).
Both call /gdrive_server/upload and /gdrive_server/upload_multi, i.e. the server with the default node_name.
Interface
gdrive_server_node.py
Services
-
~upload(gdrive_ros/Upload): upload a file. -
~upload_multi(gdrive_ros/MultipleUpload): upload files into one folder.
File truncated at 100 lines see the full file
Changelog for package gdrive_ros
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[gdrive_ros] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the gdrive_ros python package, so gdrive_ros_client.py is installed into it. The installed ROS2 copies of the node scripts get a python3 shebang.
- package.xml: format 3 for conditions. catkin_virtualenv has no ROS2 port, so ROS2 gets PyDrive from the pydrive-pip rosdep key.
- gdrive_server_node.py, sample_gdrive_rospy_client.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only). ~upload and ~upload_multi keep their /gdrive_server/... names on ROS2.
- gdrive_ros_client.py: GDriveROSClient takes an optional rclpy node; on ROS2 it calls the services through ros_compat.call_service(). The ROS1 code path is unchanged.
- launch/gdrive_server.launch.xml: ROS2 version of gdrive_server.launch.
sample/*.launchand the euslisp client stay ROS1-only.- The ROS2 scripts are installed with jsk_ros1_ros2_compat's jsk_ros1_ros2_compat_install_python() (python3 shebang), from jsk-ros-pkg/jsk_common#1832, as a ROS2-only buildtool_depend (>= 3.0.2) that stays off rosidl's build dependencies.
- PyDrive (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), which gdrive_server_node.py runs with. This also avoids a pip rosdep key in package.xml, which bloom can not release. pyOpenSSL is in the venv too, since oauth2client imports it when present and the system one does not match the venv's cryptography.
- gdrive_server_node.py / sample_gdrive_rospy_client.py: main with ros_compat.init_node()/spin(); UploadResponse/MultipleUploadResponse
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| google_chat_ros |
Launch files
- launch/gdrive_server.launch
-
- machine [default: localhost]
- settings_yaml [default: $(optenv GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
- sample/sample_roseus_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- sample/sample_rospy_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- launch/gdrive_server.launch.xml
-
- settings_yaml [default: $(env GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
Messages
Services
Plugins
Recent questions tagged gdrive_ros at Robotics Stack Exchange
|
gdrive_ros package from jsk_3rdparty repovoicevox zdepth chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools nfc_ros respeaker_ros ros_speech_recognition rospatlite rosping sesame_ros switchbot_ros zdepth_image_transport |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-18 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Shingo Kitagawa
Authors
- Shingo Kitagawa
gdrive_ros
Google Drive file uploader for ROS: a server node which uploads local files to Google Drive (with PyDrive) on a service call and returns their URLs, and Python / EusLisp clients. The same script runs on ROS 1 and ROS 2.
Requirements
- A Google account and an OAuth 2.0 client of the Google Drive API: follow steps 1-5 of the
PyDrive quickstart (create a project in the
Google Cloud console, enable the Google Drive API, create an OAuth client ID and download it as
client_secrets.json). - A PyDrive settings yaml (format), for example:
client_config_file: /your/client/secrets/json/path
save_credentials: True
save_credentials_backend: file
save_credentials_file: /your/credentials/json/path
get_refresh_token: True
oauth_scope:
- https://www.googleapis.com/auth/drive.file
A relative client_config_file / save_credentials_file which is not found is looked up relative to the directory
of the settings yaml.
- At the first start the node runs PyDrive’s
LocalWebserverAuth(): it opens a web browser to log in to the Google account, so run it once on a machine with a browser. Withsave_credentials: Truethe token is saved tosave_credentials_fileand later starts need no login. - Python dependencies: PyDrive is not available from apt. On ROS 1 it is installed into a virtualenv by
catkin_virtualenv(requirements.txt); on ROS 2 into a uv venv (share/gdrive_ros/venv) frompyproject.toml/uv.lockat build time (jsk_ros1_ros2_compat_generate_uv_venv()). Runuv lockafter changingpyproject.toml.
Usage
ROS 2
ros2 launch gdrive_ros gdrive_server.launch.xml settings_yaml:=/your/settings/yaml/path
ros2 service call /gdrive_server/upload gdrive_ros/srv/Upload \
"{file_path: /tmp/test.txt, parents_path: example_folder}"
ros2 service call /gdrive_server/upload_multi gdrive_ros/srv/MultipleUpload \
"{file_paths: [/tmp/a.txt, /tmp/b.txt], file_titles: [a.txt, b.txt], use_timestamp_folder: true}"
The sample client uploads one file with both services:
ros2 run gdrive_ros sample_gdrive_rospy_client.py --ros-args \
-p file_name:=/tmp/test.txt -p file_title:=test.txt -p parents_path:=/example_folder
ROS 1
export GOOGLE_DRIVE_SETTINGS_YAML=/your/settings/yaml/path
roslaunch gdrive_ros gdrive_server.launch
rosservice call /gdrive_server/upload "{file_path: /tmp/test.txt, parents_path: example_folder}"
Samples, which start the server and upload a file with the Python or the EusLisp client:
roslaunch gdrive_ros sample_rospy_client.launch file_name:=/tmp/test.txt file_title:=test.txt
roslaunch gdrive_ros sample_roseus_client.launch file_name:=/tmp/test.txt file_title:=test.txt
Launch arguments
launch/gdrive_server.launch (ROS 1) and launch/gdrive_server.launch.xml (ROS 2):
| Argument | Default | Description |
|---|---|---|
settings_yaml |
$GOOGLE_DRIVE_SETTINGS_YAML, or /var/lib/robot/pydrive_settings.yaml
|
The PyDrive settings yaml |
respawn |
false |
Respawn the node |
node_name |
gdrive_server |
The node name (and so the namespace of the services) |
machine |
localhost |
ROS 1 only: the machine to run the node |
Clients
- Python:
gdrive_ros.gdrive_ros_client.GDriveROSClient(node)withwait_for_gdrive_server(),upload_file()andupload_multiple_files()(ROS 1 and ROS 2; seenode_scripts/sample_gdrive_rospy_client.py). - EusLisp (ROS 1):
euslisp/gdrive-ros-utils.lwithwait-for-gdrive-server,upload-fileandupload-multiple-files(seeeuslisp/sample-gdrive-roseus-client.l).
Both call /gdrive_server/upload and /gdrive_server/upload_multi, i.e. the server with the default node_name.
Interface
gdrive_server_node.py
Services
-
~upload(gdrive_ros/Upload): upload a file. -
~upload_multi(gdrive_ros/MultipleUpload): upload files into one folder.
File truncated at 100 lines see the full file
Changelog for package gdrive_ros
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[gdrive_ros] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the gdrive_ros python package, so gdrive_ros_client.py is installed into it. The installed ROS2 copies of the node scripts get a python3 shebang.
- package.xml: format 3 for conditions. catkin_virtualenv has no ROS2 port, so ROS2 gets PyDrive from the pydrive-pip rosdep key.
- gdrive_server_node.py, sample_gdrive_rospy_client.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only). ~upload and ~upload_multi keep their /gdrive_server/... names on ROS2.
- gdrive_ros_client.py: GDriveROSClient takes an optional rclpy node; on ROS2 it calls the services through ros_compat.call_service(). The ROS1 code path is unchanged.
- launch/gdrive_server.launch.xml: ROS2 version of gdrive_server.launch.
sample/*.launchand the euslisp client stay ROS1-only.- The ROS2 scripts are installed with jsk_ros1_ros2_compat's jsk_ros1_ros2_compat_install_python() (python3 shebang), from jsk-ros-pkg/jsk_common#1832, as a ROS2-only buildtool_depend (>= 3.0.2) that stays off rosidl's build dependencies.
- PyDrive (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), which gdrive_server_node.py runs with. This also avoids a pip rosdep key in package.xml, which bloom can not release. pyOpenSSL is in the venv too, since oauth2client imports it when present and the system one does not match the venv's cryptography.
- gdrive_server_node.py / sample_gdrive_rospy_client.py: main with ros_compat.init_node()/spin(); UploadResponse/MultipleUploadResponse
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| google_chat_ros |
Launch files
- launch/gdrive_server.launch
-
- machine [default: localhost]
- settings_yaml [default: $(optenv GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
- sample/sample_roseus_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- sample/sample_rospy_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- launch/gdrive_server.launch.xml
-
- settings_yaml [default: $(env GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
Messages
Services
Plugins
Recent questions tagged gdrive_ros at Robotics Stack Exchange
|
gdrive_ros package from jsk_3rdparty repovoicevox zdepth chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools nfc_ros respeaker_ros ros_speech_recognition rospatlite rosping sesame_ros switchbot_ros zdepth_image_transport |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-18 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Shingo Kitagawa
Authors
- Shingo Kitagawa
gdrive_ros
Google Drive file uploader for ROS: a server node which uploads local files to Google Drive (with PyDrive) on a service call and returns their URLs, and Python / EusLisp clients. The same script runs on ROS 1 and ROS 2.
Requirements
- A Google account and an OAuth 2.0 client of the Google Drive API: follow steps 1-5 of the
PyDrive quickstart (create a project in the
Google Cloud console, enable the Google Drive API, create an OAuth client ID and download it as
client_secrets.json). - A PyDrive settings yaml (format), for example:
client_config_file: /your/client/secrets/json/path
save_credentials: True
save_credentials_backend: file
save_credentials_file: /your/credentials/json/path
get_refresh_token: True
oauth_scope:
- https://www.googleapis.com/auth/drive.file
A relative client_config_file / save_credentials_file which is not found is looked up relative to the directory
of the settings yaml.
- At the first start the node runs PyDrive’s
LocalWebserverAuth(): it opens a web browser to log in to the Google account, so run it once on a machine with a browser. Withsave_credentials: Truethe token is saved tosave_credentials_fileand later starts need no login. - Python dependencies: PyDrive is not available from apt. On ROS 1 it is installed into a virtualenv by
catkin_virtualenv(requirements.txt); on ROS 2 into a uv venv (share/gdrive_ros/venv) frompyproject.toml/uv.lockat build time (jsk_ros1_ros2_compat_generate_uv_venv()). Runuv lockafter changingpyproject.toml.
Usage
ROS 2
ros2 launch gdrive_ros gdrive_server.launch.xml settings_yaml:=/your/settings/yaml/path
ros2 service call /gdrive_server/upload gdrive_ros/srv/Upload \
"{file_path: /tmp/test.txt, parents_path: example_folder}"
ros2 service call /gdrive_server/upload_multi gdrive_ros/srv/MultipleUpload \
"{file_paths: [/tmp/a.txt, /tmp/b.txt], file_titles: [a.txt, b.txt], use_timestamp_folder: true}"
The sample client uploads one file with both services:
ros2 run gdrive_ros sample_gdrive_rospy_client.py --ros-args \
-p file_name:=/tmp/test.txt -p file_title:=test.txt -p parents_path:=/example_folder
ROS 1
export GOOGLE_DRIVE_SETTINGS_YAML=/your/settings/yaml/path
roslaunch gdrive_ros gdrive_server.launch
rosservice call /gdrive_server/upload "{file_path: /tmp/test.txt, parents_path: example_folder}"
Samples, which start the server and upload a file with the Python or the EusLisp client:
roslaunch gdrive_ros sample_rospy_client.launch file_name:=/tmp/test.txt file_title:=test.txt
roslaunch gdrive_ros sample_roseus_client.launch file_name:=/tmp/test.txt file_title:=test.txt
Launch arguments
launch/gdrive_server.launch (ROS 1) and launch/gdrive_server.launch.xml (ROS 2):
| Argument | Default | Description |
|---|---|---|
settings_yaml |
$GOOGLE_DRIVE_SETTINGS_YAML, or /var/lib/robot/pydrive_settings.yaml
|
The PyDrive settings yaml |
respawn |
false |
Respawn the node |
node_name |
gdrive_server |
The node name (and so the namespace of the services) |
machine |
localhost |
ROS 1 only: the machine to run the node |
Clients
- Python:
gdrive_ros.gdrive_ros_client.GDriveROSClient(node)withwait_for_gdrive_server(),upload_file()andupload_multiple_files()(ROS 1 and ROS 2; seenode_scripts/sample_gdrive_rospy_client.py). - EusLisp (ROS 1):
euslisp/gdrive-ros-utils.lwithwait-for-gdrive-server,upload-fileandupload-multiple-files(seeeuslisp/sample-gdrive-roseus-client.l).
Both call /gdrive_server/upload and /gdrive_server/upload_multi, i.e. the server with the default node_name.
Interface
gdrive_server_node.py
Services
-
~upload(gdrive_ros/Upload): upload a file. -
~upload_multi(gdrive_ros/MultipleUpload): upload files into one folder.
File truncated at 100 lines see the full file
Changelog for package gdrive_ros
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[gdrive_ros] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the gdrive_ros python package, so gdrive_ros_client.py is installed into it. The installed ROS2 copies of the node scripts get a python3 shebang.
- package.xml: format 3 for conditions. catkin_virtualenv has no ROS2 port, so ROS2 gets PyDrive from the pydrive-pip rosdep key.
- gdrive_server_node.py, sample_gdrive_rospy_client.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only). ~upload and ~upload_multi keep their /gdrive_server/... names on ROS2.
- gdrive_ros_client.py: GDriveROSClient takes an optional rclpy node; on ROS2 it calls the services through ros_compat.call_service(). The ROS1 code path is unchanged.
- launch/gdrive_server.launch.xml: ROS2 version of gdrive_server.launch.
sample/*.launchand the euslisp client stay ROS1-only.- The ROS2 scripts are installed with jsk_ros1_ros2_compat's jsk_ros1_ros2_compat_install_python() (python3 shebang), from jsk-ros-pkg/jsk_common#1832, as a ROS2-only buildtool_depend (>= 3.0.2) that stays off rosidl's build dependencies.
- PyDrive (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), which gdrive_server_node.py runs with. This also avoids a pip rosdep key in package.xml, which bloom can not release. pyOpenSSL is in the venv too, since oauth2client imports it when present and the system one does not match the venv's cryptography.
- gdrive_server_node.py / sample_gdrive_rospy_client.py: main with ros_compat.init_node()/spin(); UploadResponse/MultipleUploadResponse
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| google_chat_ros |
Launch files
- launch/gdrive_server.launch
-
- machine [default: localhost]
- settings_yaml [default: $(optenv GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
- sample/sample_roseus_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- sample/sample_rospy_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- launch/gdrive_server.launch.xml
-
- settings_yaml [default: $(env GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
Messages
Services
Plugins
Recent questions tagged gdrive_ros at Robotics Stack Exchange
|
gdrive_ros package from jsk_3rdparty repovoicevox zdepth chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools nfc_ros respeaker_ros ros_speech_recognition rospatlite rosping sesame_ros switchbot_ros zdepth_image_transport |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-18 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Shingo Kitagawa
Authors
- Shingo Kitagawa
gdrive_ros
Google Drive file uploader for ROS: a server node which uploads local files to Google Drive (with PyDrive) on a service call and returns their URLs, and Python / EusLisp clients. The same script runs on ROS 1 and ROS 2.
Requirements
- A Google account and an OAuth 2.0 client of the Google Drive API: follow steps 1-5 of the
PyDrive quickstart (create a project in the
Google Cloud console, enable the Google Drive API, create an OAuth client ID and download it as
client_secrets.json). - A PyDrive settings yaml (format), for example:
client_config_file: /your/client/secrets/json/path
save_credentials: True
save_credentials_backend: file
save_credentials_file: /your/credentials/json/path
get_refresh_token: True
oauth_scope:
- https://www.googleapis.com/auth/drive.file
A relative client_config_file / save_credentials_file which is not found is looked up relative to the directory
of the settings yaml.
- At the first start the node runs PyDrive’s
LocalWebserverAuth(): it opens a web browser to log in to the Google account, so run it once on a machine with a browser. Withsave_credentials: Truethe token is saved tosave_credentials_fileand later starts need no login. - Python dependencies: PyDrive is not available from apt. On ROS 1 it is installed into a virtualenv by
catkin_virtualenv(requirements.txt); on ROS 2 into a uv venv (share/gdrive_ros/venv) frompyproject.toml/uv.lockat build time (jsk_ros1_ros2_compat_generate_uv_venv()). Runuv lockafter changingpyproject.toml.
Usage
ROS 2
ros2 launch gdrive_ros gdrive_server.launch.xml settings_yaml:=/your/settings/yaml/path
ros2 service call /gdrive_server/upload gdrive_ros/srv/Upload \
"{file_path: /tmp/test.txt, parents_path: example_folder}"
ros2 service call /gdrive_server/upload_multi gdrive_ros/srv/MultipleUpload \
"{file_paths: [/tmp/a.txt, /tmp/b.txt], file_titles: [a.txt, b.txt], use_timestamp_folder: true}"
The sample client uploads one file with both services:
ros2 run gdrive_ros sample_gdrive_rospy_client.py --ros-args \
-p file_name:=/tmp/test.txt -p file_title:=test.txt -p parents_path:=/example_folder
ROS 1
export GOOGLE_DRIVE_SETTINGS_YAML=/your/settings/yaml/path
roslaunch gdrive_ros gdrive_server.launch
rosservice call /gdrive_server/upload "{file_path: /tmp/test.txt, parents_path: example_folder}"
Samples, which start the server and upload a file with the Python or the EusLisp client:
roslaunch gdrive_ros sample_rospy_client.launch file_name:=/tmp/test.txt file_title:=test.txt
roslaunch gdrive_ros sample_roseus_client.launch file_name:=/tmp/test.txt file_title:=test.txt
Launch arguments
launch/gdrive_server.launch (ROS 1) and launch/gdrive_server.launch.xml (ROS 2):
| Argument | Default | Description |
|---|---|---|
settings_yaml |
$GOOGLE_DRIVE_SETTINGS_YAML, or /var/lib/robot/pydrive_settings.yaml
|
The PyDrive settings yaml |
respawn |
false |
Respawn the node |
node_name |
gdrive_server |
The node name (and so the namespace of the services) |
machine |
localhost |
ROS 1 only: the machine to run the node |
Clients
- Python:
gdrive_ros.gdrive_ros_client.GDriveROSClient(node)withwait_for_gdrive_server(),upload_file()andupload_multiple_files()(ROS 1 and ROS 2; seenode_scripts/sample_gdrive_rospy_client.py). - EusLisp (ROS 1):
euslisp/gdrive-ros-utils.lwithwait-for-gdrive-server,upload-fileandupload-multiple-files(seeeuslisp/sample-gdrive-roseus-client.l).
Both call /gdrive_server/upload and /gdrive_server/upload_multi, i.e. the server with the default node_name.
Interface
gdrive_server_node.py
Services
-
~upload(gdrive_ros/Upload): upload a file. -
~upload_multi(gdrive_ros/MultipleUpload): upload files into one folder.
File truncated at 100 lines see the full file
Changelog for package gdrive_ros
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[gdrive_ros] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the gdrive_ros python package, so gdrive_ros_client.py is installed into it. The installed ROS2 copies of the node scripts get a python3 shebang.
- package.xml: format 3 for conditions. catkin_virtualenv has no ROS2 port, so ROS2 gets PyDrive from the pydrive-pip rosdep key.
- gdrive_server_node.py, sample_gdrive_rospy_client.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only). ~upload and ~upload_multi keep their /gdrive_server/... names on ROS2.
- gdrive_ros_client.py: GDriveROSClient takes an optional rclpy node; on ROS2 it calls the services through ros_compat.call_service(). The ROS1 code path is unchanged.
- launch/gdrive_server.launch.xml: ROS2 version of gdrive_server.launch.
sample/*.launchand the euslisp client stay ROS1-only.- The ROS2 scripts are installed with jsk_ros1_ros2_compat's jsk_ros1_ros2_compat_install_python() (python3 shebang), from jsk-ros-pkg/jsk_common#1832, as a ROS2-only buildtool_depend (>= 3.0.2) that stays off rosidl's build dependencies.
- PyDrive (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), which gdrive_server_node.py runs with. This also avoids a pip rosdep key in package.xml, which bloom can not release. pyOpenSSL is in the venv too, since oauth2client imports it when present and the system one does not match the venv's cryptography.
- gdrive_server_node.py / sample_gdrive_rospy_client.py: main with ros_compat.init_node()/spin(); UploadResponse/MultipleUploadResponse
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| google_chat_ros |
Launch files
- launch/gdrive_server.launch
-
- machine [default: localhost]
- settings_yaml [default: $(optenv GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
- sample/sample_roseus_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- sample/sample_rospy_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- launch/gdrive_server.launch.xml
-
- settings_yaml [default: $(env GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
Messages
Services
Plugins
Recent questions tagged gdrive_ros at Robotics Stack Exchange
|
gdrive_ros package from jsk_3rdparty repovoicevox zdepth chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools nfc_ros respeaker_ros ros_speech_recognition rospatlite rosping sesame_ros switchbot_ros zdepth_image_transport |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-18 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Shingo Kitagawa
Authors
- Shingo Kitagawa
gdrive_ros
Google Drive file uploader for ROS: a server node which uploads local files to Google Drive (with PyDrive) on a service call and returns their URLs, and Python / EusLisp clients. The same script runs on ROS 1 and ROS 2.
Requirements
- A Google account and an OAuth 2.0 client of the Google Drive API: follow steps 1-5 of the
PyDrive quickstart (create a project in the
Google Cloud console, enable the Google Drive API, create an OAuth client ID and download it as
client_secrets.json). - A PyDrive settings yaml (format), for example:
client_config_file: /your/client/secrets/json/path
save_credentials: True
save_credentials_backend: file
save_credentials_file: /your/credentials/json/path
get_refresh_token: True
oauth_scope:
- https://www.googleapis.com/auth/drive.file
A relative client_config_file / save_credentials_file which is not found is looked up relative to the directory
of the settings yaml.
- At the first start the node runs PyDrive’s
LocalWebserverAuth(): it opens a web browser to log in to the Google account, so run it once on a machine with a browser. Withsave_credentials: Truethe token is saved tosave_credentials_fileand later starts need no login. - Python dependencies: PyDrive is not available from apt. On ROS 1 it is installed into a virtualenv by
catkin_virtualenv(requirements.txt); on ROS 2 into a uv venv (share/gdrive_ros/venv) frompyproject.toml/uv.lockat build time (jsk_ros1_ros2_compat_generate_uv_venv()). Runuv lockafter changingpyproject.toml.
Usage
ROS 2
ros2 launch gdrive_ros gdrive_server.launch.xml settings_yaml:=/your/settings/yaml/path
ros2 service call /gdrive_server/upload gdrive_ros/srv/Upload \
"{file_path: /tmp/test.txt, parents_path: example_folder}"
ros2 service call /gdrive_server/upload_multi gdrive_ros/srv/MultipleUpload \
"{file_paths: [/tmp/a.txt, /tmp/b.txt], file_titles: [a.txt, b.txt], use_timestamp_folder: true}"
The sample client uploads one file with both services:
ros2 run gdrive_ros sample_gdrive_rospy_client.py --ros-args \
-p file_name:=/tmp/test.txt -p file_title:=test.txt -p parents_path:=/example_folder
ROS 1
export GOOGLE_DRIVE_SETTINGS_YAML=/your/settings/yaml/path
roslaunch gdrive_ros gdrive_server.launch
rosservice call /gdrive_server/upload "{file_path: /tmp/test.txt, parents_path: example_folder}"
Samples, which start the server and upload a file with the Python or the EusLisp client:
roslaunch gdrive_ros sample_rospy_client.launch file_name:=/tmp/test.txt file_title:=test.txt
roslaunch gdrive_ros sample_roseus_client.launch file_name:=/tmp/test.txt file_title:=test.txt
Launch arguments
launch/gdrive_server.launch (ROS 1) and launch/gdrive_server.launch.xml (ROS 2):
| Argument | Default | Description |
|---|---|---|
settings_yaml |
$GOOGLE_DRIVE_SETTINGS_YAML, or /var/lib/robot/pydrive_settings.yaml
|
The PyDrive settings yaml |
respawn |
false |
Respawn the node |
node_name |
gdrive_server |
The node name (and so the namespace of the services) |
machine |
localhost |
ROS 1 only: the machine to run the node |
Clients
- Python:
gdrive_ros.gdrive_ros_client.GDriveROSClient(node)withwait_for_gdrive_server(),upload_file()andupload_multiple_files()(ROS 1 and ROS 2; seenode_scripts/sample_gdrive_rospy_client.py). - EusLisp (ROS 1):
euslisp/gdrive-ros-utils.lwithwait-for-gdrive-server,upload-fileandupload-multiple-files(seeeuslisp/sample-gdrive-roseus-client.l).
Both call /gdrive_server/upload and /gdrive_server/upload_multi, i.e. the server with the default node_name.
Interface
gdrive_server_node.py
Services
-
~upload(gdrive_ros/Upload): upload a file. -
~upload_multi(gdrive_ros/MultipleUpload): upload files into one folder.
File truncated at 100 lines see the full file
Changelog for package gdrive_ros
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[gdrive_ros] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the gdrive_ros python package, so gdrive_ros_client.py is installed into it. The installed ROS2 copies of the node scripts get a python3 shebang.
- package.xml: format 3 for conditions. catkin_virtualenv has no ROS2 port, so ROS2 gets PyDrive from the pydrive-pip rosdep key.
- gdrive_server_node.py, sample_gdrive_rospy_client.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only). ~upload and ~upload_multi keep their /gdrive_server/... names on ROS2.
- gdrive_ros_client.py: GDriveROSClient takes an optional rclpy node; on ROS2 it calls the services through ros_compat.call_service(). The ROS1 code path is unchanged.
- launch/gdrive_server.launch.xml: ROS2 version of gdrive_server.launch.
sample/*.launchand the euslisp client stay ROS1-only.- The ROS2 scripts are installed with jsk_ros1_ros2_compat's jsk_ros1_ros2_compat_install_python() (python3 shebang), from jsk-ros-pkg/jsk_common#1832, as a ROS2-only buildtool_depend (>= 3.0.2) that stays off rosidl's build dependencies.
- PyDrive (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), which gdrive_server_node.py runs with. This also avoids a pip rosdep key in package.xml, which bloom can not release. pyOpenSSL is in the venv too, since oauth2client imports it when present and the system one does not match the venv's cryptography.
- gdrive_server_node.py / sample_gdrive_rospy_client.py: main with ros_compat.init_node()/spin(); UploadResponse/MultipleUploadResponse
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| google_chat_ros |
Launch files
- launch/gdrive_server.launch
-
- machine [default: localhost]
- settings_yaml [default: $(optenv GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
- sample/sample_roseus_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- sample/sample_rospy_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- launch/gdrive_server.launch.xml
-
- settings_yaml [default: $(env GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
Messages
Services
Plugins
Recent questions tagged gdrive_ros at Robotics Stack Exchange
|
gdrive_ros package from jsk_3rdparty repovoicevox zdepth chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools nfc_ros respeaker_ros ros_speech_recognition rospatlite rosping sesame_ros switchbot_ros zdepth_image_transport |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-18 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Shingo Kitagawa
Authors
- Shingo Kitagawa
gdrive_ros
Google Drive file uploader for ROS: a server node which uploads local files to Google Drive (with PyDrive) on a service call and returns their URLs, and Python / EusLisp clients. The same script runs on ROS 1 and ROS 2.
Requirements
- A Google account and an OAuth 2.0 client of the Google Drive API: follow steps 1-5 of the
PyDrive quickstart (create a project in the
Google Cloud console, enable the Google Drive API, create an OAuth client ID and download it as
client_secrets.json). - A PyDrive settings yaml (format), for example:
client_config_file: /your/client/secrets/json/path
save_credentials: True
save_credentials_backend: file
save_credentials_file: /your/credentials/json/path
get_refresh_token: True
oauth_scope:
- https://www.googleapis.com/auth/drive.file
A relative client_config_file / save_credentials_file which is not found is looked up relative to the directory
of the settings yaml.
- At the first start the node runs PyDrive’s
LocalWebserverAuth(): it opens a web browser to log in to the Google account, so run it once on a machine with a browser. Withsave_credentials: Truethe token is saved tosave_credentials_fileand later starts need no login. - Python dependencies: PyDrive is not available from apt. On ROS 1 it is installed into a virtualenv by
catkin_virtualenv(requirements.txt); on ROS 2 into a uv venv (share/gdrive_ros/venv) frompyproject.toml/uv.lockat build time (jsk_ros1_ros2_compat_generate_uv_venv()). Runuv lockafter changingpyproject.toml.
Usage
ROS 2
ros2 launch gdrive_ros gdrive_server.launch.xml settings_yaml:=/your/settings/yaml/path
ros2 service call /gdrive_server/upload gdrive_ros/srv/Upload \
"{file_path: /tmp/test.txt, parents_path: example_folder}"
ros2 service call /gdrive_server/upload_multi gdrive_ros/srv/MultipleUpload \
"{file_paths: [/tmp/a.txt, /tmp/b.txt], file_titles: [a.txt, b.txt], use_timestamp_folder: true}"
The sample client uploads one file with both services:
ros2 run gdrive_ros sample_gdrive_rospy_client.py --ros-args \
-p file_name:=/tmp/test.txt -p file_title:=test.txt -p parents_path:=/example_folder
ROS 1
export GOOGLE_DRIVE_SETTINGS_YAML=/your/settings/yaml/path
roslaunch gdrive_ros gdrive_server.launch
rosservice call /gdrive_server/upload "{file_path: /tmp/test.txt, parents_path: example_folder}"
Samples, which start the server and upload a file with the Python or the EusLisp client:
roslaunch gdrive_ros sample_rospy_client.launch file_name:=/tmp/test.txt file_title:=test.txt
roslaunch gdrive_ros sample_roseus_client.launch file_name:=/tmp/test.txt file_title:=test.txt
Launch arguments
launch/gdrive_server.launch (ROS 1) and launch/gdrive_server.launch.xml (ROS 2):
| Argument | Default | Description |
|---|---|---|
settings_yaml |
$GOOGLE_DRIVE_SETTINGS_YAML, or /var/lib/robot/pydrive_settings.yaml
|
The PyDrive settings yaml |
respawn |
false |
Respawn the node |
node_name |
gdrive_server |
The node name (and so the namespace of the services) |
machine |
localhost |
ROS 1 only: the machine to run the node |
Clients
- Python:
gdrive_ros.gdrive_ros_client.GDriveROSClient(node)withwait_for_gdrive_server(),upload_file()andupload_multiple_files()(ROS 1 and ROS 2; seenode_scripts/sample_gdrive_rospy_client.py). - EusLisp (ROS 1):
euslisp/gdrive-ros-utils.lwithwait-for-gdrive-server,upload-fileandupload-multiple-files(seeeuslisp/sample-gdrive-roseus-client.l).
Both call /gdrive_server/upload and /gdrive_server/upload_multi, i.e. the server with the default node_name.
Interface
gdrive_server_node.py
Services
-
~upload(gdrive_ros/Upload): upload a file. -
~upload_multi(gdrive_ros/MultipleUpload): upload files into one folder.
File truncated at 100 lines see the full file
Changelog for package gdrive_ros
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[gdrive_ros] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the gdrive_ros python package, so gdrive_ros_client.py is installed into it. The installed ROS2 copies of the node scripts get a python3 shebang.
- package.xml: format 3 for conditions. catkin_virtualenv has no ROS2 port, so ROS2 gets PyDrive from the pydrive-pip rosdep key.
- gdrive_server_node.py, sample_gdrive_rospy_client.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only). ~upload and ~upload_multi keep their /gdrive_server/... names on ROS2.
- gdrive_ros_client.py: GDriveROSClient takes an optional rclpy node; on ROS2 it calls the services through ros_compat.call_service(). The ROS1 code path is unchanged.
- launch/gdrive_server.launch.xml: ROS2 version of gdrive_server.launch.
sample/*.launchand the euslisp client stay ROS1-only.- The ROS2 scripts are installed with jsk_ros1_ros2_compat's jsk_ros1_ros2_compat_install_python() (python3 shebang), from jsk-ros-pkg/jsk_common#1832, as a ROS2-only buildtool_depend (>= 3.0.2) that stays off rosidl's build dependencies.
- PyDrive (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), which gdrive_server_node.py runs with. This also avoids a pip rosdep key in package.xml, which bloom can not release. pyOpenSSL is in the venv too, since oauth2client imports it when present and the system one does not match the venv's cryptography.
- gdrive_server_node.py / sample_gdrive_rospy_client.py: main with ros_compat.init_node()/spin(); UploadResponse/MultipleUploadResponse
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| google_chat_ros |
Launch files
- launch/gdrive_server.launch
-
- machine [default: localhost]
- settings_yaml [default: $(optenv GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
- sample/sample_roseus_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- sample/sample_rospy_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- launch/gdrive_server.launch.xml
-
- settings_yaml [default: $(env GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
Messages
Services
Plugins
Recent questions tagged gdrive_ros at Robotics Stack Exchange
|
gdrive_ros package from jsk_3rdparty repovoicevox zdepth chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools nfc_ros respeaker_ros ros_speech_recognition rospatlite rosping sesame_ros switchbot_ros zdepth_image_transport |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-18 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Shingo Kitagawa
Authors
- Shingo Kitagawa
gdrive_ros
Google Drive file uploader for ROS: a server node which uploads local files to Google Drive (with PyDrive) on a service call and returns their URLs, and Python / EusLisp clients. The same script runs on ROS 1 and ROS 2.
Requirements
- A Google account and an OAuth 2.0 client of the Google Drive API: follow steps 1-5 of the
PyDrive quickstart (create a project in the
Google Cloud console, enable the Google Drive API, create an OAuth client ID and download it as
client_secrets.json). - A PyDrive settings yaml (format), for example:
client_config_file: /your/client/secrets/json/path
save_credentials: True
save_credentials_backend: file
save_credentials_file: /your/credentials/json/path
get_refresh_token: True
oauth_scope:
- https://www.googleapis.com/auth/drive.file
A relative client_config_file / save_credentials_file which is not found is looked up relative to the directory
of the settings yaml.
- At the first start the node runs PyDrive’s
LocalWebserverAuth(): it opens a web browser to log in to the Google account, so run it once on a machine with a browser. Withsave_credentials: Truethe token is saved tosave_credentials_fileand later starts need no login. - Python dependencies: PyDrive is not available from apt. On ROS 1 it is installed into a virtualenv by
catkin_virtualenv(requirements.txt); on ROS 2 into a uv venv (share/gdrive_ros/venv) frompyproject.toml/uv.lockat build time (jsk_ros1_ros2_compat_generate_uv_venv()). Runuv lockafter changingpyproject.toml.
Usage
ROS 2
ros2 launch gdrive_ros gdrive_server.launch.xml settings_yaml:=/your/settings/yaml/path
ros2 service call /gdrive_server/upload gdrive_ros/srv/Upload \
"{file_path: /tmp/test.txt, parents_path: example_folder}"
ros2 service call /gdrive_server/upload_multi gdrive_ros/srv/MultipleUpload \
"{file_paths: [/tmp/a.txt, /tmp/b.txt], file_titles: [a.txt, b.txt], use_timestamp_folder: true}"
The sample client uploads one file with both services:
ros2 run gdrive_ros sample_gdrive_rospy_client.py --ros-args \
-p file_name:=/tmp/test.txt -p file_title:=test.txt -p parents_path:=/example_folder
ROS 1
export GOOGLE_DRIVE_SETTINGS_YAML=/your/settings/yaml/path
roslaunch gdrive_ros gdrive_server.launch
rosservice call /gdrive_server/upload "{file_path: /tmp/test.txt, parents_path: example_folder}"
Samples, which start the server and upload a file with the Python or the EusLisp client:
roslaunch gdrive_ros sample_rospy_client.launch file_name:=/tmp/test.txt file_title:=test.txt
roslaunch gdrive_ros sample_roseus_client.launch file_name:=/tmp/test.txt file_title:=test.txt
Launch arguments
launch/gdrive_server.launch (ROS 1) and launch/gdrive_server.launch.xml (ROS 2):
| Argument | Default | Description |
|---|---|---|
settings_yaml |
$GOOGLE_DRIVE_SETTINGS_YAML, or /var/lib/robot/pydrive_settings.yaml
|
The PyDrive settings yaml |
respawn |
false |
Respawn the node |
node_name |
gdrive_server |
The node name (and so the namespace of the services) |
machine |
localhost |
ROS 1 only: the machine to run the node |
Clients
- Python:
gdrive_ros.gdrive_ros_client.GDriveROSClient(node)withwait_for_gdrive_server(),upload_file()andupload_multiple_files()(ROS 1 and ROS 2; seenode_scripts/sample_gdrive_rospy_client.py). - EusLisp (ROS 1):
euslisp/gdrive-ros-utils.lwithwait-for-gdrive-server,upload-fileandupload-multiple-files(seeeuslisp/sample-gdrive-roseus-client.l).
Both call /gdrive_server/upload and /gdrive_server/upload_multi, i.e. the server with the default node_name.
Interface
gdrive_server_node.py
Services
-
~upload(gdrive_ros/Upload): upload a file. -
~upload_multi(gdrive_ros/MultipleUpload): upload files into one folder.
File truncated at 100 lines see the full file
Changelog for package gdrive_ros
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[gdrive_ros] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the gdrive_ros python package, so gdrive_ros_client.py is installed into it. The installed ROS2 copies of the node scripts get a python3 shebang.
- package.xml: format 3 for conditions. catkin_virtualenv has no ROS2 port, so ROS2 gets PyDrive from the pydrive-pip rosdep key.
- gdrive_server_node.py, sample_gdrive_rospy_client.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only). ~upload and ~upload_multi keep their /gdrive_server/... names on ROS2.
- gdrive_ros_client.py: GDriveROSClient takes an optional rclpy node; on ROS2 it calls the services through ros_compat.call_service(). The ROS1 code path is unchanged.
- launch/gdrive_server.launch.xml: ROS2 version of gdrive_server.launch.
sample/*.launchand the euslisp client stay ROS1-only.- The ROS2 scripts are installed with jsk_ros1_ros2_compat's jsk_ros1_ros2_compat_install_python() (python3 shebang), from jsk-ros-pkg/jsk_common#1832, as a ROS2-only buildtool_depend (>= 3.0.2) that stays off rosidl's build dependencies.
- PyDrive (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), which gdrive_server_node.py runs with. This also avoids a pip rosdep key in package.xml, which bloom can not release. pyOpenSSL is in the venv too, since oauth2client imports it when present and the system one does not match the venv's cryptography.
- gdrive_server_node.py / sample_gdrive_rospy_client.py: main with ros_compat.init_node()/spin(); UploadResponse/MultipleUploadResponse
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| google_chat_ros |
Launch files
- launch/gdrive_server.launch
-
- machine [default: localhost]
- settings_yaml [default: $(optenv GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
- sample/sample_roseus_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- sample/sample_rospy_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- launch/gdrive_server.launch.xml
-
- settings_yaml [default: $(env GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
Messages
Services
Plugins
Recent questions tagged gdrive_ros at Robotics Stack Exchange
|
gdrive_ros package from jsk_3rdparty repovoicevox zdepth chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools nfc_ros respeaker_ros ros_speech_recognition rospatlite rosping sesame_ros switchbot_ros zdepth_image_transport |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-18 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Shingo Kitagawa
Authors
- Shingo Kitagawa
gdrive_ros
Google Drive file uploader for ROS: a server node which uploads local files to Google Drive (with PyDrive) on a service call and returns their URLs, and Python / EusLisp clients. The same script runs on ROS 1 and ROS 2.
Requirements
- A Google account and an OAuth 2.0 client of the Google Drive API: follow steps 1-5 of the
PyDrive quickstart (create a project in the
Google Cloud console, enable the Google Drive API, create an OAuth client ID and download it as
client_secrets.json). - A PyDrive settings yaml (format), for example:
client_config_file: /your/client/secrets/json/path
save_credentials: True
save_credentials_backend: file
save_credentials_file: /your/credentials/json/path
get_refresh_token: True
oauth_scope:
- https://www.googleapis.com/auth/drive.file
A relative client_config_file / save_credentials_file which is not found is looked up relative to the directory
of the settings yaml.
- At the first start the node runs PyDrive’s
LocalWebserverAuth(): it opens a web browser to log in to the Google account, so run it once on a machine with a browser. Withsave_credentials: Truethe token is saved tosave_credentials_fileand later starts need no login. - Python dependencies: PyDrive is not available from apt. On ROS 1 it is installed into a virtualenv by
catkin_virtualenv(requirements.txt); on ROS 2 into a uv venv (share/gdrive_ros/venv) frompyproject.toml/uv.lockat build time (jsk_ros1_ros2_compat_generate_uv_venv()). Runuv lockafter changingpyproject.toml.
Usage
ROS 2
ros2 launch gdrive_ros gdrive_server.launch.xml settings_yaml:=/your/settings/yaml/path
ros2 service call /gdrive_server/upload gdrive_ros/srv/Upload \
"{file_path: /tmp/test.txt, parents_path: example_folder}"
ros2 service call /gdrive_server/upload_multi gdrive_ros/srv/MultipleUpload \
"{file_paths: [/tmp/a.txt, /tmp/b.txt], file_titles: [a.txt, b.txt], use_timestamp_folder: true}"
The sample client uploads one file with both services:
ros2 run gdrive_ros sample_gdrive_rospy_client.py --ros-args \
-p file_name:=/tmp/test.txt -p file_title:=test.txt -p parents_path:=/example_folder
ROS 1
export GOOGLE_DRIVE_SETTINGS_YAML=/your/settings/yaml/path
roslaunch gdrive_ros gdrive_server.launch
rosservice call /gdrive_server/upload "{file_path: /tmp/test.txt, parents_path: example_folder}"
Samples, which start the server and upload a file with the Python or the EusLisp client:
roslaunch gdrive_ros sample_rospy_client.launch file_name:=/tmp/test.txt file_title:=test.txt
roslaunch gdrive_ros sample_roseus_client.launch file_name:=/tmp/test.txt file_title:=test.txt
Launch arguments
launch/gdrive_server.launch (ROS 1) and launch/gdrive_server.launch.xml (ROS 2):
| Argument | Default | Description |
|---|---|---|
settings_yaml |
$GOOGLE_DRIVE_SETTINGS_YAML, or /var/lib/robot/pydrive_settings.yaml
|
The PyDrive settings yaml |
respawn |
false |
Respawn the node |
node_name |
gdrive_server |
The node name (and so the namespace of the services) |
machine |
localhost |
ROS 1 only: the machine to run the node |
Clients
- Python:
gdrive_ros.gdrive_ros_client.GDriveROSClient(node)withwait_for_gdrive_server(),upload_file()andupload_multiple_files()(ROS 1 and ROS 2; seenode_scripts/sample_gdrive_rospy_client.py). - EusLisp (ROS 1):
euslisp/gdrive-ros-utils.lwithwait-for-gdrive-server,upload-fileandupload-multiple-files(seeeuslisp/sample-gdrive-roseus-client.l).
Both call /gdrive_server/upload and /gdrive_server/upload_multi, i.e. the server with the default node_name.
Interface
gdrive_server_node.py
Services
-
~upload(gdrive_ros/Upload): upload a file. -
~upload_multi(gdrive_ros/MultipleUpload): upload files into one folder.
File truncated at 100 lines see the full file
Changelog for package gdrive_ros
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[gdrive_ros] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the gdrive_ros python package, so gdrive_ros_client.py is installed into it. The installed ROS2 copies of the node scripts get a python3 shebang.
- package.xml: format 3 for conditions. catkin_virtualenv has no ROS2 port, so ROS2 gets PyDrive from the pydrive-pip rosdep key.
- gdrive_server_node.py, sample_gdrive_rospy_client.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only). ~upload and ~upload_multi keep their /gdrive_server/... names on ROS2.
- gdrive_ros_client.py: GDriveROSClient takes an optional rclpy node; on ROS2 it calls the services through ros_compat.call_service(). The ROS1 code path is unchanged.
- launch/gdrive_server.launch.xml: ROS2 version of gdrive_server.launch.
sample/*.launchand the euslisp client stay ROS1-only.- The ROS2 scripts are installed with jsk_ros1_ros2_compat's jsk_ros1_ros2_compat_install_python() (python3 shebang), from jsk-ros-pkg/jsk_common#1832, as a ROS2-only buildtool_depend (>= 3.0.2) that stays off rosidl's build dependencies.
- PyDrive (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), which gdrive_server_node.py runs with. This also avoids a pip rosdep key in package.xml, which bloom can not release. pyOpenSSL is in the venv too, since oauth2client imports it when present and the system one does not match the venv's cryptography.
- gdrive_server_node.py / sample_gdrive_rospy_client.py: main with ros_compat.init_node()/spin(); UploadResponse/MultipleUploadResponse
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| google_chat_ros |
Launch files
- launch/gdrive_server.launch
-
- machine [default: localhost]
- settings_yaml [default: $(optenv GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
- sample/sample_roseus_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- sample/sample_rospy_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- launch/gdrive_server.launch.xml
-
- settings_yaml [default: $(env GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
Messages
Services
Plugins
Recent questions tagged gdrive_ros at Robotics Stack Exchange
|
gdrive_ros package from jsk_3rdparty repovoicevox zdepth chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools nfc_ros respeaker_ros ros_speech_recognition rospatlite rosping sesame_ros switchbot_ros zdepth_image_transport |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-18 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Shingo Kitagawa
Authors
- Shingo Kitagawa
gdrive_ros
Google Drive file uploader for ROS: a server node which uploads local files to Google Drive (with PyDrive) on a service call and returns their URLs, and Python / EusLisp clients. The same script runs on ROS 1 and ROS 2.
Requirements
- A Google account and an OAuth 2.0 client of the Google Drive API: follow steps 1-5 of the
PyDrive quickstart (create a project in the
Google Cloud console, enable the Google Drive API, create an OAuth client ID and download it as
client_secrets.json). - A PyDrive settings yaml (format), for example:
client_config_file: /your/client/secrets/json/path
save_credentials: True
save_credentials_backend: file
save_credentials_file: /your/credentials/json/path
get_refresh_token: True
oauth_scope:
- https://www.googleapis.com/auth/drive.file
A relative client_config_file / save_credentials_file which is not found is looked up relative to the directory
of the settings yaml.
- At the first start the node runs PyDrive’s
LocalWebserverAuth(): it opens a web browser to log in to the Google account, so run it once on a machine with a browser. Withsave_credentials: Truethe token is saved tosave_credentials_fileand later starts need no login. - Python dependencies: PyDrive is not available from apt. On ROS 1 it is installed into a virtualenv by
catkin_virtualenv(requirements.txt); on ROS 2 into a uv venv (share/gdrive_ros/venv) frompyproject.toml/uv.lockat build time (jsk_ros1_ros2_compat_generate_uv_venv()). Runuv lockafter changingpyproject.toml.
Usage
ROS 2
ros2 launch gdrive_ros gdrive_server.launch.xml settings_yaml:=/your/settings/yaml/path
ros2 service call /gdrive_server/upload gdrive_ros/srv/Upload \
"{file_path: /tmp/test.txt, parents_path: example_folder}"
ros2 service call /gdrive_server/upload_multi gdrive_ros/srv/MultipleUpload \
"{file_paths: [/tmp/a.txt, /tmp/b.txt], file_titles: [a.txt, b.txt], use_timestamp_folder: true}"
The sample client uploads one file with both services:
ros2 run gdrive_ros sample_gdrive_rospy_client.py --ros-args \
-p file_name:=/tmp/test.txt -p file_title:=test.txt -p parents_path:=/example_folder
ROS 1
export GOOGLE_DRIVE_SETTINGS_YAML=/your/settings/yaml/path
roslaunch gdrive_ros gdrive_server.launch
rosservice call /gdrive_server/upload "{file_path: /tmp/test.txt, parents_path: example_folder}"
Samples, which start the server and upload a file with the Python or the EusLisp client:
roslaunch gdrive_ros sample_rospy_client.launch file_name:=/tmp/test.txt file_title:=test.txt
roslaunch gdrive_ros sample_roseus_client.launch file_name:=/tmp/test.txt file_title:=test.txt
Launch arguments
launch/gdrive_server.launch (ROS 1) and launch/gdrive_server.launch.xml (ROS 2):
| Argument | Default | Description |
|---|---|---|
settings_yaml |
$GOOGLE_DRIVE_SETTINGS_YAML, or /var/lib/robot/pydrive_settings.yaml
|
The PyDrive settings yaml |
respawn |
false |
Respawn the node |
node_name |
gdrive_server |
The node name (and so the namespace of the services) |
machine |
localhost |
ROS 1 only: the machine to run the node |
Clients
- Python:
gdrive_ros.gdrive_ros_client.GDriveROSClient(node)withwait_for_gdrive_server(),upload_file()andupload_multiple_files()(ROS 1 and ROS 2; seenode_scripts/sample_gdrive_rospy_client.py). - EusLisp (ROS 1):
euslisp/gdrive-ros-utils.lwithwait-for-gdrive-server,upload-fileandupload-multiple-files(seeeuslisp/sample-gdrive-roseus-client.l).
Both call /gdrive_server/upload and /gdrive_server/upload_multi, i.e. the server with the default node_name.
Interface
gdrive_server_node.py
Services
-
~upload(gdrive_ros/Upload): upload a file. -
~upload_multi(gdrive_ros/MultipleUpload): upload files into one folder.
File truncated at 100 lines see the full file
Changelog for package gdrive_ros
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[gdrive_ros] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the gdrive_ros python package, so gdrive_ros_client.py is installed into it. The installed ROS2 copies of the node scripts get a python3 shebang.
- package.xml: format 3 for conditions. catkin_virtualenv has no ROS2 port, so ROS2 gets PyDrive from the pydrive-pip rosdep key.
- gdrive_server_node.py, sample_gdrive_rospy_client.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only). ~upload and ~upload_multi keep their /gdrive_server/... names on ROS2.
- gdrive_ros_client.py: GDriveROSClient takes an optional rclpy node; on ROS2 it calls the services through ros_compat.call_service(). The ROS1 code path is unchanged.
- launch/gdrive_server.launch.xml: ROS2 version of gdrive_server.launch.
sample/*.launchand the euslisp client stay ROS1-only.- The ROS2 scripts are installed with jsk_ros1_ros2_compat's jsk_ros1_ros2_compat_install_python() (python3 shebang), from jsk-ros-pkg/jsk_common#1832, as a ROS2-only buildtool_depend (>= 3.0.2) that stays off rosidl's build dependencies.
- PyDrive (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), which gdrive_server_node.py runs with. This also avoids a pip rosdep key in package.xml, which bloom can not release. pyOpenSSL is in the venv too, since oauth2client imports it when present and the system one does not match the venv's cryptography.
- gdrive_server_node.py / sample_gdrive_rospy_client.py: main with ros_compat.init_node()/spin(); UploadResponse/MultipleUploadResponse
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| google_chat_ros |
Launch files
- launch/gdrive_server.launch
-
- machine [default: localhost]
- settings_yaml [default: $(optenv GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
- sample/sample_roseus_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- sample/sample_rospy_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- launch/gdrive_server.launch.xml
-
- settings_yaml [default: $(env GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
Messages
Services
Plugins
Recent questions tagged gdrive_ros at Robotics Stack Exchange
|
gdrive_ros package from jsk_3rdparty repovoicevox zdepth chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools nfc_ros respeaker_ros ros_speech_recognition rospatlite rosping sesame_ros switchbot_ros zdepth_image_transport |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-18 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Shingo Kitagawa
Authors
- Shingo Kitagawa
gdrive_ros
Google Drive file uploader for ROS: a server node which uploads local files to Google Drive (with PyDrive) on a service call and returns their URLs, and Python / EusLisp clients. The same script runs on ROS 1 and ROS 2.
Requirements
- A Google account and an OAuth 2.0 client of the Google Drive API: follow steps 1-5 of the
PyDrive quickstart (create a project in the
Google Cloud console, enable the Google Drive API, create an OAuth client ID and download it as
client_secrets.json). - A PyDrive settings yaml (format), for example:
client_config_file: /your/client/secrets/json/path
save_credentials: True
save_credentials_backend: file
save_credentials_file: /your/credentials/json/path
get_refresh_token: True
oauth_scope:
- https://www.googleapis.com/auth/drive.file
A relative client_config_file / save_credentials_file which is not found is looked up relative to the directory
of the settings yaml.
- At the first start the node runs PyDrive’s
LocalWebserverAuth(): it opens a web browser to log in to the Google account, so run it once on a machine with a browser. Withsave_credentials: Truethe token is saved tosave_credentials_fileand later starts need no login. - Python dependencies: PyDrive is not available from apt. On ROS 1 it is installed into a virtualenv by
catkin_virtualenv(requirements.txt); on ROS 2 into a uv venv (share/gdrive_ros/venv) frompyproject.toml/uv.lockat build time (jsk_ros1_ros2_compat_generate_uv_venv()). Runuv lockafter changingpyproject.toml.
Usage
ROS 2
ros2 launch gdrive_ros gdrive_server.launch.xml settings_yaml:=/your/settings/yaml/path
ros2 service call /gdrive_server/upload gdrive_ros/srv/Upload \
"{file_path: /tmp/test.txt, parents_path: example_folder}"
ros2 service call /gdrive_server/upload_multi gdrive_ros/srv/MultipleUpload \
"{file_paths: [/tmp/a.txt, /tmp/b.txt], file_titles: [a.txt, b.txt], use_timestamp_folder: true}"
The sample client uploads one file with both services:
ros2 run gdrive_ros sample_gdrive_rospy_client.py --ros-args \
-p file_name:=/tmp/test.txt -p file_title:=test.txt -p parents_path:=/example_folder
ROS 1
export GOOGLE_DRIVE_SETTINGS_YAML=/your/settings/yaml/path
roslaunch gdrive_ros gdrive_server.launch
rosservice call /gdrive_server/upload "{file_path: /tmp/test.txt, parents_path: example_folder}"
Samples, which start the server and upload a file with the Python or the EusLisp client:
roslaunch gdrive_ros sample_rospy_client.launch file_name:=/tmp/test.txt file_title:=test.txt
roslaunch gdrive_ros sample_roseus_client.launch file_name:=/tmp/test.txt file_title:=test.txt
Launch arguments
launch/gdrive_server.launch (ROS 1) and launch/gdrive_server.launch.xml (ROS 2):
| Argument | Default | Description |
|---|---|---|
settings_yaml |
$GOOGLE_DRIVE_SETTINGS_YAML, or /var/lib/robot/pydrive_settings.yaml
|
The PyDrive settings yaml |
respawn |
false |
Respawn the node |
node_name |
gdrive_server |
The node name (and so the namespace of the services) |
machine |
localhost |
ROS 1 only: the machine to run the node |
Clients
- Python:
gdrive_ros.gdrive_ros_client.GDriveROSClient(node)withwait_for_gdrive_server(),upload_file()andupload_multiple_files()(ROS 1 and ROS 2; seenode_scripts/sample_gdrive_rospy_client.py). - EusLisp (ROS 1):
euslisp/gdrive-ros-utils.lwithwait-for-gdrive-server,upload-fileandupload-multiple-files(seeeuslisp/sample-gdrive-roseus-client.l).
Both call /gdrive_server/upload and /gdrive_server/upload_multi, i.e. the server with the default node_name.
Interface
gdrive_server_node.py
Services
-
~upload(gdrive_ros/Upload): upload a file. -
~upload_multi(gdrive_ros/MultipleUpload): upload files into one folder.
File truncated at 100 lines see the full file
Changelog for package gdrive_ros
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[gdrive_ros] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the gdrive_ros python package, so gdrive_ros_client.py is installed into it. The installed ROS2 copies of the node scripts get a python3 shebang.
- package.xml: format 3 for conditions. catkin_virtualenv has no ROS2 port, so ROS2 gets PyDrive from the pydrive-pip rosdep key.
- gdrive_server_node.py, sample_gdrive_rospy_client.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only). ~upload and ~upload_multi keep their /gdrive_server/... names on ROS2.
- gdrive_ros_client.py: GDriveROSClient takes an optional rclpy node; on ROS2 it calls the services through ros_compat.call_service(). The ROS1 code path is unchanged.
- launch/gdrive_server.launch.xml: ROS2 version of gdrive_server.launch.
sample/*.launchand the euslisp client stay ROS1-only.- The ROS2 scripts are installed with jsk_ros1_ros2_compat's jsk_ros1_ros2_compat_install_python() (python3 shebang), from jsk-ros-pkg/jsk_common#1832, as a ROS2-only buildtool_depend (>= 3.0.2) that stays off rosidl's build dependencies.
- PyDrive (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), which gdrive_server_node.py runs with. This also avoids a pip rosdep key in package.xml, which bloom can not release. pyOpenSSL is in the venv too, since oauth2client imports it when present and the system one does not match the venv's cryptography.
- gdrive_server_node.py / sample_gdrive_rospy_client.py: main with ros_compat.init_node()/spin(); UploadResponse/MultipleUploadResponse
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| google_chat_ros |
Launch files
- launch/gdrive_server.launch
-
- machine [default: localhost]
- settings_yaml [default: $(optenv GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
- sample/sample_roseus_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- sample/sample_rospy_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- launch/gdrive_server.launch.xml
-
- settings_yaml [default: $(env GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
Messages
Services
Plugins
Recent questions tagged gdrive_ros at Robotics Stack Exchange
|
gdrive_ros package from jsk_3rdparty repovoicevox zdepth chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools nfc_ros respeaker_ros ros_speech_recognition rospatlite rosping sesame_ros switchbot_ros zdepth_image_transport |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-18 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Shingo Kitagawa
Authors
- Shingo Kitagawa
gdrive_ros
Google Drive file uploader for ROS: a server node which uploads local files to Google Drive (with PyDrive) on a service call and returns their URLs, and Python / EusLisp clients. The same script runs on ROS 1 and ROS 2.
Requirements
- A Google account and an OAuth 2.0 client of the Google Drive API: follow steps 1-5 of the
PyDrive quickstart (create a project in the
Google Cloud console, enable the Google Drive API, create an OAuth client ID and download it as
client_secrets.json). - A PyDrive settings yaml (format), for example:
client_config_file: /your/client/secrets/json/path
save_credentials: True
save_credentials_backend: file
save_credentials_file: /your/credentials/json/path
get_refresh_token: True
oauth_scope:
- https://www.googleapis.com/auth/drive.file
A relative client_config_file / save_credentials_file which is not found is looked up relative to the directory
of the settings yaml.
- At the first start the node runs PyDrive’s
LocalWebserverAuth(): it opens a web browser to log in to the Google account, so run it once on a machine with a browser. Withsave_credentials: Truethe token is saved tosave_credentials_fileand later starts need no login. - Python dependencies: PyDrive is not available from apt. On ROS 1 it is installed into a virtualenv by
catkin_virtualenv(requirements.txt); on ROS 2 into a uv venv (share/gdrive_ros/venv) frompyproject.toml/uv.lockat build time (jsk_ros1_ros2_compat_generate_uv_venv()). Runuv lockafter changingpyproject.toml.
Usage
ROS 2
ros2 launch gdrive_ros gdrive_server.launch.xml settings_yaml:=/your/settings/yaml/path
ros2 service call /gdrive_server/upload gdrive_ros/srv/Upload \
"{file_path: /tmp/test.txt, parents_path: example_folder}"
ros2 service call /gdrive_server/upload_multi gdrive_ros/srv/MultipleUpload \
"{file_paths: [/tmp/a.txt, /tmp/b.txt], file_titles: [a.txt, b.txt], use_timestamp_folder: true}"
The sample client uploads one file with both services:
ros2 run gdrive_ros sample_gdrive_rospy_client.py --ros-args \
-p file_name:=/tmp/test.txt -p file_title:=test.txt -p parents_path:=/example_folder
ROS 1
export GOOGLE_DRIVE_SETTINGS_YAML=/your/settings/yaml/path
roslaunch gdrive_ros gdrive_server.launch
rosservice call /gdrive_server/upload "{file_path: /tmp/test.txt, parents_path: example_folder}"
Samples, which start the server and upload a file with the Python or the EusLisp client:
roslaunch gdrive_ros sample_rospy_client.launch file_name:=/tmp/test.txt file_title:=test.txt
roslaunch gdrive_ros sample_roseus_client.launch file_name:=/tmp/test.txt file_title:=test.txt
Launch arguments
launch/gdrive_server.launch (ROS 1) and launch/gdrive_server.launch.xml (ROS 2):
| Argument | Default | Description |
|---|---|---|
settings_yaml |
$GOOGLE_DRIVE_SETTINGS_YAML, or /var/lib/robot/pydrive_settings.yaml
|
The PyDrive settings yaml |
respawn |
false |
Respawn the node |
node_name |
gdrive_server |
The node name (and so the namespace of the services) |
machine |
localhost |
ROS 1 only: the machine to run the node |
Clients
- Python:
gdrive_ros.gdrive_ros_client.GDriveROSClient(node)withwait_for_gdrive_server(),upload_file()andupload_multiple_files()(ROS 1 and ROS 2; seenode_scripts/sample_gdrive_rospy_client.py). - EusLisp (ROS 1):
euslisp/gdrive-ros-utils.lwithwait-for-gdrive-server,upload-fileandupload-multiple-files(seeeuslisp/sample-gdrive-roseus-client.l).
Both call /gdrive_server/upload and /gdrive_server/upload_multi, i.e. the server with the default node_name.
Interface
gdrive_server_node.py
Services
-
~upload(gdrive_ros/Upload): upload a file. -
~upload_multi(gdrive_ros/MultipleUpload): upload files into one folder.
File truncated at 100 lines see the full file
Changelog for package gdrive_ros
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[gdrive_ros] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the gdrive_ros python package, so gdrive_ros_client.py is installed into it. The installed ROS2 copies of the node scripts get a python3 shebang.
- package.xml: format 3 for conditions. catkin_virtualenv has no ROS2 port, so ROS2 gets PyDrive from the pydrive-pip rosdep key.
- gdrive_server_node.py, sample_gdrive_rospy_client.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only). ~upload and ~upload_multi keep their /gdrive_server/... names on ROS2.
- gdrive_ros_client.py: GDriveROSClient takes an optional rclpy node; on ROS2 it calls the services through ros_compat.call_service(). The ROS1 code path is unchanged.
- launch/gdrive_server.launch.xml: ROS2 version of gdrive_server.launch.
sample/*.launchand the euslisp client stay ROS1-only.- The ROS2 scripts are installed with jsk_ros1_ros2_compat's jsk_ros1_ros2_compat_install_python() (python3 shebang), from jsk-ros-pkg/jsk_common#1832, as a ROS2-only buildtool_depend (>= 3.0.2) that stays off rosidl's build dependencies.
- PyDrive (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), which gdrive_server_node.py runs with. This also avoids a pip rosdep key in package.xml, which bloom can not release. pyOpenSSL is in the venv too, since oauth2client imports it when present and the system one does not match the venv's cryptography.
- gdrive_server_node.py / sample_gdrive_rospy_client.py: main with ros_compat.init_node()/spin(); UploadResponse/MultipleUploadResponse
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| google_chat_ros |
Launch files
- launch/gdrive_server.launch
-
- machine [default: localhost]
- settings_yaml [default: $(optenv GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
- sample/sample_roseus_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- sample/sample_rospy_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- launch/gdrive_server.launch.xml
-
- settings_yaml [default: $(env GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
Messages
Services
Plugins
Recent questions tagged gdrive_ros at Robotics Stack Exchange
|
gdrive_ros package from jsk_3rdparty repovoicevox zdepth chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools nfc_ros respeaker_ros ros_speech_recognition rospatlite rosping sesame_ros switchbot_ros zdepth_image_transport |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-18 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Shingo Kitagawa
Authors
- Shingo Kitagawa
gdrive_ros
Google Drive file uploader for ROS: a server node which uploads local files to Google Drive (with PyDrive) on a service call and returns their URLs, and Python / EusLisp clients. The same script runs on ROS 1 and ROS 2.
Requirements
- A Google account and an OAuth 2.0 client of the Google Drive API: follow steps 1-5 of the
PyDrive quickstart (create a project in the
Google Cloud console, enable the Google Drive API, create an OAuth client ID and download it as
client_secrets.json). - A PyDrive settings yaml (format), for example:
client_config_file: /your/client/secrets/json/path
save_credentials: True
save_credentials_backend: file
save_credentials_file: /your/credentials/json/path
get_refresh_token: True
oauth_scope:
- https://www.googleapis.com/auth/drive.file
A relative client_config_file / save_credentials_file which is not found is looked up relative to the directory
of the settings yaml.
- At the first start the node runs PyDrive’s
LocalWebserverAuth(): it opens a web browser to log in to the Google account, so run it once on a machine with a browser. Withsave_credentials: Truethe token is saved tosave_credentials_fileand later starts need no login. - Python dependencies: PyDrive is not available from apt. On ROS 1 it is installed into a virtualenv by
catkin_virtualenv(requirements.txt); on ROS 2 into a uv venv (share/gdrive_ros/venv) frompyproject.toml/uv.lockat build time (jsk_ros1_ros2_compat_generate_uv_venv()). Runuv lockafter changingpyproject.toml.
Usage
ROS 2
ros2 launch gdrive_ros gdrive_server.launch.xml settings_yaml:=/your/settings/yaml/path
ros2 service call /gdrive_server/upload gdrive_ros/srv/Upload \
"{file_path: /tmp/test.txt, parents_path: example_folder}"
ros2 service call /gdrive_server/upload_multi gdrive_ros/srv/MultipleUpload \
"{file_paths: [/tmp/a.txt, /tmp/b.txt], file_titles: [a.txt, b.txt], use_timestamp_folder: true}"
The sample client uploads one file with both services:
ros2 run gdrive_ros sample_gdrive_rospy_client.py --ros-args \
-p file_name:=/tmp/test.txt -p file_title:=test.txt -p parents_path:=/example_folder
ROS 1
export GOOGLE_DRIVE_SETTINGS_YAML=/your/settings/yaml/path
roslaunch gdrive_ros gdrive_server.launch
rosservice call /gdrive_server/upload "{file_path: /tmp/test.txt, parents_path: example_folder}"
Samples, which start the server and upload a file with the Python or the EusLisp client:
roslaunch gdrive_ros sample_rospy_client.launch file_name:=/tmp/test.txt file_title:=test.txt
roslaunch gdrive_ros sample_roseus_client.launch file_name:=/tmp/test.txt file_title:=test.txt
Launch arguments
launch/gdrive_server.launch (ROS 1) and launch/gdrive_server.launch.xml (ROS 2):
| Argument | Default | Description |
|---|---|---|
settings_yaml |
$GOOGLE_DRIVE_SETTINGS_YAML, or /var/lib/robot/pydrive_settings.yaml
|
The PyDrive settings yaml |
respawn |
false |
Respawn the node |
node_name |
gdrive_server |
The node name (and so the namespace of the services) |
machine |
localhost |
ROS 1 only: the machine to run the node |
Clients
- Python:
gdrive_ros.gdrive_ros_client.GDriveROSClient(node)withwait_for_gdrive_server(),upload_file()andupload_multiple_files()(ROS 1 and ROS 2; seenode_scripts/sample_gdrive_rospy_client.py). - EusLisp (ROS 1):
euslisp/gdrive-ros-utils.lwithwait-for-gdrive-server,upload-fileandupload-multiple-files(seeeuslisp/sample-gdrive-roseus-client.l).
Both call /gdrive_server/upload and /gdrive_server/upload_multi, i.e. the server with the default node_name.
Interface
gdrive_server_node.py
Services
-
~upload(gdrive_ros/Upload): upload a file. -
~upload_multi(gdrive_ros/MultipleUpload): upload files into one folder.
File truncated at 100 lines see the full file
Changelog for package gdrive_ros
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[gdrive_ros] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the gdrive_ros python package, so gdrive_ros_client.py is installed into it. The installed ROS2 copies of the node scripts get a python3 shebang.
- package.xml: format 3 for conditions. catkin_virtualenv has no ROS2 port, so ROS2 gets PyDrive from the pydrive-pip rosdep key.
- gdrive_server_node.py, sample_gdrive_rospy_client.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only). ~upload and ~upload_multi keep their /gdrive_server/... names on ROS2.
- gdrive_ros_client.py: GDriveROSClient takes an optional rclpy node; on ROS2 it calls the services through ros_compat.call_service(). The ROS1 code path is unchanged.
- launch/gdrive_server.launch.xml: ROS2 version of gdrive_server.launch.
sample/*.launchand the euslisp client stay ROS1-only.- The ROS2 scripts are installed with jsk_ros1_ros2_compat's jsk_ros1_ros2_compat_install_python() (python3 shebang), from jsk-ros-pkg/jsk_common#1832, as a ROS2-only buildtool_depend (>= 3.0.2) that stays off rosidl's build dependencies.
- PyDrive (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), which gdrive_server_node.py runs with. This also avoids a pip rosdep key in package.xml, which bloom can not release. pyOpenSSL is in the venv too, since oauth2client imports it when present and the system one does not match the venv's cryptography.
- gdrive_server_node.py / sample_gdrive_rospy_client.py: main with ros_compat.init_node()/spin(); UploadResponse/MultipleUploadResponse
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| google_chat_ros |
Launch files
- launch/gdrive_server.launch
-
- machine [default: localhost]
- settings_yaml [default: $(optenv GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
- sample/sample_roseus_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- sample/sample_rospy_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- launch/gdrive_server.launch.xml
-
- settings_yaml [default: $(env GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
Messages
Services
Plugins
Recent questions tagged gdrive_ros at Robotics Stack Exchange
|
gdrive_ros package from jsk_3rdparty repovoicevox zdepth chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools nfc_ros respeaker_ros ros_speech_recognition rospatlite rosping sesame_ros switchbot_ros zdepth_image_transport |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-18 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Shingo Kitagawa
Authors
- Shingo Kitagawa
gdrive_ros
Google Drive file uploader for ROS: a server node which uploads local files to Google Drive (with PyDrive) on a service call and returns their URLs, and Python / EusLisp clients. The same script runs on ROS 1 and ROS 2.
Requirements
- A Google account and an OAuth 2.0 client of the Google Drive API: follow steps 1-5 of the
PyDrive quickstart (create a project in the
Google Cloud console, enable the Google Drive API, create an OAuth client ID and download it as
client_secrets.json). - A PyDrive settings yaml (format), for example:
client_config_file: /your/client/secrets/json/path
save_credentials: True
save_credentials_backend: file
save_credentials_file: /your/credentials/json/path
get_refresh_token: True
oauth_scope:
- https://www.googleapis.com/auth/drive.file
A relative client_config_file / save_credentials_file which is not found is looked up relative to the directory
of the settings yaml.
- At the first start the node runs PyDrive’s
LocalWebserverAuth(): it opens a web browser to log in to the Google account, so run it once on a machine with a browser. Withsave_credentials: Truethe token is saved tosave_credentials_fileand later starts need no login. - Python dependencies: PyDrive is not available from apt. On ROS 1 it is installed into a virtualenv by
catkin_virtualenv(requirements.txt); on ROS 2 into a uv venv (share/gdrive_ros/venv) frompyproject.toml/uv.lockat build time (jsk_ros1_ros2_compat_generate_uv_venv()). Runuv lockafter changingpyproject.toml.
Usage
ROS 2
ros2 launch gdrive_ros gdrive_server.launch.xml settings_yaml:=/your/settings/yaml/path
ros2 service call /gdrive_server/upload gdrive_ros/srv/Upload \
"{file_path: /tmp/test.txt, parents_path: example_folder}"
ros2 service call /gdrive_server/upload_multi gdrive_ros/srv/MultipleUpload \
"{file_paths: [/tmp/a.txt, /tmp/b.txt], file_titles: [a.txt, b.txt], use_timestamp_folder: true}"
The sample client uploads one file with both services:
ros2 run gdrive_ros sample_gdrive_rospy_client.py --ros-args \
-p file_name:=/tmp/test.txt -p file_title:=test.txt -p parents_path:=/example_folder
ROS 1
export GOOGLE_DRIVE_SETTINGS_YAML=/your/settings/yaml/path
roslaunch gdrive_ros gdrive_server.launch
rosservice call /gdrive_server/upload "{file_path: /tmp/test.txt, parents_path: example_folder}"
Samples, which start the server and upload a file with the Python or the EusLisp client:
roslaunch gdrive_ros sample_rospy_client.launch file_name:=/tmp/test.txt file_title:=test.txt
roslaunch gdrive_ros sample_roseus_client.launch file_name:=/tmp/test.txt file_title:=test.txt
Launch arguments
launch/gdrive_server.launch (ROS 1) and launch/gdrive_server.launch.xml (ROS 2):
| Argument | Default | Description |
|---|---|---|
settings_yaml |
$GOOGLE_DRIVE_SETTINGS_YAML, or /var/lib/robot/pydrive_settings.yaml
|
The PyDrive settings yaml |
respawn |
false |
Respawn the node |
node_name |
gdrive_server |
The node name (and so the namespace of the services) |
machine |
localhost |
ROS 1 only: the machine to run the node |
Clients
- Python:
gdrive_ros.gdrive_ros_client.GDriveROSClient(node)withwait_for_gdrive_server(),upload_file()andupload_multiple_files()(ROS 1 and ROS 2; seenode_scripts/sample_gdrive_rospy_client.py). - EusLisp (ROS 1):
euslisp/gdrive-ros-utils.lwithwait-for-gdrive-server,upload-fileandupload-multiple-files(seeeuslisp/sample-gdrive-roseus-client.l).
Both call /gdrive_server/upload and /gdrive_server/upload_multi, i.e. the server with the default node_name.
Interface
gdrive_server_node.py
Services
-
~upload(gdrive_ros/Upload): upload a file. -
~upload_multi(gdrive_ros/MultipleUpload): upload files into one folder.
File truncated at 100 lines see the full file
Changelog for package gdrive_ros
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[gdrive_ros] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the gdrive_ros python package, so gdrive_ros_client.py is installed into it. The installed ROS2 copies of the node scripts get a python3 shebang.
- package.xml: format 3 for conditions. catkin_virtualenv has no ROS2 port, so ROS2 gets PyDrive from the pydrive-pip rosdep key.
- gdrive_server_node.py, sample_gdrive_rospy_client.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only). ~upload and ~upload_multi keep their /gdrive_server/... names on ROS2.
- gdrive_ros_client.py: GDriveROSClient takes an optional rclpy node; on ROS2 it calls the services through ros_compat.call_service(). The ROS1 code path is unchanged.
- launch/gdrive_server.launch.xml: ROS2 version of gdrive_server.launch.
sample/*.launchand the euslisp client stay ROS1-only.- The ROS2 scripts are installed with jsk_ros1_ros2_compat's jsk_ros1_ros2_compat_install_python() (python3 shebang), from jsk-ros-pkg/jsk_common#1832, as a ROS2-only buildtool_depend (>= 3.0.2) that stays off rosidl's build dependencies.
- PyDrive (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), which gdrive_server_node.py runs with. This also avoids a pip rosdep key in package.xml, which bloom can not release. pyOpenSSL is in the venv too, since oauth2client imports it when present and the system one does not match the venv's cryptography.
- gdrive_server_node.py / sample_gdrive_rospy_client.py: main with ros_compat.init_node()/spin(); UploadResponse/MultipleUploadResponse
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| google_chat_ros |
Launch files
- launch/gdrive_server.launch
-
- machine [default: localhost]
- settings_yaml [default: $(optenv GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
- sample/sample_roseus_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- sample/sample_rospy_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- launch/gdrive_server.launch.xml
-
- settings_yaml [default: $(env GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
Messages
Services
Plugins
Recent questions tagged gdrive_ros at Robotics Stack Exchange
|
gdrive_ros package from jsk_3rdparty repovoicevox zdepth chaplus_ros emotion_analyzer gdrive_ros google_chat_ros influxdb_store jsk_power_switching_tools nfc_ros respeaker_ros ros_speech_recognition rospatlite rosping sesame_ros switchbot_ros zdepth_image_transport |
ROS Distro
|
Package Summary
| Version | 3.0.1 |
| License | BSD-3-Clause |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/jsk-ros-pkg/jsk_3rdparty.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2026-11-18 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Shingo Kitagawa
Authors
- Shingo Kitagawa
gdrive_ros
Google Drive file uploader for ROS: a server node which uploads local files to Google Drive (with PyDrive) on a service call and returns their URLs, and Python / EusLisp clients. The same script runs on ROS 1 and ROS 2.
Requirements
- A Google account and an OAuth 2.0 client of the Google Drive API: follow steps 1-5 of the
PyDrive quickstart (create a project in the
Google Cloud console, enable the Google Drive API, create an OAuth client ID and download it as
client_secrets.json). - A PyDrive settings yaml (format), for example:
client_config_file: /your/client/secrets/json/path
save_credentials: True
save_credentials_backend: file
save_credentials_file: /your/credentials/json/path
get_refresh_token: True
oauth_scope:
- https://www.googleapis.com/auth/drive.file
A relative client_config_file / save_credentials_file which is not found is looked up relative to the directory
of the settings yaml.
- At the first start the node runs PyDrive’s
LocalWebserverAuth(): it opens a web browser to log in to the Google account, so run it once on a machine with a browser. Withsave_credentials: Truethe token is saved tosave_credentials_fileand later starts need no login. - Python dependencies: PyDrive is not available from apt. On ROS 1 it is installed into a virtualenv by
catkin_virtualenv(requirements.txt); on ROS 2 into a uv venv (share/gdrive_ros/venv) frompyproject.toml/uv.lockat build time (jsk_ros1_ros2_compat_generate_uv_venv()). Runuv lockafter changingpyproject.toml.
Usage
ROS 2
ros2 launch gdrive_ros gdrive_server.launch.xml settings_yaml:=/your/settings/yaml/path
ros2 service call /gdrive_server/upload gdrive_ros/srv/Upload \
"{file_path: /tmp/test.txt, parents_path: example_folder}"
ros2 service call /gdrive_server/upload_multi gdrive_ros/srv/MultipleUpload \
"{file_paths: [/tmp/a.txt, /tmp/b.txt], file_titles: [a.txt, b.txt], use_timestamp_folder: true}"
The sample client uploads one file with both services:
ros2 run gdrive_ros sample_gdrive_rospy_client.py --ros-args \
-p file_name:=/tmp/test.txt -p file_title:=test.txt -p parents_path:=/example_folder
ROS 1
export GOOGLE_DRIVE_SETTINGS_YAML=/your/settings/yaml/path
roslaunch gdrive_ros gdrive_server.launch
rosservice call /gdrive_server/upload "{file_path: /tmp/test.txt, parents_path: example_folder}"
Samples, which start the server and upload a file with the Python or the EusLisp client:
roslaunch gdrive_ros sample_rospy_client.launch file_name:=/tmp/test.txt file_title:=test.txt
roslaunch gdrive_ros sample_roseus_client.launch file_name:=/tmp/test.txt file_title:=test.txt
Launch arguments
launch/gdrive_server.launch (ROS 1) and launch/gdrive_server.launch.xml (ROS 2):
| Argument | Default | Description |
|---|---|---|
settings_yaml |
$GOOGLE_DRIVE_SETTINGS_YAML, or /var/lib/robot/pydrive_settings.yaml
|
The PyDrive settings yaml |
respawn |
false |
Respawn the node |
node_name |
gdrive_server |
The node name (and so the namespace of the services) |
machine |
localhost |
ROS 1 only: the machine to run the node |
Clients
- Python:
gdrive_ros.gdrive_ros_client.GDriveROSClient(node)withwait_for_gdrive_server(),upload_file()andupload_multiple_files()(ROS 1 and ROS 2; seenode_scripts/sample_gdrive_rospy_client.py). - EusLisp (ROS 1):
euslisp/gdrive-ros-utils.lwithwait-for-gdrive-server,upload-fileandupload-multiple-files(seeeuslisp/sample-gdrive-roseus-client.l).
Both call /gdrive_server/upload and /gdrive_server/upload_multi, i.e. the server with the default node_name.
Interface
gdrive_server_node.py
Services
-
~upload(gdrive_ros/Upload): upload a file. -
~upload_multi(gdrive_ros/MultipleUpload): upload files into one folder.
File truncated at 100 lines see the full file
Changelog for package gdrive_ros
3.0.1 (2026-11-10)
- Merge pull request #583 from k-okada/rosdistro-55247-review rosdistro#55247 review: rename power_switching_tools_ros to jsk_power_switching_tools, fix licenses
- use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and Apache / "Apache License, Version 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55247 review). The LICENSE files of all of them are BSD 3-Clause and Apache 2.0 respectively. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
- Contributors: Kei Okada
3.0.0 (2026-11-06)
-
Merge pull request #581 from k-okada/ros2-buildfarm-ros-environment Fix ROS2 buildfarm binary jobs: ros_environment, bundled flac, numpy wheel
-
[voicevox, chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, ros_speech_recognition, rospatlite, sesame_ros, switchbot_ros] depend on ros_environment for ROS2 buildfarm The buildfarm builds each package with only its own build dependencies, so without ros_environment $ROS_VERSION is empty and CMakeLists.txt takes the ROS1 branch (same as jsk_common#1835). voicevox also guesses ROS_VERSION from AMENT_PREFIX_PATH when it is unset. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into fix_hoya
-
Merge branch 'master' into voicevox-ros1-ros2
-
AMENT_IGNORE: do not add AMENT_IGNORE to packages already ported to ROS2 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros and switchbot_ros are already ROS2 packages on master, so this PR must not AMENT_IGNORE them. Also remove ros_speech_recognition/AMENT_IGNORE, as this PR ports it to ROS2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
Merge branch 'master' into ros2-speech-recognition-only
-
Merge pull request #575 from k-okada/ros2-support Add ROS2 (jazzy) support to chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, respeaker_ros, rospatlite, sesame_ros, switchbot_ros
-
AMENT_IGNORE packages ported to ROS2 in jsk-ros-pkg/jsk_3rdparty#575 chaplus_ros, emotion_analyzer, gdrive_ros, google_chat_ros, influxdb_store, power_switching_tools_ros, rospatlite, sesame_ros and switchbot_ros are ROS1 only here, so the ROS2 CI skips them until #575. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
-
[gdrive_ros] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, same as chaplus_ros and jsk_common's ROS2-ported packages.
- CMakeLists.txt: the ROS2 block is prepended and the ROS1 original is wrapped in else()/endif() unchanged. ROS2 generates the services with rosidl_generate_interfaces(), which already installs the gdrive_ros python package, so gdrive_ros_client.py is installed into it. The installed ROS2 copies of the node scripts get a python3 shebang.
- package.xml: format 3 for conditions. catkin_virtualenv has no ROS2 port, so ROS2 gets PyDrive from the pydrive-pip rosdep key.
- gdrive_server_node.py, sample_gdrive_rospy_client.py: use jsk_ros1_ros2_compat's rospy_rclpy_compat, falling back to rospy when it is not importable (jsk_common < 3.0, ROS1 only). ~upload and ~upload_multi keep their /gdrive_server/... names on ROS2.
- gdrive_ros_client.py: GDriveROSClient takes an optional rclpy node; on ROS2 it calls the services through ros_compat.call_service(). The ROS1 code path is unchanged.
- launch/gdrive_server.launch.xml: ROS2 version of gdrive_server.launch.
sample/*.launchand the euslisp client stay ROS1-only.- The ROS2 scripts are installed with jsk_ros1_ros2_compat's jsk_ros1_ros2_compat_install_python() (python3 shebang), from jsk-ros-pkg/jsk_common#1832, as a ROS2-only buildtool_depend (>= 3.0.2) that stays off rosidl's build dependencies.
- PyDrive (not in apt; catkin_virtualenv has no ROS2 port) is installed into a uv venv made from pyproject.toml/uv.lock at build time with jsk_ros1_ros2_compat_generate_uv_venv() (jsk-ros-pkg/jsk_common#1831), which gdrive_server_node.py runs with. This also avoids a pip rosdep key in package.xml, which bloom can not release. pyOpenSSL is in the venv too, since oauth2client imports it when present and the system one does not match the venv's cryptography.
- gdrive_server_node.py / sample_gdrive_rospy_client.py: main with ros_compat.init_node()/spin(); UploadResponse/MultipleUploadResponse
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
Dependant Packages
| Name | Deps |
|---|---|
| google_chat_ros |
Launch files
- launch/gdrive_server.launch
-
- machine [default: localhost]
- settings_yaml [default: $(optenv GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]
- sample/sample_roseus_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- sample/sample_rospy_client.launch
-
- file_name
- file_title
- parents_path [default: /example_folder]
- launch/gdrive_server.launch.xml
-
- settings_yaml [default: $(env GOOGLE_DRIVE_SETTINGS_YAML /var/lib/robot/pydrive_settings.yaml)]
- respawn [default: false]
- node_name [default: gdrive_server]