Skip to main content

GPX Route Mail App for Exchange 2013 and Exchange Online

As part of my MEC talk last month I presented a Mail App that would show a Map with route layer added based on the content of a GPX attachment on a received message. For example here's a screenshot of the Application that was activated from a GPX file that was exported from the Google Tracks application .


Mail Apps are a new feature of Exchange2013/Exchange Online that gives you a standard way of extending the functionality of Outlook,OWA and OWA for devices. The way this particular Mail app works is first, in the Manifest file there is a filter so it will only show on messages you open/view that have an attachment eg

  1. <Rule xsi:type="RuleCollection" Mode="And">  
  2.     <Rule xsi:type="ItemIs" FormType = "Read" ItemType="Message" />  
  3.     <Rule xsi:type="ItemHasAttachment" />  
  4. </Rule>  

Next if somebody activates the application the next thing it does is uses the new Attachments API that was added in 2013 SP1 to first get the details of the attachments on the message, it then checks if one of them is a GPX attachment. If there is a GPX attachment it then uses an externally hosted controller to make the GetAttachment Call to EWS using a token obtained for authentication to get the Attachment content which is then returned to the MailApp (this is done using a modified version of the following sample). Once the Mail App has the GPX content from the attachment it then uses leaflet which is a open source javascript library that makes mapping easier and also a GPX plugin that was developed for leaflet to add a GPX layer to the map.

Note in this sample I'm using  openstreetmap if you going to use this in your own environment or develop a similar solution using this code you need to be aware of the tile usage policy http://wiki.openstreetmap.org/wiki/Tile_usage_policy of this or any mapping service you decide to use.

To use a Mail App you need to host all the associated the files yourself somewhere see http://msdn.microsoft.com/en-us/library/office/fp161135(v=office.15).aspx for more details. With this particular application you need to host both the Mail App and also the controller service to allow you to get the attachment content.  I've put a download of the hosted code for the Mail App here https://www.dropbox.com/s/6fzzc3hpli8x5sf/HostedFiles.zip the attachment service uses a modified version of http://code.msdn.microsoft.com/office/Mail-apps-for-Office-Get-38babdc9 I've included a copy of the modified controller in the download.

Popular posts from this blog

The MailboxConcurrency limit and using Batching in the Microsoft Graph API

If your getting an error such as Application is over its MailboxConcurrency limit while using the Microsoft Graph API this post may help you understand why. Background   The Mailbox  concurrency limit when your using the Graph API is 4 as per https://docs.microsoft.com/en-us/graph/throttling#outlook-service-limits . This is evaluated for each app ID and mailbox combination so this means you can have different apps running under the same credentials and the poor behavior of one won't cause the other to be throttled. If you compared that to EWS you could have up to 27 concurrent connections but they are shared across all apps on a first come first served basis. Batching Batching in the Graph API is a way of combining multiple requests into a single HTTP request. Batching in the Exchange Mail API's EWS and MAPI has been around for a long time and its common, for email Apps to process large numbers of smaller items for a variety of reasons.  Batching in the Gr...

Exporting and Uploading Mailbox Items using Exchange Web Services using the new ExportItems and UploadItems operations in Exchange 2010 SP1

Two new EWS Operations ExportItems and UploadItems where introduced in Exchange 2010 SP1 that allowed you to do a number of useful things that where previously not possible using Exchange Web Services. Any object that Exchange stores is basically a collection of properties for example a message object is a collection of Message properties, Recipient properties and Attachment properties with a few meta properties that describe the underlying storage thrown in. Normally when using EWS you can access these properties in a number of a ways eg one example is using the strongly type objects such as emailmessage that presents the underlying properties in an intuitive way that's easy to use. Another way is using Extended Properties to access the underlying properties directly. However previously in EWS there was no method to access every property of a message hence there is no way to export or import an item and maintain full fidelity of every property on that item (you could export the...

EWS Create Mailbox folder Powershell module for Exchange and Office365 Mailboxes

This is a rollup post for a couple of scripts I've posted in the past for creating folders using EWS in an Exchange OnPremise or Exchange online Cloud mailbox. It can do the following Create a Folder in the Root of the Mailbox Create-Folder -Mailboxname mailbox@domain.com -NewFolderName test Create a Folder as a SubFolder of the Inbox Create-Folder -Mailboxname mailbox@domain.com -NewFolderName test -ParentFolder '\Inbox' Create a Folder as a SubFolder of the Inbox using EWS Impersonation Create-Folder -Mailboxname mailbox@domain.com -NewFolderName test -ParentFolder '\Inbox' -useImpersonation Create a new Contacts Folder as a SubFolder of the Mailboxes Contacts Folder Create-Folder -Mailboxname mailbox@domain.com -NewFolderName test -ParentFolder '\Contacts' -FolderClass IPF.Contact Create a new Calendar Folder as a SubFolder of the Mailboxes Calendar Folder Create-Folder -Mailboxname mailbox@domain.com -NewFolderName test -Parent...
All sample scripts and source code is provided by for illustrative purposes only. All examples are untested in different environments and therefore, I cannot guarantee or imply reliability, serviceability, or function of these programs.

All code contained herein is provided to you "AS IS" without any warranties of any kind. The implied warranties of non-infringement, merchantability and fitness for a particular purpose are expressly disclaimed.