[OHM] date formats (was Re: Hidden Geo of NY's Gay Nightlife)

[SK53]

Hi Richard,

I've always presumed that you would create different ways for surface=clay,
surface=asphalt with appropriate time intervals. This gets potentially very
messy for city streets which may go surface=dirt =>gravel
=>compacted=>cobblestone=>asphalt along with changes in lighting, width,
lanes etc. (Not to mention names). I deliberately avoided this type of
issue when I looked at Derby Road as an example
<http://sk53-osm.blogspot.co.uk/2014/05/editing-historical-road-layouts.html>
.

These changes are far more frequent than the actual geometry of the way.

One way one could think about this is separating temporal tagging of
geometry from temporal tagging of features of the geometry. (In the OSM
model this would require introducing a table for features which would
contain the tags column; and way_features, node_features, relation_featues;
quite how one would handle this with editors etc is another matter).

With respect to dates, I like the stuff suggested by Trevor.

Last thought would be: Would it be feasible to introduce some feature to
support temporal queries in the Overpass stack?

Jerry

PS. This is worth mentioning in your talk to show that examples are the way
to discover issues/ways of doing things.

On 29 April 2015 at 21:59, Richard Welty <rwelty at averillpark.net> wrote:

>  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
>
> -- rwelty at averillpark.net
>  Averill Park Networking - GIS & IT Consulting
>  OpenStreetMap - PostgreSQL - Linux
>  Java - Web Applications - Search
>
>
> _______________________________________________
> Historic mailing list
> Historic at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/historic
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/historic/attachments/20150430/729d3e7c/attachment.html>