On 4/30/15 7:45 AM, SK53 wrote: > 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. > given shared geometries, one could argue that we should share nodes between the ways. i usually avoid that in OSM but in this case it seems appropriate.
JOSM can support selecting one of the the stacked ways, but it's still obnoxious. still, it might do for now. > > With respect to dates, I like the stuff suggested by Trevor. don't think i've seen that. pointer or link? > Last thought would be: Would it be feasible to introduce some feature > to support temporal queries in the Overpass stack? > by temporal queries do you mean date ranges and before/after on tags containing dates? probably, but i haven't looked at the actual overpass code yet so i don't have any way of assessing difficulty. i can add it to the list. > PS. This is worth mentioning in your talk to show that examples are > the way to discover issues/ways of doing things. > i was planning on discussing things that have been exposed that we don't know how to do yet and potential approaches. 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
