<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 1/31/10 10:51 AM, Anthony wrote:
<blockquote
cite="mid:71cd4dd91001310751p29491d7ev6c88b3b0ecf63856@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type"
content="text/html; charset=ISO-8859-1">
On Sun, Jan 31, 2010 at 8:46 AM, John Smith <span><<a
moz-do-not-send="true" href="mailto:deltafoxtrot256@gmail.com">deltafoxtrot256@gmail.com</a>></span>
wrote:<br>
<div>
<blockquote>Again, are we trying to make a map look photo realistic?<br>
<br>
To me a map is a set of abstract ideas that express information about<br>
reality that can't be seen from photo imagery. Mapping road widths can<br>
be done by estimate based on a number of factors that are both vector<br>
and meta information, I fail to see how presenting an area will<br>
actually present any more information to a person. If they want such<br>
information and if there is aerial imagery they can just switch tile<br>
sets.<br>
</blockquote>
</div>
</blockquote>
in the case of the race track example, using a way as a centerline and
including<br>
width= tags should encompass what's needed. i can represent escape
roads,<br>
optional chicanes, pit roads, access & paddock roads, etc., quite
well with those<br>
tools.<br>
<br>
richard<br>
<br>
</body>
</html>