This prototype allows for uploading Ekahau heatmap to a Meraki dashboard as a network floorplan. Given a user's input of (1) a Meraki network, (2) an Ekahau heatmap and (3) the geographical coordinates of its location, the tool uploads the floorplan image to the Meraki cloud, as well as places the corresponding access points on it.
- Roaa Alkhalaf
- Stien Vanderhallen
- Meraki REST API
- Meraki
- Ekahau
The following commands are executed in the terminal.
-
Set up a Python virtual environment. Make sure Python 3 is installed in your environment, and if not, you may download Python here. Once Python 3 is installed in your environment, you can activate the virtual environment with the instructions found here.
-
Access the created virtual environment folder
$ cd your_venv -
Clone this repository
$ git clone https://github.com/gve-sw/gve_devnet_meraki_floorplan_import -
Access the folder
gve_devnet_meraki_floorplan_import$ cd gve_devnet_meraki_floorplan_import -
Install the dependencies:
$ pip install -r requirements.txt -
In
.env, fill out your Meraki API key. Obtain this key in the Meraki dashboard, underMy Profile > API access
MERAKI_API_KEY=<your-meraki-api-key>
-
To launch the app, type the following command in your terminal:
$ python3 app.py -
To access the app, navigate in a browser to
localhost:5004
- On
localhost:5004, you find the landing page of the prototype. Choose the targeted Meraki organization
-
Choose the targeted Meraki network
-
Upload the Ekahau heatmap
-
Select the geographical coordinates of the heatmap
-
Click on Submit Floorplan to submit the heatmap to Meraki cloud
Provided under Cisco Sample Code License, for details see LICENSE
Our code of conduct is available here
See our contributing guidelines here
Please note: This script is meant for demo purposes only. All tools/ scripts in this repo are released for use "AS IS" without any warranties of any kind, including, but not limited to their installation, use, or performance. Any use of these scripts and tools is at your own risk. There is no guarantee that they have been through thorough testing in a comparable environment and we are not responsible for any damage or data loss incurred with their use. You are responsible for reviewing and testing any scripts you run thoroughly before use in any non-testing environment.