Sunday, March 29, 2009

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?



No comments:

Post a Comment