[mapserver-users] Interesting Implementation of Mapserver

[Paul Ramsey]

For a website with dynamicly updated data, you might consider using
PostGIS. The "trouble" with using shapefiles and shptree is that for
each new row you add to the shapefile, you have to rebuild the shptree,
otherwise your data and your index will get out of sync. With PostGIS,
the index is kept up to date automatically during updates and inserts.
Transactional integrity also means that the low-probability case of
multiple simultaneous writes destroying your data file will not ever
occur.

P.

Drew wrote:
> 
> > > P.S. I am curious as to what "killed" the Mapserver. Was it an
> > > setup/optimisation problem or what? Our dev box started thrashing
> > > disk when someone placed a 300 Mb un-indexed shapefile into a map
> > > they were putting together (it doesn't matter how much CPU you have
> > > if it's going to take several seconds to read your shapefile from disk).
> >
> > This is not totally true, you should add a shapetree index to the
> > file and see what happens to performance, because then you will not
> > be reading data that is not needed for display purposes!!!!
> 
>         Is that a tileindex?
> 
>         Part of the problem, is that we've got hundreds of thousands of
> scanned wireless access-points in a shapefile, the world-maps seem to load
> really quickly, via tileindex.
> 
>         Is a shapetree different than a tileindex? Can you provide an
> example?

-- 
      __
     /
     | Paul Ramsey
     | Refractions Research
     | Email: pramsey at refractions.net
     | Phone: (250) 885-0632
     \_