[OSM-dev] GSoC - Data Tile Service

Peter Körner osm-lists at mazdermind.de
Mon Jun 11 11:37:07 BST 2012


Hi

Am 10.06.2012 18:03, schrieb Michael Daines:
> I have been documenting the data tile format from the Kothic project (including the details of how map features are cropped, etc.) which is at present what the data tile format I am working on will be based on. I am also working on describing other schemes for cropping OSM data, and other JSON representations of OSM data.
Is this documentation-draft published somewhere? Would really like to 
take a view into it.

> I will post this work (the documentation and the tile production script and web testbed) on the wiki and in a GitHub repository in the coming week.
Ahh, forget my question from above ;)

> Finally, I have been working on a script for producing augmented diffs (as suggested a little while ago on the list by my mentor) by querying the Overpass API, meant to make keeping a replica of the planet up to date with minute diffs more tenable in the face of data processing speed and the possibility of missing data and broken geometry. An initial version is here:
Isn't this a totaly unreleated project? Although its more interesting 
then a Tiled-Data-Service to me :) Despite that I'd strongly vote for 
NOT using Pverpass-API, because of multiple problems that could arise 
from this dependency:
  - Overpass API is a important tool for Individuums to get specific
    data they're interested in. It's no good idea to occupy that api
    with another service
  - It's no good idea to provide a service that depends on another
    service that is not maintained by you.
  - Your tool yould be a lot faster when you base it on a specialized
    database and not on a generic api

I think it would be far better for an diff-augmentation-server to hold 
its own specialized database, optimized for the single job of augmenting 
diffs. (remember: preprocessing is everything in the osm universe)

Peter



More information about the dev mailing list