From 8ad427564044bfb4f3f6ae4c319f1475dc535ee5 Mon Sep 17 00:00:00 2001 From: Scott Main Date: Fri, 14 Feb 2014 18:37:24 -0800 Subject: [PATCH] update intent examples for maps bug: 12661490 bug: 12957723 Change-Id: Ice25ef430901b155c00d59402c5f9f50dcb48390 --- docs/html/guide/components/intents-common.jd | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/docs/html/guide/components/intents-common.jd b/docs/html/guide/components/intents-common.jd index f09ef9f1ea480..506cf9dbd4924 100644 --- a/docs/html/guide/components/intents-common.jd +++ b/docs/html/guide/components/intents-common.jd @@ -880,13 +880,17 @@ the location information in the intent data with one of the schemes defined belo (closest) zoom level is 23.

Example: "geo:47.6,-122.3?z=11" -

geo:0,0?q=lat,lng(label)
-
Show the map at the given longitude and latitude with a string label. -

Example: "geo:0,0?q=34.99,-106.61(Treasure)" -

+
geo:0,0?q=lat,lng(label)
+
Show the map at the given longitude and latitude with a string label. +

Example: "geo:0,0?q=34.99,-106.61(Treasure)" +

geo:0,0?q=my+street+address
Show the location for "my street address" (may be a specific address or location query). -

Example: "geo:0,0?q=1600+amphitheatre+parkway+ca" +

Example: "geo:0,0?q=1600+Amphitheatre+Parkway%2C+CA"

+

Note: All strings passed in the {@code geo} URI must + be encoded. For example, the string {@code 1st & Pike, Seattle} should become + {@code 1st%20%26%20Pike%2C%20Seattle}. Spaces in the string can be encoded with + {@code %20} or replaced with the plus sign ({@code +}).