From e0a390c6f37ea8bff1e48c7fb65a818ecfcbd8b5 Mon Sep 17 00:00:00 2001 From: Philipp Meisen Date: Wed, 12 Apr 2017 15:52:10 -0700 Subject: [PATCH] more docs --- .../snippets/language-request-temporal-data.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/documentation/snippets/language-request-temporal-data.md b/documentation/snippets/language-request-temporal-data.md index 78b171e..6faa273 100644 --- a/documentation/snippets/language-request-temporal-data.md +++ b/documentation/snippets/language-request-temporal-data.md @@ -3,6 +3,11 @@ of the temporalData method.

+
+

Using Latitude/Longitude

+

It is possible to pass in a latitude/longitude pair.

+
+ > ```javascript--node var latitude = 37.7749; @@ -12,6 +17,11 @@ Breinify.temporalData(latitude, longitude, function(data) { }); ``` +
+

Using IP-Address

+

Another possibility is to just pass in an ip-address and resolve the temporal information available.

+
+ > ```javascript--node var ipAddress = '72.229.28.185'; @@ -20,6 +30,13 @@ Breinify.temporalData(ipAddress, function(data) { }); ``` +
+

Using an Object

+

The most general solution is to pass in an object and specify the different known values +to determine what can be resolved (but also what should be returned), based on the provided data. +The further usage examples illustrate different possibilities.

+
+ > ```javascript--node // you can also pass in a more complex location object