<!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">
<br>
<br>
Tyler Mitchell wrote:
<blockquote cite="midE1D3C094-3C4D-4A00-BA2F-60381EBEAF99@shaw.ca"
type="cite"><br>
<div>
<div>On 30-Jul-06, at 9:29 PM, Bob Basques wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><span class="Apple-style-span"
style="border-collapse: separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;">I
think the route to go with something like this, is NOT to use a
specific portable OS, but rather concentrate on using a Micro PC of
some sort (the OQO with Linux, comes to mind) and use the same old
tools we've been using for everything else. My database of choice for
the storage, at least for points, would be MYSQL, much lower overhead
for storage and retrieval. The Mapping side is a different story, but
speed and simplicity would be the order of the day. While there's no
reason a Spatial database couldn't be used for the mapping, I would
suspect that the management of the mapping data might be easier with
static SHP files in the near term. Although using a Regular PC OS
would help with database up keep in the syncing process as well.</span></blockquote>
</div>
<br>
<div>I agree, for the mostpart the specialised portable OS's were
somewhat invented to subvert hardware limitations. Now, with flash/SD
memory and mobile PC chip architecture, I think there is less of a
barrier.</div>
<div><br class="khtml-block-placeholder">
</div>
<div>re: light databases, the aptly named SQLite is worthy of
consideration. Storing simple Well Known Text representations of
geometry in a SQLite db would be an easy way to incorporate open data
standards.</div>
</blockquote>
I'm open to using WKT, but don't know that even this level of data
organization is needed up front. I supposed it will come into play as
the client GUI input methods improve, the ability to draw Spatial
primitive for example will require something like this for example.<br>
<br>
bobb<br>
<br>
<blockquote cite="midE1D3C094-3C4D-4A00-BA2F-60381EBEAF99@shaw.ca"
type="cite">
<div><br class="khtml-block-placeholder">
</div>
<div>Tyler</div>
</blockquote>
</body>
</html>