GPS-triggered thing for a Creative Partnerships interview. We’ll be re-writing entries for a Hitchhiker’s Guide to the Galaxy-esque publication to give more detail on the Earth, Moon and Sun.
Distance between the sun and Pluto remapped to 212 metres so it fits on the school field. This then makes the distance between the sun and Earth just over 5 metres. Will need to do a zoom, I think...
I’ll be using The Anticipator on Monday to try and locate the source of a mysterious noise, so over the last few days I’ve been dusting off the cardboard hardware and the (now defunct) mscape software.
The Anticipator: now with power indicator, LED bezels and several layers of what I hope will be waterproof spray...
I’ve tarted up The Anticipator a bit to hopefully improve its usability – bezels for the main series of LEDs and also a power indicator. We’ll be using it no matter the weather, so I’ve also given it a few coats of waterproofing. (Not that I’m feeling pessimistic at all, but I’ve also given myself a new waterproof coat too!)
I’ve put together a first draft of the GPS zones I’ll be using over the school field to represent the presence of our mysterious noise-making object and tomorrow I’ll be in Leicester giving it a test run.
School field with GPS zones overlaid
Oh, and we’ll also be testing the field with a metal detector, just to make sure we don’t get any derailing surprises on Wednesday next week when we do it with 50 kids watching!
I’ve been doing lots of GPS legwork in preparation for a piece of place-specific work I’m developing for a section of Digbeth.
Basically this means walking a fixed route many times whilst carrying a GPS device so I can then look back at the trace of where it thought I went and get a feel for how much the buildings deflect the GPS signal. The things I’m particularly interested in (sorry – can’t be too specific at this stage!) are extremely liable to do this, so let’s just say I’m spending a lot of time walking around Digbeth at the moment!
Each walk takes approximately an hour to complete: I walk up and down particular roads, always staying on the right hand side and walking in the middle of the pavement (or as close to it as I can get seeing as how the pavements are often substitute carparks in Digbeth).
A few days ago I did a nice walk in the sunshine, but it was sullied somewhat when I got home and processed the traces – only the first 400m or so of my walk had been recorded! After that I decided to take both of my devices out with me, so I had a safety net if one of them didn’t record properly.
Yesterday I walked with a device in each hand:
Check out those gum constellations! nice.
As I walked, I noticed that the device in my right hand was consistently giving me more erratic readings for my position than the one in my left hand. At one point I left them both next to each other on a wall for a few minutes so that when I could tell if it was my body disrupting the signal, or if it was because the device in my right hand was closer to the buildings I was walking past.
As you can see in the above screen-grab, there’s still a lot of discrepancy.
This got me thinking: by taking two devices out with me, I now had two traces that could be synchronised because the data that’s logged also includes time.
With a bit of fiddling around in notepad and calc I was able to merge the two sets of data and combine it with some mark-up so that that rather than having a line per device that joined position at time1 with position at time2, I could generate a series of lines that joined position from device1 and time1 with position with device2 at time1. Approximately.
Here’s a screen grab:
Most of the lines really aren’t that short though and Digbeth is criss-crossed with a mesh of yellow. The best attempt so far at describing it comes from Tom Maillioux:
Like you reprogrammed your GPS to make not just a point, but a line from everywhere you were, showing all the places where you COULD have been.
I love how this has turned the data-collection into a drawing project and how it’s resonating with aspects of psychogeography, belief in technology and the whole sort of indecisiveness of Digbeth.
Now all I need is a way of extracting those lines from the .kml file so I can print them out big.
I’m not very familiar with either GPS or Google Earth so this took me a lot of trial and error – there’s probably room for some refinement!
You have used mscape to log your GPS route, but the overlay trace function within mscape isn’t useful for comparing multiple traces or for sharing with others.
Open your log file and save a copy somewhere else to work with.
I’m generally working with coordinates in decimal degrees in Google Earth (Tools > Options… >3D view), so that’s the format I want my log data in.
Open the file in notepad (or other text editor) and check your data is in the right format. Here’s a sample line for Birmingham, UK (wrapped):
21:05:32,Place,centre_and_digbeth,E,OnLocationChange,
52.4545033333333,-1.892005
We need to strip out all the first part so we’re only left with the coordinates.
Open the text file (you did save a different copy to work with, right?) in Calc or alternative spreadsheet application. You’ll need to open it as text CSV so make sure you select that file type after selecting the file you want to work with:
The next window will give you some options. Check the box to select comma as a separator and double-check in the preview below that this splits your data up into the appropriate columns:
After the file has opened, select columns A-E and delete them:
This will leave you with just your longitude and latitude data in columns F and G. They’re the wrong way around though so we need to select column G and cut and paste it into column A, and then cut and paste F into B:
For me, calc defaults to showing numbers to 2 decimal places, so I right click and format cells to bring it up to 14 decimal places which is how accurate my log data is:
(You may need to increase the column width to display the full number rather than ###.)
We now have data that we can insert into a .kml file for Google Earth. Nearly.
Save your spreadsheet as a .csv file, making sure to check the “edit filter settings” box at the bottom:
In the next window make sure you’re using a comma as your field delimiter and then save.
You can now open up your .csv file in notepad. It should look something like this:
-1.89200500000000,52.45450333333330
-1.89200500000000,52.45450333333330
-1.89200500000000,52.45450333333330
-1.89213000000000,52.45448500000000
-1.89213000000000,52.45448500000000
-1.89213000000000,52.45448500000000
-1.89210666666667,52.45450333333330
This is what you will carry over into your .kml file.
Some of my logs are in UTM format, (I think it’s something to do with importing a pre-existing maplib file, this may help) in which case they look more like this to start off with:
20:32:17,Place,centre_and_digbeth,E,OnLocationChange,
575850.093317163,5814462.83102075
(You can check what you’re aiming for by hovering the mouse over your location in Google Earth and reading off the coordinates at the bottom of the window.)
To convert from UTM to decimal lat/long I used the batch convert sheet of this spreadsheet from Steven Dutch. In the case of Birmingham (and most of the UK) set column D cells to all have a value of “N” and column E (aka UTM zone) to “30”. You’ll then have to copy your data into F and G and extend the formulae down on either side to the appropriate length.
I then had problems trying to copy and paste the results into a different file because the cells were still trying to reference cells in the first spreadsheet for the formulae. My eventual work-around was to save as a .csv file and then open it again before copying into a different file, switching the column positions and then taking it into notepad.
Working from the examples here, I got my basic .kml structure down to this.
Save that file and then you can open it up in your text editor.
Copy and paste your coordinates into the gap between the
Save and then cross your fingers as you open the .kml file in Google Earth!
It’s not that grate, akshully.
(click for map of full walk.)
Just before Christmas I responded to a call for artists from a Primary school looking for ways of
I think I had my application in – suggesting application of mscape – within an hour of first getting the notification email.
Experience has shown that it can be a bit tricky explaining the principles of the software to people who are not familiar with the technologies involved. Talking sticks to the rescue.
In preparation for meeting with the project coordinators this morning, yesterday I prepared a quick demonstration mediascape to hint at how these things might be used as an impetus for creative narrative. (I’d never been to the school before, and so didn’t attempt to try and create something specific to the location).
Although it was only intended as a quick demo, I’ve become quite taken by the idea so I’m blogging it in case anyone’s interested in providing motivation or situation for putting it into practice. :)
It’s a very simple set-up in terms of the coding involved: just a series of regions placed around the (in this case) school environment with onEnter/onExit events that trigger an alarm that randomly selects a sound file for addition to the playlist.
The interesting bit came when trying to decide what the sound files should consist of.
The context I’m imagining is a small group of pupils carrying a talking stick-esque device around with them as they set off on an improvised adventure around the designated area. This could be based on a classic journeying quest; be it to find an object or explore uncharted lands. Our intrepid adventurers move around in real space, but use their imaginations to reinterpret their surroundings and invent new things within it.
The role of the talking stick-esque device is to randomly interject prompts that the adventurers must respond to in real time within their narratives: if the stick yells out a warning to “hide!”, then hide they must; if the stick wonders if anyone lives here, then they should assess the surroundings and decide if it’s a suitable habitat for whatever characters are in the story…
Here are the prompts I used for the demo: (Many thanks to @goodhen whose response to my twitter request added a large number of these to the list.)
Look out! | What was that noise? | who’s this? | And so, off they went | oh no… | Good news! | Don’t move! | Shhhhh! Listen | What’s that over there in the distance? | Is anyone else getting that strange feeling? | Whatever you do, don’t make any sudden movements… | I think we need a change of plan | Be careful | Quick! What are we going to do? | What’s that smell? | Is there something hiding in there? | What was it he said again? | Quick, run for it! | Hide! | What should we do next? | Is it safe? | Look! Up in the sky! | Oh! That reminds me! | What *is* that?! | I feel weird. What’s happening to me? | I’m hungry | huh, is that an elephant? | I don’t believe it! | Of course! | I knew that was going to happen | oh, wait a minute | hang on | are you sure this is a good idea | what do you think will happen? | [Gasp] | ouch | do you think anyone lives here? | Is it a message?
What type of prompts inject the narrative with the sort of elements that make for a gripping narrative and what sort of prompts inject the narrative with opportunities for pupils to develop the sorts of skills their teachers might be looking for? And are these things different? …oh, and how can they instigate interactions with/responses to the surroundings too?
Also for consideration: How to start off the story – should you set a particular scenario and then can you tailor your prompts to that? Would it work equally well with trigger regions placed randomly, or should they relate to the ‘interesting’ features of the landscape? With more knowledge of yarn-spinning, would it be a good idea to add conditional logic to the prompt selection such that if x has already been played, then do/don’t play y?
About 6 months ago I started getting very interested in how people navigate their way around a particular part of the New Forest.
Having now been to The Other Canada I returned to Canada Common a couple of times over the last week or so with the beginnings of an idea to collate the material I gathered from the dog-walkers into a mscape-driven thingy that then presents you with different guidance and instructions depending on where you are and which direction you are heading in.
I still haven’t decided on exactly how I’m going to tackle it, so I just took the opportunity to observe and ponder, trying to place the information people had given me back into the landscape it referred to.
The the GPS trace shows that, despite the cold weather freezing most of the water on the common, there were still a few parts I struggled with (for example, the S shape in the middle of this image as I try and decide how best to cross a small stream!)
[note to self: must take a look at how to import the log into Google Earth – I don’t like all those artefacts that appear on the images imported into mscape]
I have to say though, the best tracks laid that day were the snuffly ones made by the ponies.
This video shows the landscape I’m investigating in 2 revolutions: the first with no markers; and the second with labels indicating some of the landmarks people use to navigate by [warning: not suitable for those prone to sea-sickness].
landmarks from nikkipugh on Vimeo.
A few photos from the walk:
This afternoon I went out to a nearby and conveniently large, open area of common to test a new version of the code for the project I started last month.
The code works a treat – which is great – but I can confirm the experience of using it is rubbish without the sticks and someone else to play with.
Can you get there from here? from nikkipugh on Vimeo.
Here is a [completely non-representative] taster of what was coming out of the cardboard boxes:
Percussion for Hill and GPS from nikkipugh on Vimeo.
The drumming and breathing was commissioned from Adam Kinner (the saxophonist from this post). He’s recently started a blog and I definitely think it’s one to watch for the future. Go have a look-see.
Copyright and permissions:
General blog contents released under a Creative Commons
by-nc-sa license.
Artworks and other projects copyright Nicola Pugh 2003-2024, all rights reserved.
If in doubt, ask.
The theme used on this WordPress-powered site started off life as Modern Clix, by Rodrigo Galindez.