A tool to download/archive Matterport virtual tours. Supports most matterport virtual tour links ( ie https://my.matterport.com/show/?m=roWLLMMmPL8 ). This project is not in any way associated with or supported by matterport.com in any way. It supports offline viewing of virtual tours and most tour features including: Walking/browsing the tour using mouse or keyboard. Virtual reality supported tours. Measuring items within the tour. Information nodes and popup data. Dollhouse* and floorplan* views (see "Advanced Options" section below).

1. Install Python 3.6 or higher.
2. Download the files from this repository (click Code button near upper right and click download zip).
3. Extract these files to a local folder.
4. Archive a virtual tour by running matterport-dl.py [url_or_page_id], you may need to use python3 matterport-dl.py ... or python matterport-dl.py ... instead.
5. Revisit an archived virtual tour by running matterport-dl.py [url_or_page_id] 127.0.0.1 8080 and visiting http://127.0.0.1:8080 in a browser.

• Add --proxy 127.0.0.1:1234 to a download run to use a proxy for requests
• Add --advanced-download to a download run to try and download the needed textures and files for supporting dollhouse/floorplan views. NOTE: Must use built in webserver to host content for this to work.

• It is possible to host these Matterport archives using standard web servers however: 1) Certain features beyond the tour itself may not work. 2) #1 may be fixable by specific rewrite rules for apache/nginx. These are not currently provided but if you look at OurSimpleHTTPRequestHandler class near the bottom of the source file you can likely figure out what redirects we do.

• As improvements are made to the script you can often upgrade old archives but simply running the script again. Any existing files downloaded are generally skipped so it will run much faster. This is not a guarantee so backup your important archives first.

• As matterport changes their code things will likely need to be updated in the script. A good place to start is looking at the server.log file for any lines that say "404 error" in them, these are likely additional files we need to download for the archive to work.