[OSM-dev] Hello World

[Matt Amos]

On Fri, Oct 12, 2012 at 6:14 PM, Michal Migurski <mike at teczno.com> wrote:
> * Improved relation + data model support in a editors, either a new one or a retrofit onto Potlatch. Things like route relations or addressing schemas are important, for example, and should see the same kind of first-class support in an editor that the primary/secondary/etc. road schema does. It's time for these higher-order features to come out of the lab.

another item, if i may add to your wishlist, is turn restrictions;
there's already some special-purpose support for this in JOSM and
Potlatch 2, and i think it's something where a little more work could
really help reduce the complexity of adding and maintaining these
features. they tend to be found around complex junctions and there
have been many ideas in the past for what a UI specifically for
junction editing might look like (for example [1]).

> * Better time-awareness in planet dumps. I want to see a "days since last edit" or similar attribute on all entities in the planet file, which will make it possible to create downstream displays and styles that address hot, contentious information. We're starting to see two tiers of OSM data consumers, those who want the latest-newness and those who want to treat OSM like a slower-moving data source.

please could you explain a little more? i think perhaps i've
misunderstood what you're asking for. all nodes, ways and relations in
the planet file have a timestamp, and the planet has a date header
that would allow the calculation of "days since last edited". would
you like this information on the sub-elements (tags, nds, members) as
well?

> Stepping back, the story of OSM *is* that things happen in other tools, so I'm in agreement with Paweł Paprota that Mapbox should "build something that needs JSON support, filtering and tag API" before those features get fed into the core infrastructure. The minute diffs support the ability to develop real, working systems in an offboard manner, and I think we should take advantage of that.

and systems developed in this way are loosely coupled to the rails
code and main database, making it easier to admin and scale these
services later without adding complexity to the rails code. in my
opinion, it's a huge advantage.

cheers,

matt

[1] http://www.slideshare.net/yutik/mapzen-junction-editor