On 4/29/15 3:08 PM, Richard Welty wrote: > On 4/29/15 2:39 PM, Jeff Meyer wrote: >> - Dates >> -- Handling approximate date ranges >> > we need to do this anyway, there are lots of cases where we > need to deal with this. following myself up, which some people tell me is bad form...
my work on track documentation suggests a need for more than just start_date and end_date; tracks drift in and out of operation over time and end up with multiple start/stop dates. on top of that, there are tracks that were clay then paved or paved then clay, and in one supremely novel case, there is an inactive track not far from where i live that had pavement in the corners and clay on the straights for its first year of operation (not enough money to pay for pavement all the way around.) right now i don't really know how to model something like that in OSM terms. richard -- [email protected] Averill Park Networking - GIS & IT Consulting OpenStreetMap - PostgreSQL - Linux Java - Web Applications - Search
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Historic mailing list [email protected] https://lists.openstreetmap.org/listinfo/historic
