- Get a list of likely trig points
- Alternative web hosting
- Ideally the data defining the trig points is downloaded in a JSON file rather than being hard coded …
- … which means that some way of managing and creating the JSON data is needed
- Different coloured markers for the hierarchy of trig points.
- It would also be neat if I could show 3D models of points of interest in a pop up window. Sketchfab provides a way of embedding content in an iframe so it should be possible.
Each of these is described in more detail below but here’s the link to the first version containing a few more panoramas ( and a lot more to go ) – https://john-davies.github.io/
Trig Point List
I wasn’t intending to take a panorama from every trig point because there’s far too many of them 🙂 The Ordnance Survey has a useful search page and also you can download a CSV file of the whole lot. I eventually chose 40, mainly in the western end of the Brecon Beacons, the Gower Peninsula and a few in between ( but see comments about disk space below ). I’ll probably end up with fewer than this because:
- Some will be destroyed
- Some are on private land
- Some of the views may not be very inspiring
Alternative Web Hosting
Up to now I’ve been using Google’s App Engine free tier to host demos that I can’t run on this WordPress site. Generally this has worked well except for one extremely annoying feature. Rather than uploading only the files that have changed the App Engine client will upload all the files each time. This is rather tiresome when you’ve got 100s of Mbytes of image files that don’t change from one update to the next1.
There are a number of other free options out there but I chose the GitHub offering as I already use it to store source code. The only problem at the moment is that they say “We recommend repositories be kept under 1GB each.” Each trig point takes about 25 Mbytes and I’ve got about 40 identified as candidates which may make it a bit tight for space eventually. I’ve decided not to worry about it for now because, as described above, this list will inevitably be reduced.
1Note that it’s not quite that simple because if you do two updates in quick succession then only the changed files get uploaded. However if you leave too much time between updates ( > 1 day? ) then the whole lot is uploaded. I found one Stackoverflow comment on this matter which seems to confirm what I’ve experienced.
Creating and Managing JSON Files
There’s a small amount of data that needs to be defined for each trig point – essentially the hard coded data in the demo. The JSON file to hold this data is fairly straightforward but, even though JSON file syntax is human readable, I really didn’t fancy manually maintaining it via a text editor.
I did search for some sort of graphical tool that would let me define the schema of the file, enter the data then export to a JSON file but I didn’t find anything useful. In the end I resorted to the old favourite of a spreadsheet with one trig point defined per tab. I then exported the data to CSV files and wrote a small shell script to convert the CSV files to a JSON file.
Even this wasn’t quite as straightforward as it should be because LibreOffice Calc doesn’t have an “export all to CSV” function but I found a suitable macro online. ( To be fair to LibreOffice, Excel doesn’t have this feature either 🙂 )
Leaflet only comes with blue markers as standard. However there are a number of free addons available and I chose this one. I also added a few more to use for showing whether an image was available or not available.
Embedding 3D Models
The pop up window for the “About” text and displaying the 3D models was based on this W3 Schools tutorial. The “About” text is straight HTML and the 3D model embedding is a slight tweak of the standard Sketchfab method.
At the moment one 3D model can be found on the Fan Brycheiniog trig point. This is a model of Llyn y Fan Fawr generated from LiDAR data and a Google Map image overlay.
Deploying the site via GitHub pages was also easy and I only found one slight wrinkle which was fairly easily solved:
I first published a very simple HTML file to make sure that everything worked but when I loaded the first version of the site I got the following error:
The page build failed for the `master` branch with the following error: Unable to build page. Please try again later. For information on troubleshooting Jekyll see: https://help.github.com/articles/troubleshooting-jekyll-builds If you have any questions you can contact us by replying to this email.
Because you specifically mentioned that your site is static HTML/CSS with no Jekyll, the easiest fix would be to disable Jekyll by adding a .nojekyll file like described here.
Sure enough adding a blank .nojekyll file in the root directory did the trick and everything deployed correctly.
At the moment the image and map panes are a fixed size and ideally they would resize as the browser window is resized. Fixing this is certainly a priority. Other than that it’s on to the interesting bit of taking panorama photos and uploading 3D models …