Plenty of duplicate nodes still to be resolved in Texas too:
http://matt.dev.openstreetmap.org/dupe_nodes/?zoom=8&lat=31.65821&lon=-99.32729&layers=BT

It would have been good if these comments had been entered individually with each changeset rather than after the event :)

OS VectorMap District is due for release as part of OS OpenData in May 2010, in theory less than a month away.

It is not a beta, but a developer platform preview release - one every 2 months prior to the actual beta builds. It won't work on XP, so no improvement in standards for the current majority user base. If only M$ had started in 2004.

Obviously spam. I'd block this user if I could, except I can't. I'd remove the content from the blog page too, except I can't and no-one else seems able to.

I've long been pondering a way to get my GPS tracker above my head when walking for increased accuracy. It doesn't support an external antenna so the best I can achieve currently is holding it with an extended arm. I'd really like one of those Ordnance Survey GPS poles with sub-millimetre accuracy :)

I agree, spam.

Cunningly the spam links are in the Lokko profile, rather than the posting.

It is good in part since that dedication will turn you into a good OSM mapper and aid the project itself. Eventually you'll run out of nearby areas to map and will then switch to more detail locally or start to travel elsewhere. Generally the additional cost, editing boredom, tagging arguments and strange people that OSM attracts might help you shift away - but only once the area you can cover is perfect :)

I fully support the use of online web-based validation such as KeepRight! but also the validator plug-in for the JOSM editor which can check uploads before they get entered into the OSM database. I can't stress how important it is to have good quality data so that many thousands of people now and in the future can use OSM successfully.

I use the GT-31 too, though haven't experienced the freezes you mention. However, I have had data loss on power loss with the memory card logging option. I nearly always recharge it fully via USB after mapping trips in readiness for the next :)

A shop's door is the barrier for its opening_hours. When the barrier is no longer an issue the shop is open. Thus for bollards the opening_hours should reflect the time when access is possible.

It is best to map based on reality and raw data, not the way that it will be presented (which depends on the renderer in use). Thus JOSM is the client that gets my vote.

That should be http://nominatim.openstreetmap.org/

I have had several JOSM crashes over the year, mainly due to running out of Java virtual memory because of memory leaks in its code. It's very frustrating to lose edited data, though usually ends up much quicker the second time around to enter. I tend to save progress as an OSM file as I go, after completing significant areas. To reduce the risk further I close and reopen JOSM occasionally. You can also launch JOSM with command line parameter to increase the available memory to it, but that's can just prolong the inevitable.

How about highway=proposed and highway=dismissed?

Please always look for the reference code on postboxes and add with the 'ref' tag. This is useful, verifiable data that allows others to add additional information such as the collection times for a given box - using resources such as http://www.whatdotheyknow.com/request/postbox_collection_times

Be careful if doing for long trips, as then the track based collection will run out after 8,192 points (2 hours 16 minutes @ 1 Hz). The data logger will store 20,480 points (5 hours 41 minutes @ 1 Hz) but won't let you see them while you're travelling. Sadly I learnt this from experience after having gone for a 3 hour walk with just tracking alone. I now use a 2 GB SD card :)

Perhaps report this at http://josm.openstreetmap.de/newticket with an upload of the OSM file in question?

I wondered about this also to begin with. However, I reasoned that since paths are typically parallel to roads that they don't make for much of a navigational feature. I do add them where the path diverges from the road curb by more than a few metres though and where paths intersect roads at sharper angles. If you try adding paths beside roads as well as being a lot of effort it's likely that the close proximity means they won't render well either.