Revision history [back]

When are planning to do planning from a parking spot to another in Autoware.Auto, the global planner expects to be planned from parking_spot -> parking_access -> lane -> parking_access -> parking_spot.

• parking_spot: The actual space to park, and Autoware.Auto will try to park at the center of this object. It is defined as lanelet2 Area objects(multipolygon in osm). It should have following tags: subtype=parking_spot, parking_accesses=<list of relevant parking access>. Autoware.Auto also assumes that the parking spot is rectangle shape with 5 points where first and last point overlap.
• Parking Access Areas: This is used to define free space between parking spot and its nearest lane. Parking planner will use the shape of parking_spot, parking_access, and lanelet to calculate trajectory. Parking Access Areas are defined as lanelet2 Area objects(multipolygon in osm). It should have following tags: subtype=parking_access, ref_lanelet=<id of the nearest lanelet>
• Lanelet: Lane objects to define lanes with right bounds and left bounds. See lanelet2 document for the details.

If you are familiar with c++, looking into the global_planner source code might help you get some idea.

What did I do wrong in the .osm file?

You have to add multipolygon relation to define parking_spots. You also have to define parking_access area as well. Although you don't have any "gaps" between lanelets and your parking spot, Autoware.Auto expects this object to find out the connection between lanelets and parking spots so you can perhaps create one that is overlapping with the parking_spot. Also, it seems like you are trying to drive through lanes, in that case, you might not need to define parking spots at all.

If you still don't see a map in RVIZ, I doubt there is something wrong with configuration of the origin when loading the map.