tmcw has commented on the following diary entries

Post When Comment
A year with imagery offset database 5 months ago

To be clear: we'd be happy to accept a pull request that adds support to iD, as stated in June of 2013. Nobody has stepped forward with code to do that, so it hasn't happened. Anyone who can write it and submit a pull request can make it happen today.

New users shouldn't be allowed to delete a lot of data 7 months ago

Do any of the editors warn you if you try to upload a change that includes a lot of deletions?

The answer is yes. Here's iD's implementation.

GeoGit and GitHub Geo about 1 year ago

Fwiw, I'm pretty bearish on GeoGit, for a number of reasons.

Java is a poor choice of basis - your contributor base is small and userbase has to deal with Java-isms. The 'multiple backends' concept makes performance and potential hard to pin down. The military-fund-for-open-source model of project management often produces incomprehensible software (see: GeoPackage). The GeoGit model is, like Git, more or less a glorified hash table whereas OSM is at its core not a list of features but a graph database, and the graph-ness of this graph database makes the idea of versioning it fundamentally different than a shapefile or PostGIS database. The lack of opinion in terms of datatype means that operations will be lossy and non-pure for quite a few datatypes, unless GeoGit's internal format is a superset of all geospatial data formats. And there's no real solid answer for how GeoGit will scale to OSM, even if the bottleneck of database throughput is removed.

That's not to say that I disagree with the intent - nearly everyone agrees with the intent, and wants something-of-this-sort.

overpass turbo goes – translators seeked about 1 year ago

Awesome! Nice work

Guided Tagging by an interpreter of XML-formated rules almost 2 years ago

Hey all,

From the iD side:

We currently have a brainstorming ticket about presets. It'll be one of the main objectives after we tag an alpha1 release.

Some prior art here: JOSM & Potlatch both have formats for exactly this: JOSM and Potlatch implementations.

We're also making strong use of Taginfo, which through its API can provide recommendations about related tags. This also provides an API for wiki-sourced documentation of tag combinations, including thumbnail images.

When we do implement presets, it's likely to be in a simple JSON format: XML parsing in Javascript is not very efficient or simple.


New Look almost 2 years ago

Last iteration was by the very talented samanbb!

Animated dataviz of OpenStreetMap edits per year almost 2 years ago

Very cool, this does a great job of highlighting where we need to focus outreach. Thanks for doing this.

1 Million Mappers Soon ... No, Not Really almost 2 years ago

As butrus_butrus said, this isn't a very reasonable solution - my account was idle for more than two years, and now I'm rather deeply involved in OSM.

If the problem you're trying to fix is misleading 'users numbers', the solution is to publish 'active users' numbers alongside.

Test driving iD almost 2 years ago

There's also the hosted demo version which updates every 10 minutes if you want to test without having to clone/view locally!