am 19564c70: Merge "Adds the metadata to the Geofencing Sample" into lmp-docs
* commit '19564c70db1fbd670b2561ac38eceedc0e7efb3c':
Adds the metadata to the Geofencing Sample
diff --git a/wearable/wear/Geofencing/screenshots/icon-web.png b/wearable/wear/Geofencing/screenshots/icon-web.png
new file mode 100644
index 0000000..81c1008
--- /dev/null
+++ b/wearable/wear/Geofencing/screenshots/icon-web.png
Binary files differ
diff --git a/wearable/wear/Geofencing/template-params.xml b/wearable/wear/Geofencing/template-params.xml
index 8750397..5530b02 100644
--- a/wearable/wear/Geofencing/template-params.xml
+++ b/wearable/wear/Geofencing/template-params.xml
@@ -44,4 +44,53 @@
<template src="base"/>
<template src="Wear"/>
+ <metadata>
+ <status>PUBLISHED</status>
+ <categories>Wearable, Sensors</categories>
+ <technologies>Android</technologies>
+ <languages>Java</languages>
+ <solutions>Mobile</solutions>
+ <level>ADVANCED</level>
+ <icon>screenshots/icon-web.png</icon>
+ <screenshots>
+ <img>screenshots/android_building_check_in.png</img>
+ </screenshots>
+ <api_refs>
+ <android>com.google.android.gms.location.Geofence</android>
+ </api_refs>
+ <description>
+<![CDATA[
+When the user enters the vicinity of the Android building (B44) or the Yerba Buena
+Gardens near the Moscone center in San Francisco, a notification silently appears on their
+wearable with an option to check in. This notification automatically disappears when they leave
+the area, and reappears the next time they are at one of these locations.
+]]>
+ </description>
+ <intro>
+<![CDATA[
+Geofencing combines awareness of the user's current location with awareness of
+nearby features, defined as the user's proximity to locations that may be of
+interest. To mark a location of interest, you specify its latitude and longitude.
+To adjust the proximity for the location, you add a radius. The latitude,
+longitude, and radius define a geofence. You can have multiple active
+geofences at one time.
+
+To use geofencing, start by defining the geofences you want to monitor.
+Although you usually store geofence data in a local database or download
+it from the network, you need to send a geofence to Location Services as
+an instance of [Geofence][2], which you create with `Geofence.Builder`. Each
+Geofence object contains the following information:
+
+1. Latitude, longitude, and radius
+2. Expiration time
+3. Transition type
+4. Geofence ID
+
+Read more about geofences in [Creating and Monitoring Geofences][1].
+
+[1]:http://developer.android.com/training/location/geofencing.html
+[2]:http://developer.android.com/reference/com/google/android/gms/location/Geofence.html
+]]>
+ </intro>
+ </metadata>
</sample>
