Planet + diffs is the way to go. The availability of the diff does not impact the API so keeps the API for data contribution. I believe this approach will generally keep you within 6 mins of the live database.
You might look at osmxapi for how that service makes a near real time read-only dataset available in the same way. Others I'm sure will suggest other ideas and options. Cheers Andy >-----Original Message----- >From: [email protected] [mailto:[email protected]] On Behalf Of Jeffrey >Warren >Sent: 14 May 2009 4:07 PM >To: Andy Robinson (blackadder-lists) >Cc: Tom Hughes; [email protected] >Subject: Re: [OSM-dev] API 0.6 returns 403 forbidden > >Yes, thank you. I had looked for an API policy and had not found one... I'm >looking for bulk data but in fact live bulk data... working on a live >javascript editor/renderer. I have a planet dump but had avoided working on >it since the idea is to use data as it comes in. Is there a solution for >that that's sustainable? I'm not familiar with the diffs and changesets as >I've been focused on client-side work in the past week, but if there's an >efficient way to sync my planet dump with the live dataset I'd love to do >that. > >My understanding is that the planet dumps are done weekly, and downloading >changesets continuously seems not much better than hitting the API... I >suppose this may simply be outside the scope of OSM's available interfaces, >no? > > >Jeff > > >On Thu, May 14, 2009 at 4:46 AM, Andy Robinson (blackadder-lists) ><[email protected]> wrote: > > > one that includes the API as far as I can see. We should either add > > _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
