[Imports] Introducing OSMLY

Jason Remillard remillard.jason at gmail.com
Sat Sep 21 15:14:25 UTC 2013

Hi Aaron, Serge

In Aaron defense, before this thread, it would not have have occurred
to me to use Maproulette for an import.

We seem to have two flavors of community imports right now. The first
style, (Seattle, DC and NY city), has the QA, conflation, and
uploading done directly by mappers. It looks like your tool is
designed to support this style. The second style, has the community
doing just the QA on "finished" OSM files, with the prep, conflation
and uploading being automated. Do you anticipate that OSMLY would be
useful for both kinds of imports?

When you are ready, propose your import. I look forward to seeing how
it works for real.


On Fri, Sep 20, 2013 at 12:53 PM, Aaron Lidman <aaronlidman at gmail.com> wrote:
> Hi Serge,
> Yup I've been keeping an eye on the Maproulette rewrite, I was just working
> on this before you guys started. We'll see, maybe I can help out somewhere.
> Your concern:
> In no way do I want to change the proposal or approval process for imports,
> those are in place for good reason and I will totally work within them. This
> is simply another tool, like JOSM or any of the import scripts, for
> completing those imports that have been approved and discussed. If there was
> some official means to parse a list of active approved imports that have
> been sanctioned by the DWG, I would love to force OSMLY to only allow those
> imports on the live OSM server.
> On 9/20/13 5:08 AM, Serge Wroclawski wrote:
>> Aaron,
>> I have a number of thoughts about your tool.
>> First, the good:
>> This is great. It is very similar to the work Martijn and I have done
>> with MapRoulette. MapRoulette can essentially do what this tool does,
>> so there wasn't really a need for yet another tool. In fact, my only
>> complaint is that I wish you had decided to help us work on
>> MapRoulette and include more features, rather than go off and make yet
>> another tool in a very fragmented community. Nonetheless, this is very
>> nice.
>> The concern:
>> My concern is less about the tool than the technique. Just because a
>> user has a tool to assist them does not mean that the import can
>> bypass the normal community process. While this isn't directly related
>> to the software (and we never want to blame tools for how they're
>> used), I still worry about imports happening without due diligence.
>> Overall, I'm glad this exists, though I'd be much happier if you
>> helped us with MR, which can do this and more. :)
>> - Serge
> _______________________________________________
> Imports mailing list
> Imports at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/imports

More information about the Imports mailing list