The geocoder needs to support cardinal and ordinal numbers (http://www.mathsisfun.com/numbers/cardinal-ordinal-chart.html). It is very common to see 'first' or 'one' in an address and would greatly help not only in geocoding coding process but the address parser.

A really nice and efficient algorithm could be written for this!

Address geocoder works for 'NY' but not 'New York'.

Reasons:
1.the postgresql metaphone function requires a string length while doublemetaphone does not
2. doublemetaphone should be more accurate!!

The test DB is currently loaded with only NY state data. A new test DB needs to spun up (in AWS VPC), loaded with data and then tested.

Currently, intersection geocoding is NOT supported. From my research there's a few ways to to do this - but any basic functionality here would be awesome.

The interpolation code in engine.py seems to be off for certain addresses.
Example; 6 caputo drive manorville ny 11949 interpolates to the next street....

I would like PinPoint to return a real JSON result set. This includes defining geocoding levels and a standard structure. Google has a good article on this I'll link in later.

We cannot geocode without a zip code right now. We can leverage the "Guess City" function to do this.

It's apprently difficult to geocode an address with the right zip code but wrong city [or vice versa].
Example: 1 McGuirk Street East Hampton NY 11949

US Geocoder cannot do this:

http://geocoder.us/demo.cgi?address=1+mcguirk+street+east+hampton+ny+11949

PinPoint sorta can do it!

works: 1 mcguirk street east hampton ny 11949
does not work: 1 mcguirk street east hampton new york 11949

It seems due to a bug, we can do this! I need to figure out why PinPoint can do this...thanks bug.