Hi
As the mapper for Burning Man, let me explain a little bit about the festival,
and how I've attempted to represent it in OSM.
But first...
Apollinaris Schoell ascho...@gmail.com
should be deleted then. Burning man follows a no trace policy. as alternative
it must be at least tagged
From: Aun Johnsen li...@gimnechiske.org
Date: Fri, Dec 18, 2009 at 12:06 PM
Subject: Re: [OSM-talk] Burning Man (was: revert changesets??)
To: Mikel Maron mikel_ma...@yahoo.com
Just a suggestion that I think will satisfy both camps:
When the burning man us remapped (i.e. moved), add the prefix
2009/12/18 Mikel Maron mikel_ma...@yahoo.com:
So that's the situation. I decided to represent the temporality by adding
start_date and end_date tags to the 2008 data, one of the suggestions of
I agree with comments on the 4D page about this that
start_date/end_date is a bit conflicting with
2009/12/18 Aun Johnsen li...@gimnechiske.org:
Just a suggestion that I think will satisfy both camps:
When the burning man us remapped (i.e. moved), add the prefix burning_man:
to all tags, that will retain them in the database, erase them from maps,
but still allow for special interest maps
On 18 Dec 2009, at 3:51 , Mikel Maron wrote:
Of course, we now have a map with data shown past the end_date for the 2008
event. The most obvious option is tuning the renderers to data past it's end
date. There's downsides to that .. larger planet size, increased complexity
in
On Fri, Dec 18, 2009 at 12:12 PM, John Smith deltafoxtrot...@gmail.comwrote:
2009/12/18 Aun Johnsen li...@gimnechiske.org:
Just a suggestion that I think will satisfy both camps:
When the burning man us remapped (i.e. moved), add the prefix
burning_man:
to all tags, that will retain
On Fri, Dec 18, 2009 at 12:12 PM, John Smith deltafoxtrot...@gmail.com wrote:
2009/12/18 Aun Johnsen li...@gimnechiske.org:
Just a suggestion that I think will satisfy both camps:
When the burning man us remapped (i.e. moved), add the prefix burning_man:
to all tags, that will retain them in
On Fri, Dec 18, 2009 at 4:24 PM, Aun Johnsen li...@gimnechiske.org wrote:
It is not only rendering software, but all software that use the spatial
data in some way or another.
A few years ago, you could pretty much assume that any untagged
segment in the OSM database was a road. Renderers
On Fri, Dec 18, 2009 at 6:16 PM, John Smith deltafoxtrot...@gmail.com wrote:
2009/12/19 Andy Allan gravityst...@gmail.com:
I prefer the principle of least surprise when working with OSM data.
The most basic analysis of the data should have the least gotchas
possible. So we should avoid tagging
2009/12/19 Andy Allan gravityst...@gmail.com:
Those who are interested in historical maps will need to know about
the 4th dimension and whatever tags are involved. Those who aren't,
shouldn't need to.
Initially it may well be a niche activity, but long term roads move
etc, and it's often
On Fri, Dec 18, 2009 at 11:11 PM, OJ W ojwli...@googlemail.com wrote:
filtering-out historical data (date_end doesn't exist or is in the
past) is 1 or 2 rules. Any application needs tens or hundreds of
rules to even begin to understand OSM (try defining 'can you cycle on
this' or 'is this
2009/12/19 Aun Johnsen li...@gimnechiske.org:
For changing roads, I think the future of changesets will allow us to revert
changes as well as have a way to retrieve historical data. I guess that a
future API version will allow you to see how the world looked in 2009, so
that non-existing roads
12 matches
Mail list logo
