Wrong results from TIGER geocoder for WA

Question

For WA I'm getting wrong results from my local setup. For the this address:

"1150 Varnum St NE, Washington, DC 20017"

SELECT g.rating, ST_X(geomout) As lon, ST_Y(geomout) As lat, (addy).* FROM geocode('1150 Varnum St NE, Washington, DC 20017', 1) As g;

I'm not getting any result:

SELECT g.rating, ST_X(geomout) As lon, ST_Y(geomout) As lat, (addy).* FROM geocode('1150 Varnum St NE, Washington, DC 20017', 1) As g;
 rating | lon | lat | address | predirabbrev | streetname | streettypeabbrev | postdirabbrev | internal | location | stateabbrev | zip | parsed 
--------+-----+-----+---------+--------------+------------+------------------+---------------+----------+----------+-------------+-----+--------
(0 rows)

If I replace Washington, DC with WA

1150 Varnum St NE, WA 20017

I do get a result:

SELECT g.rating, ST_X(geomout) As lon, ST_Y(geomout) As lat, (addy).* FROM geocode('1150 Varnum St NE, WA 20017', 1) As g;



rating |        lon        |       lat        | address | predirabbrev | streetname | streettypeabbrev | postdirabbrev | internal | location | stateabbrev |  zip  | parsed 
--------+-------------------+------------------+---------+--------------+------------+------------------+---------------+----------+----------+-------------+-------+--------
     55 | -117.640723859113 | 48.0459212150471 |         |              | Vernon     | St               |               |          | Burien   | WA          | 98148 | t

But this result is actually wrong:

(-117.640723859113, 48.0459212150471)

Which are way different from the ones from the census site:

(-76.993, 38.94287)

I search if WA tables are loaded and got this result:

SELECT count(*) FROM tiger_data.wa_edges;
  count  
---------
 2746400

Answer 1

You are probably missing the District of Columbia data. Using what you have for the state of Washington, you get the "best" result, which is fairly bad (wrong town and postal code)