From ee1807a0dd59a79f6670a27d45da8c3cba2063df Mon Sep 17 00:00:00 2001 From: Bastien Boutonnet Date: Sat, 27 Feb 2021 14:49:23 +0100 Subject: [PATCH] update readme --- README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index f5d96b344..9fa96b6f2 100644 --- a/README.md +++ b/README.md @@ -95,7 +95,7 @@ Usage: --- ### Date/Time #### date_spine ([source](macros/datetime/date_spine.sql)) -This macro returns the sql required to build a date spine. The spine will include the `start_date` (if it is aligned to the `datepart`), but it will not include the `end_date`. +This macro returns the sql required to build a date spine. The spine will include the `start_date` (if it is aligned to the `datepart`), but it will not include the `end_date`. Usage: ``` @@ -111,9 +111,11 @@ Usage: #### haversine_distance ([source](macros/geo/haversine_distance.sql)) This macro calculates the [haversine distance](http://daynebatten.com/2015/09/latitude-longitude-distance-sql/) between a pair of x/y coordinates. +Optionally takes a `unit` string parameter ('km' or 'mi') which defaults to miles (imperial system). + Usage: ``` -{{ dbt_utils.haversine_distance(lat1=,lon1=,lat2=,lon2=) }} +{{ dbt_utils.haversine_distance(lat1=,lon1=,lat2=,lon2=, unit='mi') }} ``` --- ### Schema Tests