Only trackpoints are currently imported from uploaded GPX files - waypoints could be imported but nobody has got around to doing so yet and there are some issues relating to preprogrammed waypoints on some GPS models.

JOSM can display waypoints from local GPX files, which is what I normally do. I'm not sure if Potlatch can do that when it loads a whole trace - in theory it could but I'm no Potlatch expert.

It was a bug. It's fixed.

Exactly - the advantage of OSM is that you can fix it when it's wrong ;-)

This is a very complicated area - in theory the name of the street is a fact and not subject to copyright. It is however subject to database right in countries (like EU countries) which have that - database right protects a collection of data even if that data is factual and making a substantial extract (for some value of substantial) of that collection of data is not allowed.

In addition there is the problem that these mapping site will put in deliberately misnamed streets and things to detect copying - those incorrect names are arguably not facts and hence subject to copyright protection if you copy them.

The critical point however is that it doesn't really matter what the law actually says - if the site you are using wants to start a legal argument then we can't afford to defend ourselves so we have to avoid doing anything that might even possibly lead to such an argument.

I may have misunderstood you here, but if you're saying that you used other online maps to "identify streets" then I hope you haven't copied names or other information from those other maps into OpenStreetMap without first checking that the license on those other maps allows such copying.

Potlatch tells you in the top right hand corner whether or not it is currently loading data.

That command should of course be:

gpsbabel -w -i navilink -f /dev/ttyUSB0 -o gpx -F waypoints.gpx

Looking at the Highways Agency site, the B6420 has definitely been realigned to terminate on the eastern half of the new dumbbell junction, so that new alignment will need capturing. For now the B6420 is disconnected from the A1 completely.

You don't have to wait for a track to be processed in order to map it - if you're using JOSM then you can load it locally and if you're using Potlatch you can click on the edit link beside the track to load it straight into Potlatch.

That's because of cross domain restrictions in flash that stop it fetching the trace in that case.

If it isn't in the queue anymore then the import probably failed because of some problem with the track - you should have had an email with details. In fact you should always get an email when the track is processed, whether it works or not.

Sure it would be possible to implement limits, but it would be complicated and our experience to date is that it is not a significant problem - very occasionally somebody will upload a large batch of traces like this and it will cause a short term backlog but it usually clears fairly quickly.

It was me that had done part of Elvetham Heath Way a few months back as I have a friend that has just moved to to one of the new developments there. So the only bit I'd done was the bit I had to drive when visiting...

Converting the KML to GPX won't help as we don't import waypoints from GPX files, which also answers the original question about how to upload waypoints - you can't.

That's find thought, because it probably isn't really what you want to do as you will want these things to appear on the map, and GPX files (ie traces) are only used as source material - the map is drawn over the top of those.

What you want to do therefore is to convert your data to OSM XML format and then upload that with JOSM or the bulk upload script.

That all assumes that the license turns out to be compatible of course.

I looked at one sample untagged way and it has no history showing that it once had tags so I guess this is just bad tracing where no tagging was done.

You'll have to create your own permalinks (as openstreetmap.org does) or hack OpenLayers (like informationfreeway,org does) if you want to use the standard OpenLayers PermaLink control.

The next OpenLayers release will support reprojection which will fix this properly.

That's normal - there are always some broken bits of shoreline that cause errors like that. You should still find that most of it has imported, or I did at least.

The planet is loaded once or twice a week, but there is no global rerendering done - tiles are only queued for rerendering as a result of them being viewed. A summary of how it works can be seen at:

osm.wiki/index.php/Slippy_Map#Mapnik_tile_rendering

There is an additional delay at the moment as all rendering has been stopped for a few days while we transition to a new tile rendering/delivery system - during the period all the existing tiles are being rerendered using the new system but until that is complete you will be seeing the old tiles.

You can upload multiple files at once - just zip or tar them up into an archive and upload that. It will appear as one track if you do that though.

Alternatively, use one of the bulk upload tools in the svn repository to upload the tracks.

That's not true - we have always recorded history. Way history was wiped when segments were dropped though. I don't think the node history was though. What is new is the ability to see (and rollback) objects in Potlatch.