[OSM-dev] Proposal: Database accelerator and dirty tile marker based on simple algorithm.

[Joerg Ostertag (OSM Munich/Germany)]

On Monday 18 September 2006 19:52, David Sheldon wrote:
> On Mon, Sep 18, 2006 at 07:14:00PM +0200, Lars Aronsson wrote:
> > What part of GRASS is not applicable to OSM?  Their way of doing
> > quad trees is not useful for us?  So we have to write our own?
> > Their way of doing quad trees is only useful for proprietary data,
> > and to create free geodata OSM has to reinvent all the algorithms?
>
> Their website looks like GRASS is a GUI application. Are you suggesting
> that we cut and paste from their source, or is there a library hidden
> somewhere? 

As what I understood; Basically GDAL/GRASS is a set of libraries for raster 
and vector graphics which have example application (the gui, the commandline 
interface) to work with.

> Does it talk to mysql 

If it does it would be great. I havn't checked yet, but I wouldn't be 
astonished.

> and store history

This might not have been in the focus of the grass/gdal developers. But I'm 
not sure.

> and meta data of all the points? 

I think this shouldn't be a real problem for a real GIS library. So probably 
yes.

Not knowing all these questions; This was the reason I asked Lars for helping 
out in pointing us more precise how he thinks we can integrate GRASS into 
OSM. As what I understood from GRASS it has a lot of functionality which 
would bring us forward towards a real GIS system. But we really need someone 
who knows GDAL very well or is willing to read into it to know how to use its 
powerful skills.

-

Joerg

who is honestly excited to hear how we can use GRASS to save a lot of 
developer work