Editing bits of roads with loads of routes on them is extremely tedious. I had to remove two pieces of road from ~10 different relations and replace them with another piece of road.

There must be a better way to define routes than relations.

I've been adding some addresses.

I've been using nodes for the entrances tagged with the addr:*=* tags and building=entrance.

The reason for this is because some buildings have multiple "bits" in them. I've seen others dividing the building into smaller sections instead.

I'd say the node way is better, but I just wonder if it's good practice.

An idea that I saw on the mailing list (thank goodness I don't subscribe to that) was that of different layers of data. The idea would be choosing what "layers" of data you want.

Certainly it would make editing a lot easier as some areas are unwieldy to deal with.

Thinking about it, XAPI does (did?) this.

Does every road need to have a maxspeed tag? What methods do people use for collecting speed limits?

I've been looking through bugs on MapDust, there are rather a lot of fairly useless bugs with no description, but I've also fixed at least 3 genuine bugs.

Seems like a nice system altogether.

I've just requested mkgmap's packaging in Fedora. See https://bugzilla.redhat.com/show_bug.cgi?id=592645. Any advice is welcome

I think the United Kingdom label should be a wee bit higher, somewhere near Newcastle would be more central I think.

I have changed Great Western Road in Glasgow to be highway=trunk. Feel free to change the lower regions nearer to the centre of Glasgow to be primary again.

This was done on the evidence of green signs along the road instead of white ones.

I very much like Crschmidt's work on the data browsing thingy. That is all.

I have noticed that there are a lot of people joining OSM just now. Larger numbers are always a good thing, but I do wonder at this time whether the anarchistic model will suffice in the future.

Not only could there be vandalism like Wikipedia's, but the "tag how you wish" approach could prove to be confusing and wasteful.

I'd say that the next 6 months will be absolutely critical for OSM. The work ongoing in changesets and suchlike for the 0.6 API is a step in the right direction.

I welcome opinions on the future direction of OSM.

Originally the A811 was in OSM as highway primary. I noticed that some signs on it were green, so I changed it to trunk. SpeedEvil confirmed its primary route status.

Today, I noticed a part of it was back as primary, so I sent a message to the last editor. I hadn't noticed the note tag expaining Transport Scotland no longer consider it as a primary route. Sorry about that.

I think possibly the island names are a bit too obvious on the T@H layer.

Yesterday, I noticed a new sign on what I knew as Carseview Drive. It proclaimed the road was "Carse View Drive". I thought I may as well change it to the new name, but perhaps this wasn't such a good idea.

The new sign was placed high on a pole, you can guess why.

Whenever I hear of Armidale, I think of a small village on the Isle of Skye.

Just thought I'd mention it.

Looking at the region just north of the M8/M73 junction, I noticed a lot of ways that didn't connect to each other.

Just for a laugh, I have opened my passing_places proposal to comments. Have fun.

I noticed a lot of bad data in the Lochwinnoch region. Unconnected ways, nodes all over the place at ends of ways and using the same nodes twice in each way were all in evidence. They were all made with Potlatch.

All errors have been fixed now, but please be more careful in future.

Any name=fixme tags near Glasgow will be removed. I don't agree with adding incorrect data to make things to be done more obvious.

Good news on the green list, I've already used it to get the A811 fixed.

Playing with potlatch made me notice that Glasgow has Yahoo imagery. Nice.