<div>Nice to see this topic is gaining interest!</div>
<div> </div>
<div>Mike, Craig, Alex, I'll forward Frank's quote to you plus some questions/answers that have gone back and forth between us. Perhaps there's some important issues or features I missed that you guys could toss into this.
</div>
<div> </div>
<div>Over here, (BGC Engineering Inc in Vancouver BC), we'd love to see this project go ahead with a couple partners to share the cost.</div>
<div> </div>
<div>I'll be out of the office (camping in the Okanagen!) between July 8th and July 20th. During that time if anyone needs to contact me regarding this endevour, please contact Gerry James ( gjames AT <a href="http://bgcengineering.ca">
bgcengineering.ca</a> ).</div>
<div> </div>
<div>Cheers,<br>Ken Lord</div>
<div>Vancouver BC</div>
<div><br><br> </div>
<div><span class="gmail_quote">On 7/6/05, <b class="gmail_sendername">Frank Warmerdam</b> <<a href="mailto:fwarmerdam@gmail.com">fwarmerdam@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On 7/6/05, Frank Warmerdam <<a href="mailto:fwarmerdam@gmail.com">fwarmerdam@gmail.com</a>> wrote:<br>
> On 7/6/05, Mike Davis <<a href="mailto:mike.and.kerry@gmail.com">mike.and.kerry@gmail.com</a>> wrote:<br>> > Funding things where I work is like pulling teeth, but I will inquire<br>> > with the "powers that be" to see if it is possible, this is a feature
<br>> > we would really like to have (especially if the performace is close to<br>> > that of shapefiles).<br><br>Mike,<br><br>There are two main issues affecting performance.<br><br>1) Spatial indexing. Personal geodatabase does have a spatial
<br>index table associated with spatial tables. If we can properly utilize<br>this we ought to be able to grab small spatial regions out of big tables<br>effeciently. If not, it will be as corresponding slow as a shapefile would
<br>be without a spatial index. I'm not really confident I can utilize the<br>spatial index yet though. I looked at a sample file Howard provided,<br>and the index table just had 0's and -1's in the spatial index table.
<br>I don't know if I was using too old a version of MS Access to look at it,<br>or if it wasn't built or what.<br><br>2) ODBC and OGR translation overhead. Both of these layers add<br>significant performance drag.<br><br>
I can't give any real guarantees for performance, but if we can get<br>spatial indexing working it shouldn't be too much worse than direct<br>shapefiles.<br><br>Best regards,<br>--<br>---------------------------------------+--------------------------------------
<br>I set the clouds in motion - turn up | Frank Warmerdam, <a href="mailto:warmerdam@pobox.com">warmerdam@pobox.com</a><br>light and sound - activate the windows | <a href="http://pobox.com/~warmerdam">http://pobox.com/~warmerdam
</a><br>and watch the world go round - Rush | Geospatial Programmer for Rent<br></blockquote></div><br>