<div>Thanks Gavin, Badreddine for the quick reply.</div>
<div>The provider does implement <font size="2">SelectAggregates (it came with the SHP provider), but not sure were to implement the SpatialExtents and Count. In what class is that? (<font size="2">SelectAggregates base class do not implement these)
</font></font></div>
<p><font size="2">Piet</font><br><br></p>
<div><span class="gmail_quote">On 10/1/07, <b class="gmail_sendername">Gavin Cramer</b> <<a href="mailto:gavin.cramer@autodesk.com">gavin.cramer@autodesk.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I agree. The code excerpt does not have appear to have any intrinsic<br>performance problem. Pre-sizing the FdoByteArray would likely make a
<br>trivial difference, since it uses internal object caching for smaller<br>values that are typical for geometries. The biggest difference would be<br>having SpatialExtents and Count implemented.<br><br>Gavin<br><br><br>
<br>-----Original Message-----<br>From: <a href="mailto:fdo-users-bounces@lists.osgeo.org">fdo-users-bounces@lists.osgeo.org</a><br>[mailto:<a href="mailto:fdo-users-bounces@lists.osgeo.org">fdo-users-bounces@lists.osgeo.org
</a>] On Behalf Of Badreddine<br>Karoui<br>Sent: Monday, October 01, 2007 9:42 AM<br>To: <a href="mailto:fdo-users@lists.osgeo.org">fdo-users@lists.osgeo.org</a><br>Subject: RE: [fdo-users] Improving performance for NEN1878 provider,
<br>howto?<br><br>Hi,<br><br>You may want to implement the FdoISelectAggregates command plus the<br>SpatialExtents and Count functions. If these two functions are not<br>implemented, then Map will scan all the geometries to find the minimum
<br>bounding rectangle of all the data.<br><br>Badreddine<br><br>-----Original Message-----<br>From: <a href="mailto:fdo-users-bounces@lists.osgeo.org">fdo-users-bounces@lists.osgeo.org</a><br>[mailto:<a href="mailto:fdo-users-bounces@lists.osgeo.org">
fdo-users-bounces@lists.osgeo.org</a>] On Behalf Of Piet Bibber<br>Sent: Monday, October 01, 2007 7:46 AM<br>To: <a href="mailto:fdo-users@lists.osgeo.org">fdo-users@lists.osgeo.org</a><br>Subject: [fdo-users] Improving performance for NEN1878 provider, howto?
<br><br><br>Hello,<br><br>My NEN1878 provider is almost done, but performance is not so fantastic<br>when<br>reading the geometry; reading the schema is alright.<br>That is stange, as I cache in the geometry when I read the schema
<br>(NEN1878<br>schema discovery requires a full file scan; no seperate schema header).<br>(The<br>schema is read within 3 seconds for a 2.3MB file, including the geometry<br>and<br>attributes (all in memory (using STL)).
<br>The SDF and SHP all seem so fast :-)<br><br>Map 3D seem to spend most of his time caching in the geometry (see<br>source<br>code below)<br><br>I based my provider on the SHP provider, the reader seem to use<br>FDO_READER
<br>template, but I can't find where that points to. Maybe there are better<br>optimized readers.<br><br>Thanks.<br>Piet<br><br>Excerpt from the source files:<br><br> FdoByteArray * CreateCachedGeometry(FdoByteArray* fgfByteArray_I)
<br> {<br> FdoByteArray* fgfByteArray = fgfByteArray_I; // it may be<br>reallocated<br> int count = mFeature->GetNumPoints();<br> FdoInt32 numPointOrds = 2;<br> FdoInt32 numBytesForOrdinates = numPointOrds *
<br>sizeof(double)<br>* count;<br> FdoInt32 numParts = 0;<br> FdoGeometryType fdoGeomType = GetFdoGeometryType();<br> FdoInt32 dimensionality = FdoDimensionality_XY;<br> FdoInt32 numPositions = mFeature->GetNumPoints();
<br><br> fgfByteArray->Clear();<br><br> fgfByteArray = FdoByteArray::Append(fgfByteArray,<br>sizeof(fdoGeomType), (FdoByte *) &fdoGeomType);<br><br> switch (fdoGeomType)<br> {<br> case FdoGeometryType_None:
<br> break;<br><br> case FdoGeometryType_Point:<br> fgfByteArray = FdoByteArray::Append(fgfByteArray,<br>sizeof(dimensionality), (FdoByte*)&dimensionality);<br> fgfByteArray = FdoByteArray::Append(fgfByteArray,
<br>numBytesForOrdinates, (FdoByte*)mFeature->GetPoints());<br> break;<br><br> case FdoGeometryType_LineString:<br> fgfByteArray = FdoByteArray::Append(fgfByteArray,<br>sizeof(dimensionality), (FdoByte *) &dimensionality);
<br> fgfByteArray = FdoByteArray::Append(fgfByteArray,<br>sizeof(count),<br>(FdoByte *)&count);<br> fgfByteArray = FdoByteArray::Append(fgfByteArray,<br>numBytesForOrdinates, (FdoByte *)mFeature->GetPoints());
<br> break;<br><br> default:<br> throw<br>FdoException::Create(FdoException::NLSGetMessage(FDO_NLSID(FDO_10_UNSUPP<br>ORTEDGEOMETRYTYPE)));<br> }<br><br> return (fgfByteArray);
<br> }<br><br><br>// Returns pointer to vector of DoublePoints<br>inline DoublePoint* Nen1878Feature::GetPoints()<br>{<br> return (&mCoordinates[0]);<br>}<br><br>--<br>View this message in context:<br><a href="http://www.nabble.com/Improving-performance-for-NEN1878-provider%2C-howt">
http://www.nabble.com/Improving-performance-for-NEN1878-provider%2C-howt</a><br>o--tf4547817s18162.html#a12977669<br>Sent from the fdo-users mailing list archive at <a href="http://Nabble.com">Nabble.com</a>.<br><br>_______________________________________________
<br>fdo-users mailing list<br><a href="mailto:fdo-users@lists.osgeo.org">fdo-users@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/fdo-users">http://lists.osgeo.org/mailman/listinfo/fdo-users</a><br>
<br>_______________________________________________<br>fdo-users mailing list<br><a href="mailto:fdo-users@lists.osgeo.org">fdo-users@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/fdo-users">http://lists.osgeo.org/mailman/listinfo/fdo-users
</a><br><br>_______________________________________________<br>fdo-users mailing list<br><a href="mailto:fdo-users@lists.osgeo.org">fdo-users@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/fdo-users">
http://lists.osgeo.org/mailman/listinfo/fdo-users</a><br></blockquote></div><br>