Re: [Tagging] power lines/cables power

On 15/11/2020 19.17, François Lacombe wrote: Le dim. 15 nov. 2020 à 16:45, André Pirard a écrit : Hi, A group of friends were discussing the

Re: [Tagging] Tagging Cycle Route Relations vs. Ways

Am Di., 17. Nov. 2020 um 20:04 Uhr schrieb stevea : > I never said to NOT use source=* tags, they are correctly used on an > individual datum if / as it might diverge from a greater set of data that > otherwise has another source. In short, if ALL of the data are from a > single source, use a

Re: [Tagging] Tagging Cycle Route Relations vs. Ways

DaveF: I don’t wish to baffle, so I appreciate your clarifications. I think we agree we don’t want “less correct” (out-of-date, etc.) data in OSM. We leave to the judgement of the Contributor whether data which are imported or curated from official sources IF those sources are of high enough

Re: [Tagging] Tagging Cycle Route Relations vs. Ways

On 17/11/2020 18:56, stevea wrote: I've found published data (from the authority authorised to amend the route) are often too inaccurate, out of date or lacking in detail to warrant transferring to OSM. Then, don’t import, curate or transfer them to OSM. I don’t believe we want "inaccurate,

Re: [Tagging] Tagging Cycle Route Relations vs. Ways

On Nov 17, 2020, at 7:43 AM, Seth Deegan wrote: > A contributor can obtain data from many different sources within each > changeset. Pushing the tag to the changeset meta data invalidates it's > limited usefulness when added to individual objects. > > Exactly. I never said to NOT use source=*

Re: [Tagging] Tagging Cycle Route Relations vs. Ways

> > it does an OK job of this: click the History button to get a > recent-around-here list of 20 edits (click the Load More button for 20 > more…and again and again if you like). > Yes, the History button does do a good job. But I'm talking about this: Clicking on one specific changeset will

Re: [Tagging] Tagging Cycle Route Relations vs. Ways

The classic case for a "source" tag is for imports. It's useful to know that something came from a TIGER import, or from some public database or wherever. I think source=* makes sense when the data is literally coming from some defined external place. On Tue, Nov 17, 2020 at 10:36 AM Dave F via

Re: [Tagging] Tagging Cycle Route Relations vs. Ways

On 17/11/2020 03:09, Seth Deegan wrote: May I ask why not source=*? TBH. I'm not a fan of the tag. I don't think it adds much value. It's too subjective/variable, but... It relates to the individual contributor editing individual objects. A contributor can obtain data from many different

Re: [Tagging] Tagging Cycle Route Relations vs. Ways

sent from a phone > On 17. Nov 2020, at 06:23, stevea wrote: > > to the degree they can be displayed in a narrow column on a web page yes, this is basically broken since the redesign (maybe 2012?), the history view used to provide a clearer overview on the full width, and this is

Re: [Tagging] Tagging Cycle Route Relations vs. Ways

On Mon, Nov 16, 2020 at 08:25:43PM -0800, stevea wrote: > On Nov 16, 2020, at 7:09 PM, Seth Deegan wrote: > > May I ask why not source=*? I know it's basically depreciated, but many > > times I find myself wondering where past mappers got the info for a route > > (this happened just today). I