(Your English is obviously better than you show here. These posts would convey a lot more if you stopped using a faux German/English mix.)

You begin your post with a picture and by saying “It is big problem.” Can you be more clear about what you view the problem to be? I’m assuming you see some conflict of interest in our OSMF board members? If you see such a conflict, then run against them or convince others to replace them.

Having a diverse group of board members is a good thing. Each of them are members of the community in various ways while at the same time some of them are using OSM data in their business. This isn’t a bad thing.

Have you tried looking through the videos that people have made to describe how to use OpenStreetMap? Try looking through some of these videos. Emacsen’s videos near the top of the page are particularly helpful.

You want to look at this graph in particular. Usually those values are in the 0-100 range and as you can see the "dirty queue" is very high. This is usually from someone uploading large amounts of data or making changes to an object that touches a wide area on the map.

Another possibility is that your browser is caching older tiles. Try clearing your browser's cache and/or restarting it to force new tiles to be fetched.

The "Browsers" you clumped together are almost exclusively faked User Agents. Most of the User Agents for real browsers are relatively unique and won't end up grouped together.

The sysadmins have been contacted by or have contacted themselves several of the tile downloading clients. If I remember correctly one of the app authors even made a donation to OSMF that helped pay for the SSD in yevaud.

Thanks for running and talking about this Harry! It was tons of fun. I totally would have won if I didn't have the Summer of Code stuff :).

Paul, although this is off-topic, Google is very unlikely to ditch MapMaker for OSM due to 1) they spent a bazillion dollars on MapMaker and 2) the OSM license prevents them from using it alongside some of their data

Ah, sorry. It looks like Pink Duck did the searching. I'd be interested in hearing from the original poster where they saw offensive words. I don't think we should completely "cleanse" the project of potentially offensive words, but I do think people should feel comfortable showing OSM to kids.

It sounds like you performed searches on our wiki for words that you feel might be offensive. The pages you linked to are difficult to find and would most definitely not be touched by any students in a Summer mapping project.

The beauty of OpenStreetMap is that you can map using our tools without even looking at the wiki. I looked through our editing tools and was unable to find any potentially offensive words. If you're not comfortable with that, you don't even need to have the kids directly edit: they can draw maps on printed maps and add the data later.

MapDust's interface is so slow and there are so many invalid bugs that it's worse than useless... Lots of noise and very little signal.

Do you have any other, more-concrete backing for your claim? I looked at Google MapMaker history up and down Hwy 26 and the only change since the original data was generated was someone adding a bikelane flag to the road in April.

Also, there are plenty of businesses that use "Southwest Highway 26" as part of their address: http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=%22southwest+sunset+highway%22+oregon

OpenStreetMap's data is stored on servers owned by the OpenStreetMap Foundation, not on any Google servers.

********THIS IS NOT A GOOD PLACE TO MAKE BUG REPORTS************. Do that here: https://github.com/iandees/xapi-servlet/issues

"Is there no standard way to do anything here?"

No, there isn't, and that's why the project has been so successful so far. The community has landed on some consensus for ways to do the things you're talking about (multipolygon relations for buildings with holes in them, the Karlsruhe Schema for addressing, etc.), but the beauty of OSM is that there is no standard to read, no 500 page "mapping requirements" document, etc.

********THIS IS NOT A GOOD PLACE TO MAKE BUG REPORTS************. Do that here: https://github.com/iandees/xapi-servlet/issues

This is not a good place to make bug reports. Do that here: https://github.com/iandees/xapi-servlet/issues

@Tilo: No, the jxapi is/was not down. It was getting inundated with duplicate requests so the process queue was very long. I restarted postgres to clean out the queue.

I compute the sum of the areas of the requested bounding box(es) and compare that to 10. If larger, 500. If less, let it through.

There are no plans to do areas larger than 10 square degrees. As you can see already the hardware has a hard enough time keeping up.

@Katzman:

1. It is possible to enter multiple tag predicates:

[amenity=foo|bar] := "amenity"="foo" OR "amenity"="bar"
[amenity|leisure=foo] := "amenity"="foo" OR "leisure"="foo"
[amenity=foo][area=bar] := "amenity"="foo" AND "area"="bar"

2. Not at this time.

Your map is still incomplete: the majority of power station/sub_stations are mapped as areas, not nodes. At least put a dot on the map for the first node in such a polygon. Also, as others have mentioned before there are plenty of power=line that don't have power=[tower/pole] marked on their nodes (since it's so tedious in all the editors).

MapDust is littered with so many bugs that are not reproducible I don't waste my time with it anymore. The last few times I visited I spent more time clicking through the process of closing a bug than actually fixing the data, so I gave up and continue to map my area as perfectly as I can.

I recommend making a post to the imports mailing list (to answer your projection question) and follow the import guidelines found on the wiki.