@@ -23,11 +23,11 @@ navsat_transform_node:
2323 zero_altitude : false
2424
2525# If this is true, the transform world_frame->utm transform is broadcast for use by other nodes. Defaults to false.
26- broadcast_utm_transform : false
26+ broadcast_utm_transform : true
2727
2828# If this is true, the utm->world_frame transform will be published instead of the world_frame->utm transform.
2929# Note that broadcast_utm_transform still has to be enabled. Defaults to false.
30- broadcast_utm_transform_as_parent_frame : false
30+ broadcast_utm_transform_as_parent_frame : true
3131
3232# If this is true, all received odometry data is converted back to a lat/lon and published as a NavSatFix message as
3333# /gps/filtered. Defaults to false.
@@ -37,7 +37,7 @@ navsat_transform_node:
3737# /odometry/filtered topic coming from one of robot_localization's state estimation nodes). BE CAREFUL when using this!
3838# The yaw value in your odometry source *must* be world-referenced, e.g., you cannot use your odometry source for yaw
3939# if your yaw data is based purely on integrated velocities. Defaults to false.
40- use_odometry_yaw : false
40+ use_odometry_yaw : true
4141
4242# If true, will retrieve the datum from the 'datum' parameter below, if available. If no 'datum' parameter exists,
4343# navsat_transform_node will wait until the user calls the 'datum' service with the SetDatum service message.
@@ -47,5 +47,6 @@ navsat_transform_node:
4747# origin (datum) using this parameter. The fields in the parameter represent latitude and longitude in decimal degrees,
4848# and heading in radians. As navsat_transform_node assumes an ENU standard, a 0 heading corresponds to east.
4949# wait this might actually be usefully for translating over maps lol -AFB
50+ # NOTE WE
5051 datum : [55.944904, -3.186693, 0.0]
5152
0 commit comments