[Imports] Latitude and longitude tags and other TIGER 2009 import issues

[jamesmikedupont at googlemail.com]

I have encounter tags like this :
 county_import_v0.1_20080508235449
 county_import_v0.1_20080508235452
 county_import_v0.1_20080508235456
Which are not very useful to have such a long string. Do we really
need the exact timestamp or would it be better to tag the changeset?
mike


On Tue, Dec 29, 2009 at 11:11 AM, Alan Mintz
<Alan_Mintz+OSM at earthlink.net> wrote:
> Some import(s) have included latitude=* and longitude=* tags on nodes they
> imported. Is there any reason for these, or should I remove them when I see
> them?
>
> They seem to be mostly (all?) on imports of TIGER 2009 data, which has a
> couple other apparent issues[1]. I looked at one node, contacted the user
> named in the changeset and got a reply that did not lead me to think that
> they intended on fixing the issues. I don't know if there was just one
> user, or multiple users have used the same script somewhere. If the latter,
> the script should be fixed, too, right?
>
> Is there a generic "fixbot" that can do these kinds of tasks? Is there one
> running somewhere that can be given fixes of this type?
>
> [1]Source=TIGER2009 should be source=TIGER2009 (or maybe just
> source=TIGER09 to save a couple chars while we're at it) and Tiger:MTFCC
> should be tiger:MTFCC.
>
> --
> Alan Mintz <Alan_Mintz+OSM at Earthlink.net>
>
>
> _______________________________________________
> Imports mailing list
> Imports at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/imports
>