3 ms·
To have a unique id for each house is neat but I think there are loads of situations you’d have to account for so that there isn’t any ambiguity in the assignme
by left-struck 2y ago
To have a unique id for each house is neat but I think there are loads of situations you’d have to account for so that there isn’t any ambiguity in the assignment of unique ids. If any ambiguities exist inevitably you will have exceptions in the system which defeats the point.
For example
-Subdivision of a lot.
-Joining of lots.
-You said every house… what about two houses on the same lot?
-What about apartments buildings?
-What happens when one or more houses are demolished and an apartment building goes up?
Etc etc
I work in manufacturing and this sounds a lot like the problem of part numbering, and let me tell you, it’s not a trivial problem and the company I work for thought it was and got it wrong.
- throwway_278314 2y agoentity resolution is hard everywhere. Because the world is dynamic, but the common understanding of "entity" is a static object. and the only perfect description of the world is the world, just like on a more trivial scale the only perfect description of what a piece of software does is to run it and see what it does. So the best I know is to find a level of abstraction that captures enough stability to be useful, with enough flexibility to enable the classification to adopt. In math, phylogenetic trees might be an example; think Dirichlette processes and exchangeable stochastic processes.