[OSM-talk] Tagging the source

[Jérome Armau]

The only real problem I see mentioned above is the overall size of the
database. It seems to me that we are somehow confusing problems caused by
the data itself with problems caused by its storage in the database.
Couldn't we simply work on a scheme that would normalize the database, so
that we'd have to store each piece of information (e.g. "source" value as
well as all the other tags) only once? I haven't worked much around the OSM
pgsql database schemas, so it may not be as easy as I'd hope.

Jerome

On Fri, Sep 28, 2012 at 7:39 AM, Kevin Peat <k at k3v.eu> wrote:

> On 28 September 2012 15:13, Martin Koppenhoefer <dieterdreist at gmail.com>
> wrote:
> >
> > yes, but often when something is wrong, the source-tag is as well ;-).
> > I have seen lots of source=PSG (coastline) where the data obviously
> > was far too detailed to be from PSG, it is because people hardly
> > remove those (meanwhile unvalid) source-tags.
> >
>
> Agree on that. There is lots of UK data with source=NPE or PGS that
> has obviously been subsequently adjusted from Bing or elsewhere,
> probably done this myself many times and forgotten to change the
> source tag.
>
> That's why I would prefer some automation. If I have Bing and an OS
> based layer open and active in JOSM then I don't see a problem with
> automatically adding those as sources to the changeset. Those tags
> should then be visible when retrieving object history. Mappers could
> still override that with source tags on the objects if required.
>
> Kevin
>
> _______________________________________________
> talk mailing list
> talk at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/talk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20120928/15802fc0/attachment-0001.html>