Skip to main content

Property and Privacy

Interestingly, in Massachusetts you can find out the (fairly) complete property records for any address. This includes the names of the owners, sale price and sale history. I'm split by this transparency and efficiency in government. On one hand it is a great way to judge if the price of a home is within reason (by comparing it to similar homes nearby). It also allows you to trace the provenance of a plot of land (in the particular case I was handling the trail ended in 1949) which gives some indication of how clear the title is.
However, this looks to me like an alarmingly public release of very personal information. No one has any business knowing how much you paid for your home, or in fact, going to an address and figuring out who lives there. At the very least you should be required to give up YOUR identity to the authorities and the owner of the property should be notified that somebody is looking them up - openness should work both ways.
In California, interestingly, you can look up the assessed price of a property but you can't see sale price or owner information, which I think is the proper thing to do. You can still get this information by making a request for it, but that leaves a paper trail, which is slightly better. While it is true that sale prices usually exceed assessed prices it still gives you a relative idea. If you got to some commercial websites, however, you can get the complete records.
Usually a web-search with the term "assessor's office" will turn up the relevant websites. Individual cities can have different ways of allowing you to search for data. Malden, for example, is the most sophisticated and easy, allowing you to search along many different parameters, including owner name, property type etc etc. Malden allows you to find plot plans, sale records - basically all legal documents. Melrose only allows you to search by property address.
In Massachusetts all land records (deeds of sale, affidavits etc etc) can be searched for here. This I think is fine, because lawyers can search such records and if lawyers can do it, you should be able to too.
Labels:

Comments

Post a Comment

Popular posts from this blog

A note on Python's __exit__() and errors

Python's context managers are a very neat way of handling code that needs a teardown once you are done. Python objects have do have a destructor method ( __del__ ) called right before the last instance of the object is about to be destroyed. You can do a teardown there. However there is a lot of fine print to the __del__ method. A cleaner way of doing tear-downs is through Python's context manager , manifested as the with keyword. class CrushMe: def __init__(self): self.f = open('test.txt', 'w') def foo(self, a, b): self.f.write(str(a - b)) def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): self.f.close() return True with CrushMe() as c: c.foo(2, 3) One thing that is important, and that got me just now, is error handling. I made the mistake of ignoring all those 'junk' arguments ( exc_type, exc_val, exc_tb ). I just skimmed the docs and what popped out is that you need to return True or...
Post a Comment
Read more

Store numpy arrays in sqlite

Use numpy.getbuffer (or sqlite3.Binary ) in combination with numpy.frombuffer to lug numpy data in and out of the sqlite3 database: import sqlite3, numpy r1d = numpy.random.randn(10) con = sqlite3.connect(':memory:') con.execute("CREATE TABLE eye(id INTEGER PRIMARY KEY, desc TEXT, data BLOB)") con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", sqlite3.Binary(r1d))) con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", numpy.getbuffer(r1d))) res = con.execute("SELECT * FROM eye").fetchall() con.close() #res -> #[(1, u'1d', <read-write buffer ptr 0x10371b220, size 80 at 0x10371b1e0>), # (2, u'1d', <read-write buffer ptr 0x10371b190, size 80 at 0x10371b150>)] print r1d - numpy.frombuffer(res[0][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] print r1d - numpy.frombuffer(res[1][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] Note that for work where data ty...
Post a Comment
Read more