You can use this to find out:

http://owl.apis.dev.openstreetmap.org/?lat=53.347&lon=-2.1983&zoom=12&layers=M

Click on the ‘History (beta)’ tab at the top.

You can use this to find out:

http://owl.apis.dev.openstreetmap.org/?lat=53.347&lon=-2.1983&zoom=12&layers=M

Click on the ‘History (beta)’ tab at the top.

This is great, thanks!

You’ll also find that bus route relations in London are constantly becoming out of date because of small changes, e.g. see this:

http://mqt.london.gov.uk/mqt/public/question.do?id=46040

Hi chtfn,

I can see why you’re confused!

Both MapQuest Open’s editor and the editor on the OpenStreetMap homepage point at the same database, so if you use either one you are editing OpenStreetMap.

The slight differences you have noticed are because the software both use - called Potlatch 2 - allows for different set-ups, such as the tags that are recognised. MapQuest Open’s version of the software isn’t set-up to recognise houses, whereas the version on the OpenStreetMap homepage is. It looks like MapQuest also use an older version of Potlatch 2.

There are actually lots of different editors that you can experiment with. Here is a list:

osm.wiki/Editors

Which one is best? I’d recommend you just give them a go and see which you prefer. The most popular are the in-browser Potlatch 2 editor on the OpenStreetMap homepage, and a desktop editor called JOSM.

More suggestions for tweaking the UI…

The title of each changeset and object should just expand the div in the sidebar, with a separate link to take you to the OSM changeset/object page. The current mixed behaviour is confusing.

When you select a changeset or object, the colour should change more noticeably. It would be easier to see what is going on if each changeset started life as grey lines, which turned blue when you select the changeset or object.

Something of a holy grail would be a visualisation of modified or deleted geometry, which may be beyond the scope of your project. Changesets very often include lots of ways, that may have simply been touched or moved a tiny amount. But sometimes in among the changes somebody has moved a footpath quite significantly, or deleted a building. I find it so time consuming to spot these that I don’t even bother trying.

Excellent!

It seems to be drawing weird diagonal lines where the object that has been edited extends outside the bbox of the changeset, for example click on the history tab here:

http://owl.apis.dev.openstreetmap.org/?lat=51.41801&lon=-0.07418&zoom=17&layers=M

That big right-angled corner is an incomplete residential area: osm.org/browse/way/35823706

Ideally you would have an area for the boundary and all the roads inside it bundled together into a relation, which carries the info on the price, operator, etc. otherwise it will be a bit of a pain updating it each time the details change!

Actually, I was in the Peak District this weekend walking around Tissington and Matlock. Having OsmAnd on my phone certainly impressed friends who were staring blankly at Google Maps trying to work out where to go. So thanks.

I noticed lots of little paths around the tors/hills between Matlock and Matlock Bath that need adding in, if anyone fancies a nice day’s work. Sadly I couldn’t divert my friends in circles to get them all, and currently there’s only one footpath mapped.

From one OSM contributor to another… thanks!

This looks like really good work.

That sounds good.

Often with these monitoring tools, I see that somebody has made some changes but when I look at the changeset I can’t really work out what they have done. Have they shifted a road 10m to the east, or just touched some nodes while making other changes in the area? Is this changeset something I should check or ignore? It’s almost impossible to tell at the moment.

This is a huge improvement, it would be great to roll this out to the OSM homepage.

One of the other frustrating shortcomings of the current history features on the web site, which your panel goes some way to fixing, is that you can’t visualise features that have been deleted. A next step would be to show the feature in the map view on pages like osm.org/browse/way/131004269

This is great work, well done!

There’s always more detail to be added! Though I had to move house after I got this far in my old neck of the woods ;-)

osm.org/?lat=51.45969&lon=-0.07065&zoom=16&layers=M

Nice! It’s great that you’re adding the manufacturer and power rating too.

This is great work, well done.

I think the tag you need for Corham Hurst is leisure=nature_reserve: leisure=nature_reserve

There was some discussion of improving the level of detail when tagging protected areas, which you could contribute to if you’re interested: osm.wiki/Environmental_OSM#Natural_habitats_.2F_landuse

I think the practice of tagging the “holes” with the correct landuse/natural tag looks sound.

Zverik, it isn’t ok to import garbage but two wrongs don’t make a right!

Running large scale edits can easily delete or modify content in ways you won’t expect. People may have improved some of the poorly imported data, so you will delete their work. You may inadvertently catch good work in your net. You may have simply mistaken some edits as being bad when they are work in progress or even reflect the facts on the ground.

It is arrogant and bad behaviour to go deleting lots of content without first checking that you are working from sound assumptions.

This all sounds great, keep us updated on future developments.

I’d like to add my “welcome” as a fellow south London mapper, though I’m up in Southwark.

In my experience smart phone GPS is terribly inaccurate, most of the time you can spot all the footpaths and other features with the Bing aerial imagery so there aren’t many uses for GPS in London any more. I find that the aerial imagery, combined with notes and checking against existing features, makes for far more accurate mapping than my phone’s in-built GPS. I only use a cheap GPS (NaviGPS) and other people’s GPS traces on the main road network to ensure I’m compensating for the fact that the Bing imagery is usually offset by a few metres.