Topic on User talk:Ladsgroup

In this edit the bot removed upper and lower bounds because they matched the value. In this case it was appropriate, because elevation above sea level is never an exact value. But how does the bot distinguish between measurements that are necessarily inexact, and those that could be exact? As far as I know setting the value, upper bound, and lower bound equal to the same amount is the only way to indicate an exact value.

Hey, for measurements the bot only removes them when upperbound and lowerbound are the exact same value of the value and I run the bot on properties that are only measurements (e.g. elevation above the sea, etc.)

A few measurements are exact by definition. For example, one international yard is exactly 0.9144 meters; w:Meades Ranch Triangulation Station's position in the North American Datum of 1927 was exactly 39°13'26.686" N and 98°32'30.506" W. Do you have a method of dealing with these occasional "measurements" that are actually definitions, and thus exact?

I actually brought this issue earlier. That's why we work on properties and their units. Based on what we know I don't run it on unit/properties that can have such bleeding edges but we might miss something here.

I suppose if the bot only takes one run through the items, the few exact values could be corrected later. But if the bot is run repeatedly, there will be an edit war between the bot and editors who know the value is exact. How will such an edit war be prevented?

I won't run it repeatedly. just once, I actually mark them once they are done in User:Glorian_Yapinus_(WMDE)/quantity_change_properties