title: Fastest hierarchical geo address, data lookup on least expensive hardware? NoSQL or SQL?
body: <p>I have 350,000 city addresses with Latitude and Longitude values, like this:</p>
  
  <p>2500 HardToSpellName Street NW (quadrant), City, State, Country</p>
  
  <p>It would seem that the best data structure would be a JSON file mostly in reverse order and have the user enter the query in that order:</p>
  
  <p>Country.State.City.Quadrant.StreetType  - all these are repeated many times</p>
  
  <p>Then switch to civic number data input as numbers are easy to spell;)  From the above, we would implement a lookup to populate a "Auto Complete" on the Street Name as it is prone to spelling errors.</p>
  
  <p>The query of the data is always the same, one address input gets Lat/Long result.</p>
  
  <p>Is this a good idea? How many records would be reasonable? How would you convert a table (csv) to JSON tree?</p>
  
  <p>Is the main reason to use NoSQL the lower cost of hardware/hosting?</p>