Forum Discussion
LAMBDA Examples: Distance between two cities
This post is the first of a series where we will be sharing out examples of lambdas. This is intended to highlight lambdas we have cooked up that show the power of this new super-charged function. Additionally, you have the opportunity to engage with us on the lambdas you have built yourself and of course let us know how our own formulas could be improved.
If you didn’t catch the announcement, be sure to check out the blog post highlighting the release of this new function, Announcing LAMBDA: Turn Excel formulas into custom functions
In today’s example we will be picking up where we left off in the announcement blog and making good on the promise of:
“a custom function that takes two cities as input and calculates the distance between them...” |
So let’s get to it!
Distance between two cities
The first thing to note is that this function will be making use of Excel Data Types. Data Types are useful here because of the ease at which we can retrieve latitude and longitude for a given entity through “dot notation”.
The next thing to cover is the mathematical formula which we will be encoding as an excel formula. We will be making use of the law of cosines which can give you an as the crow flies distance calculation.
This formula is a great one to encode as a lambda given its complexity which will make it more prone to formula-authoring errors. It also happens to re-use multiple inputs which makes it a great candidate for LET. In short, this is the type of function I would want to author once and store for re-use.
The equation looks like this:
While this might seem a bit daunting, the inputs we really care about are:
- Latitude and longitude of the start location
- Latitude and longitude of the end location
In the equation
- Δλ is the delta of the longitudes (_lon2 - _lon1)
- φ1 and φ2 represent _lon1 and _lon2 respectively
- r is equal to the radius of the sphere, in this case 6378 which is the radius of the earth in kilometers.
The last trick we employ in this example is to convert everything into radians which is where we make use of the LET function to do these transformations. This is important as the equation expects lat/long in radians and the Data Types return them in degrees.
This is illustrated in the first series of name definitions where we:
- Calculate the values in terms of radians for re-use
- Assign new names to differentiate between the input values (_lat1, _lon1, _lat2, _lon2) and transformed values (lat_1, lat_2, lon_1, lon_2)
Putting all those concepts together gives us the following solution for LATLONGDISTANCE which will be doing the heavy-lifting for the final formula that takes in cities and passes in their respective latitudes and longitudes to LATLONGDISTANCE.
=LATLONGDISTANCE
=LAMBDA(_lat1, _lon1, _lat2, _lon2, LET(
lat_1, RADIANS(_lat1),
lon_1, RADIANS(_lon1),
lat_2, RADIANS(_lat2),
lon_2, RADIANS(_lon2),
r, 6378,
ACOS(
(SIN(lat_1) * SIN(lat_2)) + (COS(lat_1) * COS(lat_2) * COS(lon_2-lon_1))
) * r
))
=ASTHECROWFLIES
The last piece of the puzzle is to create a lambda which will take two cities as inputs. You could encode all of this into the previous formula, but we like the composability of lambdas and figured it would be a great way to show lambdas calling one another.
Revisiting the previous comment, about extracting properties from data types, we will need to define something which takes two cities as inputs and then extracts the latitudes and longitudes.
For this we will make use of dot notation and LET.
=LAMBDA(city1, city2, LET(
lat_1, city1.Latitude,
lon_1, city1.Longitude,
lat_2, city2.Latitude,
lon_2, city2.Longitude,
))
With the values extracted and names defined, the last thing to do is define a calculation which we call distance that returns the value. You’ll notice we wrap this in an IFERROR to catch any errors which might result from passing in bad values.
=LAMBDA(city1, city2, LET(
lat_1, city1.Latitude,
lon_1, city1.Longitude,
lat_2, city2.Latitude,
lon_2, city2.Longitude,
distance, LATLONGDISTANCE(lat_1, lon_1, lat_2, lon_2),
IFERROR(distance, "an error occurred")
))
And that's it!
We hope you found this example useful and look forward to seeing what lambdas you have cooked up on your own.
Until next time!
Chris Gross,
Program Manager Excel
This is awesome! I'm loving it! LAMBDA functions will be a game changer for the Excel heavy users!
- FidaAliCopper Contributor
Chris_Gross Measuring distances amongst various locations/places on the Earth with the help of MS Office Excel formulas is really fascinating and awesomely great.
- NikolinoDEGold ContributorA nice thing, the world has become a little bit smaller for everyone
... with just three entries in Excel :)).
Nikolino
I know that I don't know (Socrates) - lori_mSteel Contributor
I had forgotten about this post but was led back here from Viz 's Fibonacci link above. Revisiting the methods described in previous comments I was pleased to find that it's now possible to define lambdas as addin functions that can be called from any open workbook.
Steps:
1. define lambdas in a new workbook
2. insert a macro sheet (ctrl+F11)
3. with the macro sheet selected, open name manager
4. edit name definitions clicking the Function option.
5. remove the macro sheet and save as addin (xlam).
6. open the addin and enter a test formula in a new workbookLambda definitions:
TIMEIT
=LET(t, timer(), LAMBDA(formula, timer() - t));
timer
=LAMBDA(ROUND(NOW()*24000*3600,0))Test Formula:
=TIMEIT(SUM(SEQUENCE(1000,1000))) -> ¬60 milliseconds.- Sameer_BhideIron ContributorThis is great !!! Thanks a lot for this lori_m - There is no autocomplete/parameter help - but we can live with that.
Cheers
Sam
- LAMBDA👍😃:bottle_with_popping_cork::popcorn::party_popper:💥
- HennSarvBrass Contributor
One thing with =LET function I dont undestand
On this example You use parameter as city datatype and col param.latitude
when I use folowing example
=LET(t1, SomeTable, XLOOKUP(7, t1[keycolumn], t1[valuecolumn]) - dont work
so .-operator works with variables but [] indexer don't workI quess sometime might be usefull to have
=LAMBDA(SomeTable, Key, XLOOKUP(Key, SomeTable[KeyColumn], SomeTable[ValueColumn])) as named funktionReference on SomeTable returns an array, actually SomeTable[#Data], not the table. Thus t1 is array, not table.
- Sameer_BhideIron Contributor
CellColor
=LAMBDA(Rng, GET.CELL(63,Rng))
Crashes excel
Any way to get this to work
Cheers
Sam
- David HagerCopper Contributor
Sameer_Bhide No. XLM functions cannot be used on the worksheet.
- Sameer_BhideIron Contributor
Are there plans to support names defined using LAMBDA functions to be distributed via Add-ins or are we back to PERSONAL.xlsb Cheers Sam
IMHO, lambda management shall be the same for desktop, online and mobile versions.
- lori_mSteel Contributor
Given a named formula MyFunc in Book1, we should be able to call it from another workbook (as with vba functions):
=Book1!MyFunc(123)
If MyFunc =LAMBDA(x,x) this returns an error on my build but I assume it will work soon. Instead we could test with MyFunc = MyVBAFunc where
Function MyVBAFunc(x): MyVBAFunc = x: End Function
To access MyFunc as an add-in function without the Book1! prefix we would need to press Ctrl+F11 to open a macro sheet and change the definition in the define name dialog to a function. Or equivalently from vba:
Names("MyFunc").MacroType=xlFunction
For a simple test define the name MyFunc:=123 as a function and set the workbook IsAddin property to True. This name is then accessible from any workbook.
All the customs formula made with LAMBDA to be a way to stored/export online & those can be globally accessible to any workbook under that M365 subscription account.
It will be always safe and no loss of function in case of system crash.
Regards, Faraz Shaikh
- David HagerCopper Contributor
Sameer_Bhide You can save all of your LAMBDA formulas in a workbook and then move/copy a blank worksheet from that workbook to another workbook where you want to use them.
- lori_mSteel Contributor
Copying a sheet is a neat trick. XLM functions can't be input in the worksheet but should still be ok within names, this is still in beta however and it looks like a number of things are not quite how they should be yet.
Sameer_Bhide
That method comes from having spent too much time writing Excel4 macros even before VBA was mainstream! XLM language is long gone, as you say, but the same environment is now playing a key role as the old macro functions were defined via names in much the same way the new LAMBDA function is. Another little known feature of Excel is that every session has a hidden macro workbook which is where XLL function names are stored. In fact it's possible to copy workbook names to this hidden area as follows...
Enter the formula =MyFunc in A1, defined as before, and from the VBA immediate window execute the following command (in R1C1 notation)ExecuteExcel4Macro "COPY(!C1,TEXTREF(""C1""))"
MyFunc is now defined like an XLL function that can be accessed from any open workbook and is available even when the original workbook is closed.
This is awesome & I can't wait to get my hands on it
- MSBey0813_Copper ContributorHello will you be able to assist me with navigating excel?