<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div><br></div><div><br></div><div><br></div><div>Aug 11, 2020, 20:49 by dieterdreist@gmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div><br></div><div><br></div><div>sent from a phone<br></div><blockquote><div>On 11. Aug 2020, at 19:55, Clay Smalley <claysmalley@gmail.com> wrote:<br></div><div><br></div><div>We've pointed out concrete steps you can take to improve these initially-mapped stop positions. If mapping stop positions accurately is important to you, why not take responsibility for improving them?<br></div></blockquote><div><br></div><div><br></div><div>I agree that if these stop positions are only guestimates/placeholders it could make sense to at least mark them somehow (fixme etc.) so that improving them becomes easier.<br></div></blockquote><div>If these stop positions are only guestimates/placeholders then mapping platforms<br></div><div>only or instead would be preferable, stop position have some minimal value only<br></div><div>if actually accurate (though even then mapping them is unlikely to be a good idea).<br></div> </body>
</html>