[OSM-dev] 0.6 api - same story

Brett Henderson brett at bretth.com
Mon May 5 12:42:21 BST 2008

Hi All,

I suspect there will be a significant database schema update to go along 
with this.  Moving node tags into their own table is a decent change in 
itself.  I couldn't see anything on the new 0.6 API page describing any 
of this.

My main interest is from an osmosis perspective which is under the 
"further, less important stuff" heading.  Perhaps it's not a priority 
now, but I'd hope we can continue to have daily, hourly and minute 
changesets running at the point of cutover.  If the aim is to deploy 
over the next few weeks this might be a problem, my time is fairly 
limited at the moment.


Tom Hughes wrote:
> In message <20080505074600.GB4302 at jafshome.irule.be>
>           bvh <bvh-osm at irule.be> wrote:
>> On Mon, May 05, 2008 at 10:49:37AM +0200, Martijn van Oosterhout wrote:
>>> The hackathon has been in the wiki for a while now. We had the major
>>> potlatch/JOSM/API coders all there. It's all change monitoring and
>> And this is exactly my point : I am using the API in Merkaartor
>> probably just as much as JOSM. Sure, it has no way near the impact of
>> JOSM or potlatch. But really, would a few mails on dev@ hurt really
>> that much to help api writers who are not 'major'?
> The hackathon was deliberately kept a little low key I believe as
> we wanted to keep the number of people turning up to a manageable
> number otherwise nothing gets done.
>> In fact, if OSM as a project is interested in attracting novel
>> ways of interacting with the API (still the goal, yes?) it should
>> focus on making the project accessible for the _minor_ coders
>> rather than for the established coders who are less likely to do
>> groundbreaking stuff.
> The API is not going to change without giving people a reasonable
> amount of notice.
> The code isn't even complete yet, and then I have to start thinking
> about deployment issues and scheduling the necessary downtime which
> will need notice itself. All in all it is going to take a number of
> weeks before anything happens.
> Tom

More information about the dev mailing list