On 15/08/15 16:29, Russ Nelson wrote: > Now, I'm sure somebody will, at some point say, "Russell, just go off > to OpenHistoricalMap and put your data there." That's fine, except for > those pesky implementation details where THEY ARE IN TWO DISPARATE > DATABASES, UNCONNECTED. How, exactly, do you make a relation that > shows the entire route of a railroad when half of it is off in a > different corner?
And it's not just railroads that this affects ... In my book OHM needs to be a clone of OSM AND all the history so that we can manage things properly. But the bulk of the missing historic data IS start_date for every object currently documented, and that then needs passing back to OSM. So why not just have the one database? The alternative is a model that CAN use multiple databases, but I think that only really works for secondary data? Trying to merge geometry is not something that works well unless that geometry can be completely isolated. Trying to use the same way elements for different objects in different databases does not work :( -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk _______________________________________________ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
