[Imports] Fwd: [Talk-us] Import of EPA data

[Chris Hunter]

Looks like this didn't go through to the Imports list first time.

---------- Forwarded message ----------
From: Chris Hunter <chunter952 at gmail.com>
Date: Fri, Dec 18, 2009 at 2:09 AM
Subject: Re: [Talk-us] Import of EPA data
To: talk-us at openstreetmap.org, imports at openstreetmap.org


Mike,

I just had a look at another area of the map in my neck of the woods, and
I'm increasingly of the opinion that this data needs to be bulk deleted *
*ASAP** before more users start trying to correct it.  I realize you've put
a good amount of effort into trying to write a script to retro-actively fix
the data, but with all due respect, you're wrestling a WOMBAT.

I'm also cross-posting to the imports list to see if they have any
suggestions as to how best to handle the data.

Again, I respect the time and effort you're putting into using this dataset,
and I do feel that it would be useful to re-import once a review and a set
of tags are agreed on.

Sincerely,
Chris (DiverCTH)


On Thu, Dec 17, 2009 at 12:42 AM, Chris Hunter <chunter952 at gmail.com> wrote:

> I ran across 2 misplaced / not immediately locatable points while mapping a
> local airport.  Since I agree with David's take, I have deleted both.
>
> Changeset: http://www.openstreetmap.org/browse/changeset/3391401
>
>
> On Wed, Dec 16, 2009 at 10:00 AM, David Fawcett <david.fawcett at gmail.com>wrote:
>>
>>> I don't support the import at this time either.
>>>
>>> I think that this type of data is far better queried from the source
>>> at the time it is needed and mashed on top of OSM.  States are
>>> continually improving this data and pushing it up to EPA where the
>>> changes will be reflected in new versions of the KML file.  Is it
>>> likely that OSM contributors will create diffs and hand edit the
>>> locations and attributes as they change?
>>>
>>> If data like this is imported, it should not be done without a well
>>> thought out tagging/description scheme that others buy into for
>>> environmental data.  These tags should indicate the type of
>>> environmental interest that it it is and if it is from a particular
>>> EPA program, it would be very useful to use namespace specific tags
>>> like type=epa:npl, type=epa:brownfield, etc.  Maybe a standard OSM tag
>>> to indicate that the location has not been verified, like the tiger
>>> data.
>>>
>>> Personally, I think that if it is there, it should also be tagged in a
>>> way that it doesn't show up on the default renders.  An interesting
>>> project would be something like 'OpenEnviroMap'  (ala OpenPisteMap), a
>>> stylesheet and tagging scheme to pull all flavors of environmental
>>> info into a map.
>>>
>>> I don't understand what the rush is to put 100k of points into OSM
>>> without the proper work up front.  In IT-speak, you seem to be heavily
>>> invested in a solution without having done the business analysis or
>>> established the business need.  I guess that is the beauty:horror of
>>> OSM, it is a wiki, anyone can import whatever they want, however they
>>> want.
>>>
>>> I am starting to repeat myself in these posts, so I really don't think
>>> that I have anything else to add to this discussion.  If your goal is
>>> to add value to the data or make the latest version of data available
>>> to people who currently don't have access to it, I don't see the case
>>> for putting it into OSM.  What is your goal behind this effort?
>>>
>>> David.
>>>
>>>
P.S. WOMBAT = Waste Of Money Brains And Time
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/imports/attachments/20091218/9fc2e1de/attachment.html>