I, too, have been thinking that a core+layers approach would be useful in a number of contexts, primarily conflation between different databases/datasets. But the same qualities that make it useful for historical (i.e. Civil War battlefield mapping) might also be useful for mapping of ephemeral events such as Burning Man (<a href="http://www.openstreetmap.org/?lat=40.76684&lon=-119.22824&zoom=15&layers=B000FTF">http://www.openstreetmap.org/?lat=40.76684&lon=-119.22824&zoom=15&layers=B000FTF</a>)<br>
<br clear="all">-- SEJ<br><br>t: @geomantic s: sejohnson8<br><br>"A serious and good philosophical work could be written consisting entirely of jokes." -- Ludwig Wittgenstein<br><br>
<br><br><div class="gmail_quote">On Mon, Mar 28, 2011 at 10:36, <span dir="ltr"><<a href="mailto:john@jfeldredge.com">john@jfeldredge.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I like this core+layers idea. It would make it easier to render a series of overlays, for cases where one wanted to show changes over time.<br>
<div class="im"><br>
-------Original Email-------<br>
Subject :Re: [Talk-us] Civil War sites<br>
</div>From :mailto:<a href="mailto:rwelty@averillpark.net">rwelty@averillpark.net</a><br>
Date :Mon Mar 28 09:29:59 America/Chicago 2011<br>
<div><div></div><div class="h5"><br>
<br>
On 3/28/11 10:21 AM, Jeffrey Ollie wrote:<br>
> On Sat, Mar 26, 2011 at 4:57 PM, Richard Welty<<a href="mailto:rwelty@averillpark.net">rwelty@averillpark.net</a>> wrote:<br>
>> i'm debating whether or not i want to set up a parallel database, using<br>
>> the OSM design, to contain historical data that can be used in a mashup<br>
>> with OSM, and opening it up for historically minded mappers to use as<br>
>> a laboratory for experiments in how one would tag this stuff.<br>
> Actually, what might be really interesting is having a wikispaces type<br>
> hosting environment where anyone could set up a separate OSM instance<br>
> with a separate database, rails port, mapnik rendering with a custom<br>
> stylesheet etc.<br>
><br>
i was thinking this could also be a model for how to do things like<br>
a separate boundary database, etc. i've long thought that some of the<br>
issues we argue about would be made much simpler if we had a<br>
core + layers model.<br>
> This would be interesting to map historic data that's not appropriate<br>
> for the main OSM database (for example, one OSM-space per<br>
> battlefield), or to experiment with nonstandard tagging, or to create<br>
> maps with non-OSM compatible licenses (although I would discourage the<br>
> latter).<br>
><br>
we should try one or two of these to get a better sense of what a<br>
common solution ought to look like.<br>
<br>
richard<br>
<br>
<br>
<br>
_______________________________________________<br>
Talk-us mailing list<br>
<a href="mailto:Talk-us@openstreetmap.org">Talk-us@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/talk-us" target="_blank">http://lists.openstreetmap.org/listinfo/talk-us</a><br>
<br>
</div></div><div class="im">--<br>
John F. Eldredge -- <a href="mailto:john@jfeldredge.com">john@jfeldredge.com</a><br>
"Reserve your right to think, for even to think wrongly is better than not to think at all." -- Hypatia of Alexandria<br>
_______________________________________________<br>
</div><div><div></div><div class="h5">Talk-us mailing list<br>
<a href="mailto:Talk-us@openstreetmap.org">Talk-us@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/talk-us" target="_blank">http://lists.openstreetmap.org/listinfo/talk-us</a><br>
</div></div></blockquote></div><br>