Splshpoint Search Functions

The simple search and advance search functions are done. I have uploaded all of the PlaceNames data to the database and loaded all of the addresses in San Jose (residential and commercial). Start small and then load all of California by end of this month. The advance search function will perform any mix of bolean query and I would add later for user to custom make their own query and save for later execution. I've done this before when I was working with a USAMS application. I separated the data in two parts. One I called background information - things that don't change that often and the others are dynamic information - things that are constantly changing. I didn't think it's necessary to place certain layers such as boundaries to be loaded in the database and be served by WMS; it's better to have these layers reside locally. Now, how do you maintain the massive database that will exponentially grow very quickly in time? This will be managed through the Web interface with capabilities to mesh with other mapping tools as well as WW via URI protocol.

I do have my own Tiling Server for loading custom and proprietary imageries. I need to automate the creation of WW compatible tiles from raw data. I'll defer this problem for now. The other component that I need to add is an address to lat/long conversion engine which I decided to run in the background at odd hours to continually update the central database; such engine will not be used in the transaction of queries by users as it will add considerable latency in the system response. This engine is already built. I'll just have to connect it to the central, enterprise database search engine. With updates of data from USPS on a monthly basis, the database will reasonably be kept current at least in the coverage for the US.