The SDF format is a tweaked version of the SQLite engine.
I don't think there's much to do about the size of it.
I have seen pretty heavy performance optimizations, if I remove all
unused columns from the data source.
Other than that, you might consider building different versions of the
SDF data for different zoom levels.
You can usually generalize the geometry, and thus get much faster
renderings.
Regards, Kenneth, GEOGRAF A/S
uXuf skrev:
Has anybody worked on minimizing the response times of the server? I am
working primarily with SDFs and there is a considerable amount of data in
them for a large city. Is there any way to compress the source SDF? Or has
anybody any other pointers to compress the data that is actually
transferred?
I have looked into the PNG vs JPG issue, but the quality drop is very
significant for client requirements.
Regards,
uXuf
_______________________________________________
mapguide-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapguide-users
