Read parameter in launch file

edit

You can use <include> tag to add 2nd launch file in the first one.

That way you should be able to get folder path, and you can add a conditional argument (bool), if that is set to true it will launch the second launch. Your first launch file should be something like this.

<launch>
  <arg name="folder_path"    deafult="path"/>
  <arg name="launch_second" default="false"/>

  <include if="$(arg launch_second)" file="$(find package_name)/launch/second-launch.launch">
    <arg name="folderpath"  value="$(arg folder_path)"/>
  </include>
</launch>

and when launching the first launch file you can set launch_second to true like:

roslaunch package_name first_launch.launch launch_second:=true

• If the code of the node that starts as part of the 2nd roslaunch is your custom code, then reference to the ROS Parameter from the code, assuming the Parameter name can be statically defined, say folderpath.
• If the code is not your custom (I see in the OP that the node that starts in the 2nd launch is rosbag), then I'd say you'd have to add one new step before roslaunch executes e.g.

:

roslaunch 2nd.launch folderpath:=`rosparam get folderpath`

Either way, "1st laucnh" needs to start and sets the Parameter before 2nd one to start. Since roslaunch doesn't guarantee the order of nodes to start, you'd want to write a custom code to have a control over the timing to make your application robust.