<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi.<br>
<br>
For the haptorender project I'm still working on a
rapid-and-cheap-prototyping solution, more on that probably soon.<br>
<br>
But some thoughts about the rendering rules:<br>
<br>
I think, that general purpose rendering rules are not possible for
tactile maps. Such things are impossible for graphical maps -
different special maps would collide due to restrictions in the
overall count of distinguishable patterns.<br>
<br>
The number of patterns a user can distinguish and, more important,
identify, is significantly smaller in haptics, I'm pretty sure
(although it's only an unprooved claim here).<br>
Therefore it's more or less useless to discuss about "the rendering
rules".<br>
Depending on the content of the (specific) map, the selection of
attributes to render and the resulting density of information that
has to be displayed, it has to be decided which haptical signatures
are used for which information.<br>
<br>
Of course, a standard rendering style for common objects is useful,
but I would not concentrate too much on that for now.<br>
<br>
IMHO the better approach would be to define an interface how
arbitrary reliefs can be transferred to the haptical renderer, be it
as a (well defined) vector graphic or as a (e.g. grayscale) pixel
matrix.<br>
<br>
If there are hardware restrictions like resolution, minimum size of
extruded areas (stability), minimum size of lower areas ("melting
material"), then these are the interesting parameters.<br>
<br>
regards<br>
Peter<br>
<br>
Am 02.03.2012 18:44, schrieb Dr. Thomas Bremer:
<blockquote
cite="mid:CADiEzSmbz27RzRrpmmL8AAXAKVa+ZFVGHnk7r=EiR0t6S4aOzw@mail.gmail.com"
type="cite">
<div>Hello group, hello Daniel,<br>
</div>
<div>great to see that there is more interest in HaptoRender!<br>
</div>
<div class="gmail_quote">2012/3/1 Daniel Hänßgen <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:daniel.haenssgen@stud.fh-hannover.de">daniel.haenssgen@stud.fh-hannover.de</a>></span><br>
<blockquote style="margin:0px 0px 0px
0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"
class="gmail_quote">Design so far:<br>
The software is going to be rendering the OSM-data to a
b/w-image<br>
which is then feed into the output device.<br>
For those output devices I have several ideas, but they still
need to<br>
be evaluated.<br>
Anyhow the B/W-image should be independend of the hardware.</blockquote>
<div>Well, you need some vector representation independent of
the hardware. The quasi standard is <a moz-do-not-send="true"
href="http://en.wikipedia.org/wiki/STL_%28file_format%29">STL</a>.
And yes, this is device independent and can be used by various
CAD programs.</div>
<div> </div>
<blockquote style="margin:0px 0px 0px
0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"
class="gmail_quote">
Objective:<br>
Creation of the map on paper in less than one hour. Hopefully<br>
full-automatically.</blockquote>
<div>What does "on paper" mean for a tactile map?</div>
<div> </div>
<div>Have you already seen page <a moz-do-not-send="true"
href="http://wiki.openstreetmap.org/wiki/Talk:HaptoRender/Rendering_Rules">Talk:HaptoRender/Rendering
Rules</a>? I mean all of you! Please contribute!</div>
<div> </div>
<div>Regards</div>
<div>Thomas</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Accessibility mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Accessibility@openstreetmap.org">Accessibility@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstreetmap.org/listinfo/accessibility">http://lists.openstreetmap.org/listinfo/accessibility</a>
To unsubscribe from this mailing list send an empty email to <a class="moz-txt-link-abbreviated" href="mailto:accessibility-unsubscribe@openstreetmap.org">accessibility-unsubscribe@openstreetmap.org</a>
</pre>
</blockquote>
<br>
</body>
</html>