<span class="gmail_quote">On 12/4/06, <b class="gmail_sendername">Hal Mueller</b> <<a href="mailto:hal@mobilegeographics.com">hal@mobilegeographics.com</a>> wrote:</span><blockquote class="gmail_quote" style="margin-top: 0; margin-right: 0; margin-bottom: 0; margin-left: 0; margin-left: 0.80ex; border-left-color: #cccccc; border-left-width: 1px; border-left-style: solid; padding-left: 1ex">
A bit more detail about the search would help--coding environment?<br>search parameterization? DB attributes?</blockquote><div><br></div>there're more than 1 coding environments. search database is oracle on a different server. i am on a different server running my map service making maps on demand. i am also running my geocoding service on demand. i want to tie my 2 services for whoever wants it. my question really is- how do i best do the tie up?
<br><br><span class="gmail_quote">On 12/4/06, <b class="gmail_sendername">Hal Mueller</b> <<a href="mailto:hal@mobilegeographics.com">hal@mobilegeographics.com</a>> wrote:</span><blockquote class="gmail_quote" style="margin-top: 0; margin-right: 0; margin-bottom: 0; margin-left: 0; margin-left: 0.80ex; border-left-color: #cccccc; border-left-width: 1px; border-left-style: solid; padding-left: 1ex">
Geocoding after every search will be slow, and a heavy load. IMO you<br>would do better by geocoding all of the points in your search<br>database once, and storing that.<br></blockquote><br>yeah the visitor'd have to wait but i am trying to avoid mixing search database (oracle, non-spatial) with geocode database (postgresql, spatial).
<br><br><span class="gmail_quote">On 12/4/06, <b class="gmail_sendername">Hal Mueller</b> <<a href="mailto:hal@mobilegeographics.com">hal@mobilegeographics.com</a>> wrote:</span><blockquote class="gmail_quote" style="margin-top: 0; margin-right: 0; margin-bottom: 0; margin-left: 0; margin-left: 0.80ex; border-left-color: #cccccc; border-left-width: 1px; border-left-style: solid; padding-left: 1ex">
1 run search<br>2 generate unique filename string (say "xyzzy12345")<br>3 create xyzzy12345.dbf with the attributes of your search<br>4 ln -s permgeocode.shp xyzzy12345.shp<br> ln -s permgeocode.shx xyzzy12345.shx
<br> etc.<br><br>now you have a shapefile whose attributes are the search results for<br>a particular query, and you can display it normally, without having<br>to think about the fact that it came from a search query.<br>
</blockquote><br>didn't quite get that. i don't think i am struggling with shp creation. see, the search runs on a separate server on a separate database. that server'd then feed my server with the results. i get to geocode the results and show them on a fancy map ;).
<br><br>jzs<br>