Changeset No. Date Contributor Comment
12017-08-14 06:19:20 UTCbdiscoe Dguillen, it looks like you accidentally "squared" and uploaded a very long tertiary route here, which destroyed its geometry. Please be careful! You should ask an experienced mapper how to undo your changeset, or manually fix the road you mangled.
22017-08-15 07:46:04 UTCbdiscoe I have gone ahead and reverted this changeset and fixed all the geometry and topology it broke.
12017-06-18 18:04:15 UTCmarek kleciak Stop destroying detailed map using generalization tools. In developing countries like Nepal eactly map can save human life. Please first ask, then act.

22017-06-18 18:34:03 UTCSomeoneElse Hi Marek,
Can you please explain what were the actual problems caused by this changeset and the others on which you have similarly commented?
Also, you may find that that using emotive language such as "stop destroying" is less effective at communicating what you want to get across than ...
32017-06-22 13:04:49 UTCimagico I would like to add that what bdiscoe did here was not in any way destroying a detailed map. He removed nodes which had a very little influence on the overall geometry because they were almost exactly in the middle between the next and the previous node. See
42017-06-22 16:25:02 UTCSomeoneElse For info, see also .
52017-06-23 05:46:26 UTCbdiscoe For what it's worth, I wrote OSM messages to marek kleciak explaining these edits, and even described the detailed steps he can do in JOSM to do the cleanup himself.
62017-06-23 07:16:50 UTCmarek kleciak We are in touch with bdiscoe now. I wrote him about reasons for this mapping. We have opportunity to make an very exactly example for nepali authorities and show the results during SOTM Asia 2017. All old, too less forest areas should be removed/modified. I hope for help of you all: The goal would b...
72017-06-23 07:41:17 UTCimagico Who is 'we' here?

Keep in mind that planning and organizing of mapping activities and development of mapping conventions should be public.

Although there is not yet a formal policy on organized mapping activities it is good practice to document such activities and reference this in changeset c...
82017-06-23 07:50:00 UTCmarek kleciak We, is Kathmandu Living Maps. As you probably know from german forum I do a lot for Nepal and try to inform communities in Germany and Poland about recent situation there.
What you wrote about mapping activities is a part of old OSM communication problem, but you´re absolutely right, I should...
92017-06-26 05:49:54 UTCmarek kleciak *** SPAM *** not displayed - visit
102017-06-26 15:32:38 UTCSomeoneElse @marek - having nodes closer together doesn't make for a map that matches reality better; it just makes it more difficult to edit. If you've got some specific examples perhaps write it up as a diary entry?
112017-06-26 16:14:53 UTCmarek kleciak Absolutely. This matter needs an proposal and discusion of the community.
122017-06-28 03:50:12 UTCbdiscoe *** SPAM *** not displayed - visit
132017-06-28 04:39:19 UTCmarek kleciak Ben wrote: imprecise criteria, human variability, seasonality, poor resolution, loose rectification.

We have Premium Digital Globe images from last year for whole Nepal. Factors like human variability or seasonality are general for all OSM maps. Only activation of the community AND in this case l...
12017-06-24 06:24:44 UTCbdiscoe Could you please explain what these edits are? I truly hope it is not the "USGS treecover 2010" which is derived from low-resolution LandSat which is entirely inappropriate for mass-import into OSM. Or did you get this import discussed and approved?
22017-06-24 06:26:16 UTCbdiscoe I spot-checked these imported forests and they bear no similarity to what is actually on the ground.
32017-06-24 06:59:54 UTCff5722 They are derived from usgs data, I added everything in manually checked chunks with background imagery enabled. Some places need more refinement, but 'no resemblance at all' seems exaggerated.

It was discussed in talk-cn.
42017-06-24 07:12:38 UTCff5722 See my documentation here:

I would say it is more comparable to using Scanaerial.

Admittedly the data from this area is not that good, but as i trace around this area manually often, I also expected to refine it soon by hand.
52017-06-24 07:47:44 UTCbdiscoe OK, it's possible that the places i checked were worse than average, but consider the fine-grained nature of these features, like at When the nodes are as close as 2.4m but the source data (Landsat) is 28m (!) then there is s...
62017-06-24 09:54:32 UTCff5722 I have simplified the ways in JOSM with a 15 m threshold, and merged or deleted all ways with less than 17 nodes. Some abberations redrawn from Bing. It should be a lot better now. Later i'll refine it from imagery more.
72017-06-24 18:06:07 UTCbdiscoe OK, thanks! I am much reassured that quality is being cared for and you aren't just making work for me to clean up later :)
12017-03-30 11:09:53 UTCde vries Hi bdiscoe,
I need to ask you to be more careful with edits like these. In this changeset you seem to have targeted BAG buildings for mass simplification. The methods and software used for importing and actualization of the BAG data has been discussed in great length. So doing mechanical edits to t...
22017-04-20 15:27:35 UTCbdiscoe Hi, if you take a close look, you will see that no "details" were removed. As part of other cleanup (maproullette farm->farmland), I've been run the JOSM validator on some of the nearby buildings and landuse, and tidying up the results. The BAG buildings have numerous issues (including...
32017-04-20 15:45:32 UTCbdiscoe For what it's worth, I recognize unlike other mass imports I'd had to clean up (Canvec, NHD, Tiger...) this data is much better in precision as well as accuracy. That's why i use thresholds not of 70-110 cm as with NHD, but as little as 6 cm for BAG, guaranteeing that cleanup stays within the accur...
42017-04-27 21:36:15 UTCbdiscoe For an example of BAG problems, see buildings like which has a "sliver" which is 18cm wide and 3m long; it is clearly a mechanical error. I have manually fixed hundreds of these problems.
52017-04-28 20:32:31 UTCCommodoortje Hi bdiscoe,

Thank you for fixing the JOSM validation errors on BAG import here.
The person who did the BAG import is responsable for fixing duplicated nodes/crossing buildings/building inside building self-intersecting ways etc...
62017-05-01 15:23:38 UTCde vries You had me at "I am an expert at what I'm doing". But if you want an example: compare this two images:
The imagery resolution is 7,5 cm so your simplification is nowhere within the accuracy of ...
72017-05-01 15:51:38 UTCCommodoortje Het lijkt erop dat bdiscoe in JOSM de functie "Simplify Way" gebruikt.
Wat deze tool doet: de contouren ontdoen van onnodige nodes.
Ik ben het met de vries eens dat dit niet structureel op gebouwen mag plaatsvinden. Dan wordt...
12016-07-16 03:36:26 UTCbdiscoe Hi there, many of the ways in this changeset are EXTREMELY overnoded. When you upload, you need to check the data FIRST for this problem and solve it before uploading. Otherwise it creates 26903 nodes in the OSM database, then someone has to come along afterwards and clean it up by deleting ~90% o...
22016-07-16 03:45:46 UTCbdiscoe Example: before:

Notice how the nodes for the selected are reduced from 1832 to 241, without affecting the accuracy of the data at all.
12016-05-03 16:47:42 UTCbdiscoe Yes, it's NHD. Welcome to my world, Jeopardy. I've spent much of the last 6 months of my life cleaning up North Carolina's NHD (outdated wetlands just like these here in Florida). It's just a huge task, thanks for helping!
22016-05-03 16:57:16 UTCHarry Wood The messiness of the data seems to be echoed by the messiness of the wiki page which is supposed to describe the dataset and the import process/status
32016-05-04 01:54:36 UTCJeopardyTempest Good to know :-)

Though it seems the wetlands are at least proximate... we also seem to have a messy import of a church dataset with scattered nonexistent churches that seems more problematic.

So what do you guys do to clean them up? If there's development over what used to be wetlands, I'll ...
42016-05-13 06:17:52 UTCbdiscoe To answer your last question, Yes.
12016-04-26 18:15:45 UTCbdiscoe Rps, there are some serious issues with this import. For example, consider way It is "water", but unclosed. It is also duplicated, as is all the other sections of water which should have been joined here. PLEASE stop importing millions of featu...
22016-04-26 20:28:16 UTCRps333 Hi, thanks for pointing it out. The JOSM validation did not pick that out. I will clean them up. cheers
32016-04-26 21:52:47 UTCbdiscoe When I load a small area around this feature, the JOSM validator reports "Errors: Duplicated ways (98), Duplicated nodes (s), Warning: natural type water - Unclosed way (46)"
42016-04-26 22:01:51 UTCbdiscoe Rather than import huge amounts (>500K changed features on the day of this changeset!), I'd strongly recommend doing smaller sections (like ~10K features/day) so you can check it for errors _before_ uploading, thanks.
52016-04-28 19:08:07 UTCbdiscoe It's two days later, and JOSM in this area still reports errors unclosed ways. Please fix your import before importing any more, thanks.
62016-04-28 19:13:33 UTCRps333 Hi I have been checking the JOSM again and for what ever reason JOSM is not finding the errors. I am pretty sure most of the errors are on the edge of the AOI that I downloaded from NRCan. I will try checking with another version of JOSM and a different PC.
12016-01-22 23:08:26 UTCbdiscoe Hello Davaadulam, I see you changed the english name (name:en) of this street from "Olympic Avenue" to "Олимпийн өргөн чөлөө". The English name is actually "Olympic Avenue, correct? Why did you change it?
12015-12-16 19:43:47 UTCbdiscoe Kendall, you added ways which should be paths or service roads, but you tagged them as "motorway" with names like "I-40 West" which is very odd and confusing. I will attempt to fix the tagging, but what did you intend here?
12015-11-24 22:02:17 UTCgileri Thank you, this looks like a good thing to do !

May I ask how did you do it with JOSM ?
22015-11-25 07:15:19 UTCbdiscoe In the preferences, under "advanced", there is a setting called "simplify-way.max-error". It is important to set this to a low number appropriate for the specific geometry; in the case of a very clear lake like this, sub-meter precision can be maintained, hence a value of 0.4
32015-11-25 16:22:13 UTCgileri Thank you !
12015-10-24 15:52:53 UTCbdiscoe Testing ability to put emojis in chageset comments: 👍🏻👍🏼👍🏽👍🏾👍🏿😊😄😊
22015-10-24 15:54:42 UTCbdiscoe 👍
12015-06-08 20:48:33 UTCbdiscoe Maykel, you used "service" incorrectly for the roads in the village. They are "residential" roads.
22015-06-08 20:50:25 UTCbdiscoe Also, where two roads cross, they need to share a node. Please learn about connectivity.
12015-06-08 20:26:20 UTCbdiscoe Albert, you damaged the main Pinrang-Rappang highway by incorrectly changing the secondary to a service road. I will fix it now, but please be careful in the future.
22015-06-08 20:27:19 UTCbdiscoe Also, never name roads just "jalan". The name tag is only for the actual name of the road, e.g. "Jln Poror Pinrang-Rappang"
12015-05-09 20:42:32 UTCmaraf24 Is this tag removal and transformation discussed with polish community?
22015-05-25 02:04:55 UTCbdiscoe Hi maraf24, I believe I only removed a few tags, which were uncontroversially incorrect or extraneous. If there is a page that describes the Wroclaw building import, please direct me to it.
12015-04-27 18:50:03 UTCtrigpoint Hi
I have spotted that you have edited the River Severn in Shropshire.
The river forms parts of Montford/Ford parish boundaries and in moving the river flow you have moved the boundaries so that they no longer follow the official lines.
I am not sure what source you used to determine the main flo...
22015-05-01 16:48:35 UTCbdiscoe Hi tngpoint, mostly this changeset was fixing the riverbanks and adding the islands. The centerline moved only very slightly; it had a few places where it did not appear to correspond to the river flow. I did the best I could using the aerial, but if you have better local knowledge, please feel fre...
32015-05-01 16:52:47 UTCbdiscoe Also, I notice that it isn't quite consistent; in some places the parish boundaries share a way with the river, in other places they use two separate ways; perhaps someone determined that on that stretch the "official" boundary differed significantly enough from the river. Some boundaries...
42015-05-01 19:30:41 UTCSomeoneElse I've always wondered (where boundaries follow rivers) exactly how those boundaries are defined, given that rivers move? In this case is there a text description that says something like "follows the centreline of the river from blah to blah", or is it defined in terms of exact coordinates...
52015-05-25 02:01:45 UTCbdiscoe @SomeoneElse, it depends :) In some places the legal boundary is defined as the river, in other places the river was surveyed and that description of the course defined as legal boundary. It takes local knowledge to know the difference in different parts of the world.
62015-05-25 11:40:22 UTCtrigpoint The boundaries are taken from the latest OS Boundaryline, so can be assumed to indicate the official boundaries.
I part way through a project to add the Shropshire parish boundaries, some sections of the Severn have yet to be joined to the parish boundaries.
I am not sure how "the main flow&q...
12015-05-12 11:26:51 UTCmaraf24 With over 30000 deleted nodes this is certainly a mechanical edit.
22015-05-22 06:44:57 UTCbdiscoe I reviewed it personally. There is decimation to remove noise and redundancy, but I also go over what remains manually to compare it to the aerial; many of these wetlands are no longer here and are adjusted accordingly.
12015-05-05 20:42:08 UTCbdiscoe This looks like a building import, but there were already buildings there. Was there no attempt to integrate and check for overlaps? Is there a plan to clean this up, or should I go ahead and clean it up manually?
22015-05-07 20:00:05 UTCbdiscoe I've proceeded to clean it up now.
bdiscoe has contributed to 17 changeset discussions(s) with a total of 64 comment(s)