tmcw has commented on the following diary entries
|GeoGit and GitHub Geo||7 months 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 geojson.io – translators seeked||7 months ago||
Awesome! Nice work
|Guided Tagging by an interpreter of XML-formated rules||about 1 year ago||
From the iD side:
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.
|New Look||about 1 year ago||
Last iteration was by the very talented samanbb!
|Animated dataviz of OpenStreetMap edits per year||about 1 year 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||over 1 year 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||over 1 year ago||
There's also the hosted demo version which updates every 10 minutes if you want to test without having to clone/view locally!