I've made a county-wide LIDAR based 1ft contour feature class in a local fGDB. There are ~2.6 million features for about 550 contour intervals (possibly order of billions of vertices, at least hundreds of millions). The extent is about 15 miles by 30 miles. Currently many of the lines are single features over 20 miles long with perhaps thousands of vertices (I'm speculating). It takes about 6 minutes to draw at full extent which is pretty much unusable. If I diced this up with, say, a 1mile x 1mile grid to make more, smaller features would the performance be better or worse?
Alternatively, would a local "personal" SDE GDB on SQL Server Express speed this up?
10.1 SP1, Win 7 64bit, Core i7 870 (2.93Ghz), 10Gb RAM.
Alternatively, would a local "personal" SDE GDB on SQL Server Express speed this up?
10.1 SP1, Win 7 64bit, Core i7 870 (2.93Ghz), 10Gb RAM.
Best practice would be to intersect the contour lines against a regular grid
of at least 5x5 over the study area, then dissolve by grid cell and elevation
(unioning nearby shapes with the same attribute). If you then set scale
dependency so that not more than 4-9 grids are rendered at one time,
the draw request should fly (at which point it won't matter if it's got the
added database overhead of SQL-Server Express [which would generally
slow access vice a local FGDB]).
- V