OpenStreetMap
Idea: export the entire data storage of openstreetmap osm into wikipedia on git. Use cached rendered pages checked in. all layers generated by local layers from json data.
ߊ߬ ߟߊߦߟߍ߬ߣߍ߲߬ ߦߋ߫ h4ck3rm1k3 ߓߟߏ߫ 19 October 2009 ߦߋ߫ English ߟߋ߬ ߘߐ߫Idea: export the entire data storage of openstreetmap osm into wikipedia on git. Use cached rendered pages checked in. all layers generated by local layers from json data.
check my new video on svn-git
full video 1:5h introduction to git-svn for Subversion/SVK users and deserters http://www.archive.org/details/SvnGitVideo
Discussion
ߡߙߌߣߊ߲ ߞߊ߬ ߝߘߊ߫ TomH ߟߊ߫ 19 October 2009 at 12:39 ߘߐ߫
Are you completely insane?
ߡߙߌߣߊ߲ ߞߊ߬ ߝߘߊ߫ wallclimber21 ߟߊ߫ 19 October 2009 at 19:45 ߘߐ߫
Maybe you should first explain what problem you're trying to solve?
ߡߙߌߣߊ߲ ߞߊ߬ ߝߘߊ߫ eAi ߟߊ߫ 19 October 2009 at 23:26 ߘߐ߫
I'd almost say this was auto-generated spam....
ߡߙߌߣߊ߲ ߞߊ߬ ߝߘߊ߫ h4ck3rm1k3 ߟߊ߫ 20 October 2009 at 06:36 ߘߐ߫
No spam, listen.
let me explain myself. I am thinking about a distributed git repository for openstreetmap.
Imagine you would get all your data needed via git, and would communicate with others via commits to git.
this would be distributed to other people.
even tiles would be rendered and checked in, maybe to a different area but with the same naming scheme.
you wont need a central database, you could add the names to a central index file that is also in git. So basically you would get away from a central database and import and export.
The other tools could be made to run off of these static pages by embedding code/data in the page that would be executed/evaluated when needed.
this would work via richer clients and allow mapping to be done by a peer to peer sharing load sharing system.
mike
ߡߙߌߣߊ߲ ߞߊ߬ ߝߘߊ߫ Gnonthgol ߟߊ߫ 20 October 2009 at 08:37 ߘߐ߫
We have a central database and a CVS. Why use git? There are no problem with how things are done today.
And there are far to much data to use a distributed repository. You might use a DHT if you insist on distributing the data but the lookup time would be to long.
The best way to handle the huge amount of data is with a central database.
ߡߙߌߣߊ߲ ߞߊ߬ ߝߘߊ߫ h4ck3rm1k3 ߟߊ߫ 20 October 2009 at 08:41 ߘߐ߫
I am thinking of local servers, layers of them working together to map the world.
each local team would have its own central server that is pulled from bigger and bigger servers until we get the central one.
the local servers could run a database and gui instance, and have the rendering tools.
git allows the raw data to be stored, and stores only unique ones.
if you put the small enough files of data on there, only the unique ones will be stored, nodes and ways as files for example.
ߡߙߌߣߊ߲ ߞߊ߬ ߝߘߊ߫ Gnonthgol ߟߊ߫ 20 October 2009 at 19:44 ߘߐ߫
But still why? What advantage does we get?