---

landmark Class Reference

#include <landmark.h>

Public Member Functions
	landmark (void)
	set (string iname, pose &ipose)
string &	name (void)
pose &	position (void)
Protected Attributes
string	_name
short	_id
remote_command	_location

---

Detailed Description

current theory will attempt to have a HOST side which sets names and IDs for locations and keeps a landmark chain. embedded side will simply keep a list of locations with an ID. Generally, would not keep landmarks on embedded side, but would resolve landmark to location and simply download GOTO as waypoint--not landmark. If we may want to have learning of landmarks, then we need a primitive landmark storage capability onboard. Learn landmark by location--assign new ID; tranfser new landmark and ID to host where it is given a name and used.

---

Constructor & Destructor Documentation

landmark (  void   )

---

Member Function Documentation

string& name (  void   )

pose& position (  void   )

set (  string  iname, pose &  ipose )

---

Field Documentation

short _id [protected]

remote_command _location [protected]

string _name [protected]

---