Hi, I would prefer not to have a need for one data exchange format for small datasets, and some other for big ones :)
I suppose that it is just this high memory consumption during parsing that is limiting the size of WFS request in OpenJUMP. The memory is freed once the parsing is done, but the peak value is what matters. Just with WFS it is not such a big problem because the data can be collected with several small requests, but what if you received the data on CD or something? -Jukka- -----Original Message----- From: [EMAIL PROTECTED] on behalf of Larry Becker >True, if you have the case of one very large GML layer for your whole >map, but this is far from normal GIS. >Larry >On 8/30/07, Sunburned Surveyor <[EMAIL PROTECTED]> wrote: >> Paul is correct. The pull parser does not reduce the memory of the >> parsing results, but it does reduce the memory used during the parsing >> process. That is because an in-memory representation of the entire XML >> document is not constructed. > >> One advantage of this is using the parser to select only data within >> the XML file that meets specific criteria. For example, if we had a >> 50MB SGF file representing the city of Stockton, I could parse the >> file and create only building features, even thought the file might >> contain road features, landmark features, park features. etc. >> In fact, I could even parse the file and only create features for >> buildings whose "building type" attribute was set to "Public". This >> allows me to extract the information I want without reading all 50 MB >> into memory. > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel