Google has now stopped its Earth API and Maps API is a paid for API nowadays. Some capabilities have also been either removed or changed. Therefore, I had to remove all examples of VizMap applications I had created. I didn’t remove the entire topic as I thought some of the code may still be useful with some modifications. 

VizMap: the common vba for setting up parameter sheets

For this example I had created a  Concerts/Venues example that is now deprecated. The complete workbook (googlemapping.xlsm) can be downloaded (above) and the example Parameter WorkSheet is called VenuesParameters.

Setting up the parameter sheets

All VizMap modules start with setting up all the parameter blocks that will be needed. All these common procedures are in the MapPublics module,  along with the names of the parameter blocks that are going to be used. I also register the name of application parameter sheets  as constants here so I can refer to them in other modules – note that the name of the parameter sheet for  cVizAppVenues is defined here. There are also some other common procedures used in geoCoding etc in this module. The key procedure here though is dSetsSetup which sets up all the parameter blocks according to the selected parameter sheet.
This is called at the beginning of a procedure which will be using these structures as follows, and from then on all access to the parameters in the workbook is ‘abstracted’  meaning that the physical locations or dimensions in the workbook do not need to be known as they can be accessed from the dSets Collection by the name referred to in the list of constants.
other modules read additional data the same way, for example, this will get the extra parameter blocks needed to generate a vizMap application
The full code of the MapPublics module

Questions, feedback and VizMap applications you have generated can be submitted for loading to this site via our forum.

Now let’s look at Vba to join master and transactional data