Skip to content

mappify.io Rock RMS Plugin

Stewart edited this page Sep 3, 2020 · 5 revisions

Install

To install the plugin to your Rock RMS server, you will need to download latest release melbourne.hopecentral.Mappify.dll file and paste it into the bin folder of your wwwroot (This is normally found within C:\inetpub), doing this will trigger Rock RMS to rebuild and restart (may take a few minutes). That's it, now onto the setup.

Note: Don't use the .plugin file, this will only be used if I decide to add the plugin to the Rock Shop

Setup

mappify.io

You will need to signup for a mappify.io free account, you just need an email address and to setup a password. Once you have confirmed your email address (check your junk mail) and signed in, the account provides you with an API Key and unrestricted access to their service. No need to add credit card details as the free account gives you a generous 2500 api calls per day, which should be more than enough for the average Aussie church using the service. Copy the API key as you'll need it in Rock.

Rock

Configuring your Rock instance to use Mappify is easy. There are two simple changes that have to made. Firstly, visit Admin Tools > General Settings > Global Attributes and set the Support International Addresses value to Yes (Note: as an Aussie church using Rock you may have already done this, but just double check). Secondly, visit Admin Tools > System Settings > Location Services and select Mappify, change the service to Active and paste the API key you copied earlier into the API Key field.

How the Plugin Functions

This location service will pass the values (if any are present) of the address line 1, address line 2, city, state, and postal code fields from Rock to the mappify.io address autocomplete remote procedure call API service. The location service asks for the best match and, if values are present in the response, it verifies the confidence level of the match and will either:

  1. confirm verification and replace the address values stored in Rock with the standardised response values, including geocode coordinates, or
  2. deny verification, due to low match confidence, and instead provide the best match provided by mappify.io with an associated confidence level as a percentage. If this happens, check the recommended match details provided and if suitable update the address to match it and verify again.

Future updates

The confidence measure that is provided by mappify.io and used by plugin could be optimised. As present anything under 75% is considered low match confidence and verification is denied. If you do find that minor misspelling or abbreviations of roadway names are often denied please raise an issue.

Clone this wiki locally