<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 4/29/15 3:08 PM, Richard Welty
wrote:<br>
</div>
<blockquote cite="mid:55412C2C.4070308@averillpark.net" type="cite">
<meta http-equiv="Context-Type" content="text/html; charset=utf-8">
<div class="moz-cite-prefix">On 4/29/15 2:39 PM, Jeff Meyer wrote:<br>
</div>
<blockquote
cite="mid:CAA1fFeyPB1qDE7=p-OnZoT2X1mXw=iW1gviANP79BYr_fNxwBw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>- Dates</div>
<div> -- Handling approximate date ranges</div>
<div><br>
</div>
</div>
</blockquote>
we need to do this anyway, there are lots of cases where we<br>
need to deal with this.
</blockquote>
following myself up, which some people tell me is bad form...<br>
<br>
my work on track documentation suggests a need for more than<br>
just start_date and end_date; tracks drift in and out of operation<br>
over time and end up with multiple start/stop dates. on top of<br>
that, there are tracks that were clay then paved or paved then<br>
clay, and in one supremely novel case, there is an inactive<br>
track not far from where i live that had pavement in the corners<br>
and clay on the straights for its first year of operation (not
enough<br>
money to pay for pavement all the way around.)<br>
<br>
right now i don't really know how to model something like that<br>
in OSM terms.<br>
<br>
richard<br>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-abbreviated" href="mailto:rwelty@averillpark.net">rwelty@averillpark.net</a>
Averill Park Networking - GIS & IT Consulting
OpenStreetMap - PostgreSQL - Linux
Java - Web Applications - Search</pre>
</body>
</html>