Always to play the devils advocate..... We have all heard about "mapping for the renderer" but are you "mapping for the third party data providers that is slow at updating the planet data". They should use the data correctly. It is annoying the stale content that some devs/providers provide, maybe it would encourage them to put some effort into updating the content for frequently. I think we all have different opinions on this (it will likely take months for the work to be done at least 6 weeks was the latest I heard this morning) and don't we pride ourselves about having the most up-to-date information and what is on the ground?! Permanent versus temporary is very subjective and people will have different opinions. Maybe a time period should be used a month, etc? Maybe something between a road works for a day to a 2 years bridge closure. Why would not want to see on the map a bridge that is closed for ages? I wonder if DWG should revert all those building those HOT people marked as destroyed recently...... > From: l...@lorp.org > Date: Thu, 6 Feb 2014 14:46:55 +0000 > To: gravityst...@gmail.com > CC: talk-gb@openstreetmap.org > Subject: Re: [Talk-GB] Somerset Levels Flooding > > Indeed this is surely the right approach. Many people use OSM inside products > where the map data is updated rarely: all the offline map apps for mobile > come to mind. Temporary states have no place in these apps, and it’s unfair > on their devs to force them to work out a long-term state to offer their > users. > > - L > > > On 6 Feb 2014, at 14:36, Andy Allan <gravityst...@gmail.com> wrote: > > > >> On 6 February 2014 09:43, David Earl <da...@frankieandshadow.com> wrote: > >> I think it would be useful to have a means of indicating road closures etc > >> which are different from simply pretending the road doesn't exist or > >> doesn't > >> allow certain users for a while. > > > > I work on the principle of marking the "permanent state" of features, > > as much as possible. Obviously everything changes, but if a situation > > is deliberately temporary (e.g. a road closed for crane operations, or > > for a fortnight for digging, etc) then I don't change the 'permanent > > state' of the feature. We had a trunk road in Putney that was one-way > > for three months, but I didn't change the map to correspond since it > > was clearly not permanent. And I'd encourage people not to mark > > flooding as natural=water, or removing bits of railway when they are > > certainly going to repair it, or even adding "access=no" tags to > > something that might be fixed by the weekend. > > > > If it's deemed important by people to mark the "temporary state" > > somehow, then please use a separate tagging system. > > > > Cheers, > > Andy > > > > _______________________________________________ > > Talk-GB mailing list > > Talk-GB@openstreetmap.org > > https://lists.openstreetmap.org/listinfo/talk-gb > > _______________________________________________ > Talk-GB mailing list > Talk-GB@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-gb
_______________________________________________ Talk-GB mailing list Talk-GB@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-gb
