Hello.

Ich did a redraw of previous image.

Answers to some points:

@quantumstate: moving license change upwards will not help. If some one wants to import Google Maps data, it is fine to make converter. And make sure all tags are wikidescribed. But not fine to upload, which ist marked. If person can not look ahead on the list she deserves that.

@Gnonthgol: linear path ist for easy understaning. To make sure nothing falls off out mind. Before upload, you look at this again and check whole process following the arrows.

@LivingWithDragons note about revert ist from original import guide lines.

Ich think about giving numbers to blocks for easy reference. Need make sure community do not want add more blocks so numbers do not change.

Ich post link to this to talk@ and imports@ to discuss better.

Hello.

Multiple persons asked me to review import guidelines. I translated pages of text into this:

Comments? Ideas?

Diaries exist for 17 000 posts already. Happy Birthday OSM User Diaries!

I did small table for better understanding.

People in list above are respected. They did big contributions.

There was saying “OSMF doesn’t shape the community”. It now came to “OSMF has nothing to do with community”.

It ist not problem. Problem ist most influencive OSMF members have their own small business. They have to pay bills. And think of their company.

It is big problem.

You know why Frederik Ramm keeps upsetting himself of Database Bloat? GeoFabrik.de has low disk space. Not openstreetmap.org. OpenStreetMap only grows faster than his business. He even wants to delete buildings: http://osm.gryph.de/2012/06/openbuildingmap/

OpenStreetMap is changing licenz. Ist fine. But two months already diffs are not easy to set up, and no regular planet exists. It certanly gives more respect to GeoFabrik. Their extracts update daily. But it simply a way to remove competitors.

Look at license change bot.

https://github.com/zerebubuth/openstreetmap-license-change/commits/master

… See full entry

Some users asked me about importing ID tags. I tried to make a small scheme about that. Hope it is clear enough.

Comments? Ideas? Additions?

I want no offence. Forgive me if I speak wrong. I state my mind in best words I find. If I fail to find words please help me. Not say “go away and stop critics”.

I try to fix worst things. First I thinked they were tags. Trying to fix tags I found larger issue. I will no more fix tags without approval. I got idea of “Caring community preview” proposed by user Matt. I want not my posts to be read as “justification for unaccepted edits”. I want my edits accepted. But when unacceptance reasons are technical, I want fix technical reasons, not get “no do not just because”.

User woodpeck said “Ten guys like WorstFixer and we can fill a separate $15000 database server just with the likes of him”. Think: ten users can kill $15000 server.

I respect system administrators. They do good job.

But looks we have worse problem than database bloat. Database server IO load. I read wiki and munin. Here is how it looks it works.

… See full entry

I was told every edit creates database bloat. Here some drawings.

This is simple image showing how data circulates in OSM:

Why grey revert? Reverting store is cheap. “Version 1 is same as version 3”. You keep current version in current data base and just pointer in archive.

Look closer at archive and visible separation:

… See full entry

I am ready to discuss.

I listen to you attentively. I put notes.

Why no mailinglist post?

Won’t work. Ever. Maybe only if you write that to dead local mailing list. Where nobody reads anyway.

Have a look at our license change. Workflow #1. When the fuck will they finish?!

I propose alternative. It is not ideal. Nobody is ideal. But it will work. Because it needs people with editors. Not bureaucrats with mail boxes.

… See full entry

Problem of OSM is graphomania.

People want to write.

To write long books about openstreetmap.

To write long threads on openstreetmap. Even longer to prevent disputes.

… See full entry