Progress: March 28, 2009

I decided I wanted to use Google maps along with the Mapquest maps to examine the different mapping formats. For the former, I needed my waypoints in decimal format. I found a great site to do Latitude/Longitude Conversions. This would have been useful when I was creating my digital maps in the beginning of this process. All the Quebec topographical maps were in the degrees, minutes, second format, while the Swedish maps were in the decimal format. At the time I didn't know the difference. I simply reformatted the decimal data into the degrees, minutes, second format, not realizing that I was bypassing the mathematical formula. I didn't realize that latitude and longitude values can be set using different notations: Decimal Degrees (DDD) (For example, 58.7500N) and Degrees, Minutes, and Seconds (DMS). (For example, 58°45'00"N). You can even use the Degrees, Minutes with Decimal Seconds (DMM) notation. The result is that my three Swedish maps were slightly off.

S-1 N 58°45'00" E -17°00'00" or 58.75N,17E

(not N 58°75'00" E- 17°00'00")

S-2 N 66°19'01" E -22°49'59" or 66.317N,22.833E

(not N 66°38'00" E- 22°83'00")

S-3 N 60°32'60" E 16°16'59" or 60.55N,16.283E

(not N 60°55'00" E- 16°28'00")

I didn't take note of the discrepancy until I was tweaking the Google code for each map. This is what happens when you learn as you go along. I really don't mind looking foolish, as so many of my creative choices in the past have stemmed from errors and accidents. Getting lost and taking detours in the physical realm (cycling), has its affinities in the creative realm as well. The chance happenings that you cannot plan. You can only set the stage for them to happen by being open.

Process: Hidden boundaries

Due to the ephemeral nature of my project — where I am trying to map waterways, often mutable as they are subject to time and weather — it is fitting that the Google maps and the Mapquest maps often reveal different boundaries. For example, Mapquest names and outlines the Whitefish Lake Indian Reserve 6 inhabited by the Ojibwa Whitefish Lake First Nation that is situated beside Panache Lake (PA-1). Google uses the reserve's official name (Whitefish Lake 6) without indicating it is a reserve, and does not include its boundaries. However, if you Google the term "Whitefish Lake Indian Reserve 6", it does bring up the Google Map. Mapquest seems to be more explicit with its tracing and naming.

It underlines my thoughts on mapmaking: that the map is related to its maker. There is not one Map, nor is there solely one interpretation of the world or reality. If something is missing from a map, does it mean it does not exist? Who decides what is worthy of being documented? What choices am I making while working on this project? What are my own motives?

Progress: March 7, 2009

Though I've worked on this project off and on for years due to sorry finances and a little detour through academia, the timing couldn't be better for completing the Tongue Rug project now in terms of new social media tools. The blog is the perfect medium to make the virtual sladdakavring.

• Each tag (A-1, LE-1, LA-1, etc.) becomes the individual tongues which make up the Tongue Rug.
• At the same time, each tag corresponds to a topographical element (body of water, bridge, etc.).
• The time-based entries allows me to keep track of my cycling logs as well as the associative thoughts and mini essays which surround this project.
• Commenting feature invites the public's participation and has the potential to alter the shape of the virtual Tongue Rug.

I'm looking forward to investigating the possibilities of the blog; playing, exploring, stretching and tweaking it, imagining new uses for it in both a formal and theoretical manner.