[Talk-us] Brainstorming an Import Tool

Joe Woycke woycke at gmail.com
Tue Aug 17 16:31:44 BST 2010

the reason to give the data to them is to make it more available to the
public.  there are many benefits to local governments sharing data such as
economic development and the fact that the people who paid for that data to
be created (the taxpayers) are most likely to consume that data through
public outlets such as google maps.  the esri community maps are very
different from osm.  the entity posting the data retains ownership and
control of the data.  this makes it very simple and easy to manage.  five
different entities can have five different versions of the same road.  there
is no synthesis of data.  google is similar in that they are looking for the
best data that they can get so the most people come to their site.  they are
working off of the assumption that the smallest govt will have the  best
data.  again very simple and very easy to do.  they pick the "best" data set
and run with it.  osm is about creating a community.  if osm chooses to
exclude the local govt and refuse their data they will lose out on a rich
data source that is better than the tiger data that osm currently uses as
its base data.

at the very least, i think that we need to find a way for local govt to
replace the tiger data with their data.  that will still present some
problems with connectivity and formatting but those should be doable.  i say
this as both a local govt geographer and an osm enthusiast.

On Tue, Aug 17, 2010 at 10:58 AM, Ian Dees <ian.dees at gmail.com> wrote:

> On Tue, Aug 17, 2010 at 9:42 AM, Lord-Castillo, Brett <
> BLord-Castillo at stlouisco.com> wrote:
>> Once I get our data uploaded into ESRI Community Basemaps (which is a
>> simpler process, has technical support, and will accept and integrate our
>> authoritative data even without an editor community), I'm going to have to
>> make a choice whether our public maps will continue to use OSM. If
>> significant barriers are made to our agency being able to upload or edit,
>> that will be an easy choice. ESRI and Google are both actively recruiting
>> data uploads with offered support. I don't think it is wise to go the
>> opposite extreme with actively refusing uploads.
> We are not refusing edits, but Frederik makes a good point: we've seen that
> imports stifle community mapping in other areas. One of the groups of people
> OSM is trying to attract are regular, non-GIS folks that usually are
> passionate enough about getting their area correct that we end up with data
> that is more complete than anything a paid GIS analyst can do.
> That being said, the GIS community is definitely another segment of the
> population we should attract so that our community can learn and grow from
> your input.
> However, you should realize that ESRI Community Basemaps, Google, etc. all
> have a *very* different mission than OSM. Google wants to get your data so
> that they can have a more accurate map so that they can sell more accurate
> (read: expensive) ads. ESRI wants to get ahold of your data so it can sell
> more Arc products. OSM wants your data to have a better map and to give it
> out to whoever wants it.
> It is my understanding that once you send data to either of these places,
> not only can you not edit it, but you can't get it back out. Also, there's
> no community updating your data, so what's the point in giving it to them
> (other than legal obligation)? Why not just keep your data in-house and edit
> using your own in-house setup?
> It boils down to what you want out of your data upload. Are you offering
> your data as an improvement to data that exists in the system already? Are
> you hoping to get community-based improvements sent back to you? Are you
> trying to supplant your $20k+ GIS system? OSM can offer solutions for some
> of that, but the bottom line is that we don't want this new data to harm our
> already-fragile community in the US.
> _______________________________________________
> Talk-us mailing list
> Talk-us at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/talk-us
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20100817/a62e8d00/attachment.html>

More information about the Talk-us mailing list