Skip to main content

How to integrate the Google map support in Azure Bot Service / Luis

Context

A system needs to collect information related to the garbage locations from the user. You decide that one of the interfaces that you want to build is based on a chatbot.

What do we want to achieve?

The user is not all the time in the same location where the garbage was spotted. You want to provide the user the ability to use an interactive map to select the location where the garbage is.



Technology stack

The selected bot that you decide to use is Azure Bot Service and will be fully integrated with Facebook Messager. We are using Node.JS to write the custom code required to run the application. 

The challenge 

Azure Bot Service does not have the ability to display an interactive map in the chat, that would allow the user to select a location.

How to solve the problem

Allowing users to type a specific address or ZIP code might work, but would not indicate the exact location of the garbage. 

Requiring GPS Coordinates would work, but would not be an easy task for an average user and you might lose people's interest. There are multiple GPS coordinates standards and ways to express a location and you would need to handle a lot of data transformation. You would increase the error-prone in this way.


Another approach can be based on your favorite map provider. In my case, Google Maps is one of the best options that I have in my area. The solution is built around a custom web page that is shared with the user at the moment in time when he needs to select the location. That page is unique generated for that session and allows Azure Bot Service to get the exact coordinates where the garbage was spotted. 

In the above solution, we are using Azure Functions to generate on the fly a custom web page where Google Map is displayed. Azure Web App is used to host a Node.JS web application used to render the map. We preferred Azure Web App because there is also some logic that needs to run behind the scene and was the most simple solution available. Another Azure Function is called once the user submits the GPS coordinates. From there, the coordinates are sent to Azure Bot Service and the user is notified that the coordinates were submitted successfully.   

We covered only how we can get the GPS coordinates, around the solution we need additional Azure Functions and a database like Azure Cosmos DB. 

Comments

Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified