Skip to main content

Loose Manhole cover

There is a loose manhole on a street cover near our house. Cars going over it make a very loud clanking noise. This will be a test of PG County Government efficiency.

A. How hard is it to find who to contact about this?
  1. A google search "prince george county government" takes us quickly to
  2. PG county where a top menu option takes us to
  3. Government and a easily naviagble side menu takes us to
  4. Department of Public Works and Transportation where though there is no option for a "loose manhole cover" there are things to do with roadways. I decided that "drainage" would be most appropriate since these dudes should have the tool set to open (and perhaps replace) manhole covers.
  5. Office of Highway Maintenance's (OHM) Customer Service Office at (301) 499-8520 seems to be the people to contact.
B. Does this work?
Yes! I get patched through to a operator who takes the details of the loose manhole lid and gives me a confirmation number.

All done over lunch, say 15min tops starting cold. So far, I'm happy to be paying taxes to PG County.

Now lets see how long the business end takes.
Labels:

Comments

  1. Edward OttJanuary 8, 2008 at 2:42 PM

    That is very efficient. of course if a crew doews not show up for a couple of weeks it would seem for naught.

    ReplyDelete

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