Hi,
Just wanted to put my 2 cents on on this.
OSM already has a rough consensus on its relationship to external data
sources. I don't think there we be any controversy saying no thank
you if somebody showed up wanting to import a shape file containing
the habitat of say black bears. We don't
Hi,
On 17.12.2012 18:47, Serge Wroclawski wrote:
I'm suggesting a different approach, one where you have a proposed
importer saying I have this data, they then take it to a
committee/working group who has been blessed by the community to help
with this process.
I'm keen on the import process
To me, imports are any bulk transfer of data from an existing data source
into OSM. They can be big (10's of 1000's of nodes) or small (10-40 nodes);
they can be mechanized, curated (reviewed by eye and hand), or otherwise.
I'm not sure a different name will help other than to create a faux
On Mon, Dec 17, 2012 at 9:42 AM, Serge Wroclawski emac...@gmail.com wrote:
[...]
So I'm proposing a new committee, run by the US Chapter, to help guide
imports and large edits.
[...]
What do folks think?
Excellent idea and a good time to do it. Cleaning up the wiki around
US-related
On 12/17/12 9:42 AM, Serge Wroclawski wrote:
When I helped create the US Chapter several years ago, this was one of
the main reasons I thought it should exist, but I think there's
finally the amount of data and interest to justify it.
What do folks think?
i think it's a necessary step, thanks
Interesting idea… trying to wrap my mind around this.
On Dec 17, 2012, at 9:42 AM, Serge Wroclawski emac...@gmail.com wrote:
So I'm proposing a new committee, run by the US Chapter, to help guide
imports and large edits.
What specifically would this committee (or point person or whatever it
Two more quesions just came to my mind:
- Are there any volunteers who would love to run with guiding imports better?
- Would also love to learn Jason Remillard's perspective of what could be done
better given that he's in the middle of working on the MassGIS building import
:)
On Dec 17,
On Mon, Dec 17, 2012 at 6:42 AM, Serge Wroclawski emac...@gmail.com wrote:
This will give step by step guidance to those who want to import data,
and offer the larger community time to review and provide feedback.
On Mon, Dec 17, 2012 at 7:16 AM, Josh Doe j...@joshdoe.com wrote:
Excellent
Alex,
You're asking good questions. Instead of trying to answer them point
by point, let me try instead to give you a comprehensive answer.
The community (US and broader worldwide community) have issues with
imports. I won't rehash those issues now- we can do that another time
but what we have
Jeff Meyer wrote
On Mon, Dec 17, 2012 at 6:42 AM, Serge Wroclawski lt;
emacsen@
gt; wrote:
What is stopping these this from happening without a committee?
Probably nothing. Although a committee might not strictly be necessary, it
can give an additional boost of motivation and sense of
Serge,
This is a good idea.
I have a large file of data from the Acoma tribe, but my
efforts to negotiate the import wiki have been fruitless. I can't
made heads or tails of it.
Further, I don't know if it's the kind of data we want
(though they say it is public domain
Hi,
On 17.12.2012 19:55, Kai Krueger wrote:
it is great to see if technically capable people deeply routed in the
community take charge of the import process to ensure that they are done to
the highest technical standard
That is one thing. Another thing that will usually distinguish an
The result is that folks like myself and others are frustrated by the
import process, and folks who have good, useful datasets are frstrated
by the import process.
[import/mechanical-edit committee proposal]
I agree with your broad sentiments.
Having observed some recent discussion, I
Hi,
There are some technical issues that make imports more complicated
than needed. First is the entire user account thing. I don't
understand why it is needed. If something gets screwed up, either way,
we are reverting the change set. Besides discouraging people form the
import, I don't know we
On Mon, Dec 17, 2012 at 9:15 PM, Jason Remillard
remillard.ja...@gmail.com wrote:
If you setup a user group to help with the imports, I think it will
be overrun with people that don't like all imports or are terrified of
them being screwed up.
I haven't received any negative feedback about
Hi Serge,
You are tougher man than me :-)
How about this, nobody on the committee that has not personally done
at least 1 large import. If you do that, I am happy. Like I said,
these imports require a bunch of specialized skills, it would be good
to build up an expertise in it.
Thanks
Jason.
Hi Serge ,
I am sorry for being negative. I am feeling grumpy from the building
import ruckus, I probably just need to take break from this for bit.
The US import process is clearly borked right now, and I will support
110% you and anybody that is trying to fix it. Please ignore my
snarky
Jason -
Would you be interested in joining the import / large edit committee? Given how
you just went through a pretty ad-hoc import process it would be great to have
your concrete input.
I'm seeing this committee as preliminary and exploratory. We don't have the
answers yet. I'd love the
18 matches
Mail list logo
