Hi list
I'm not sure if there's an import or some mass editing going on right
now, but the minutely diffs are running between 100 and 200KB of
gzipped data.
I'm not sure if the solution is to throw more hardware at it,
or if there are tuning issues with the TRAPI code
since the database has grown so much since it was written.
So..I'm not a newbie but have not very long been active with OSM.
My main parts with OSM is
- having a t@h-client
- mapping
- fixing errors with keepright.imax.at
Well, you say the database has grown. How about with optimizing the
database?
Look at this:
http://www.openstreetmap.org/?lat=40.3320980072021&lon=16.7644929885864&zoom=14
Way 87854044 (railway)
A straightaway line with wasting 19 points. 2 points would do the same
for this single straight line.
This is for me a deal why the database grows. There are too many
useless points..
Are there some tools which could detect this?
if there were a tool like keepright but for this type of erros we could
optimize the database by deleting useless points.
What do you think about my idea?
I'm not a programmer and I don't have access to big servers. So I can't
develop t@h further.
But I would be willing to correct such types of errors (I'm already
doing this when I see them)..
Kind regards
Daniel
_______________________________________________
Tilesathome mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/tilesathome
