diff -r 89d6a7a84779 -r 25a17d01db0c Symbian3/PDK/Source/GUID-DF756D6C-1E03-4EC0-B074-09611D122359.dita --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/Symbian3/PDK/Source/GUID-DF756D6C-1E03-4EC0-B074-09611D122359.dita Fri Jan 22 18:26:19 2010 +0000 @@ -0,0 +1,105 @@ + + + + Storing +location information on a mobile device +

Location information may +be stored as database entries called landmarks that contain at least +a name and a location.

+

Typical use cases include:

+ + +

The SDK does not include a map API, and therefore you must use a third +party API to display the location information you receive on a map. Does this also apply to S60 5th Edition?

+
+
Saving location +information on a mobile device +

To store location information on your mobile device:

+
    +
  1. Make use of +the methods of the Landmarks API when constructing +your application.

    + +

    The CPosLandmarkDatabase class is used for accessing the database with the landmarks +information and the CPosLandmark class +contains the location information.

    +

    For detailed information on how to do this, see:

    +
      +
    • Using landmarks database for +a discussion of how to start accessing the database with the location information, +including a structure diagram.

    • +
    • Managing landmarks for +code samples of opening, editing, and adding location information to a database

      +
    • +
    • Listening to database events for +possible events type passed to your application and code samples for implementing +a listener

      + +

      The TPosLmEvent class +is used in listening for events.

      +
      +
    • +
    +
    +
  2. +
  3. Make sure eposlandmarks.lib is +accessible to your linker when compiling your application by including it +in your .mmp file or by editing the project properties in your IDE, depending +on your build environment.

  4. +
  5. Make sure +you have the correct capabilities information set for your application, depending +on your application you may need LocalServices, NetworkServices, ReadDeviceData, ReadUserData, WriteDeviceData, and WriteUserData.

    +
  6. +
+
+
Additional information +on storing location information +

For more information see, Question +for the reviewers: Is there anything else that we could add here?

+
    +
  • API description for a description +of the API and its class structure

  • +
  • Using the Landmarks API for a +general overview on how to create applications using the API

  • +
  • For a reference example on searching and manipulating the +information in the location database, see LocationLandmarksRefAppForS60 in +the SDK (<SDK installation directory>\S60CppExamples\)

    +
  • +
  • For a reference example on how to use common UI components +to work with landmark data, see LocationLandmarksUIRefApp in +the SDK (<SDK installation directory>\S60CppExamples\AutoAdaptedToTouchEx\)

    +
  • +
+
+
Related Symbian +APIs +

The Symbian platform also offers the following related +APIs:

+
    +
  • Landmarks API for accessing +the database

  • +
  • Landmarks Database +Management API for creating and deleting databases

  • +
  • Landmarks Search API for +allowing mobile devices users to search the database

  • +
  • Landmarks UI Add/Edit API for +allowing mobile device users to add and edit landmarks

  • +
  • Landmarks UI Selector API for +displaying and selecting landmarks

  • +
  • Location Acquisition API for +finding the location of a mobile device

  • +
  • Communication for +sending location information to other devices

  • +
+
+
\ No newline at end of file