Rather than provide responses in pages of 3000, the service just transmits 3000 records and stops. So the result is incomplete.
If we try to ask for more records, then the transmission seems to be terminated and the incomplete in terms of the xml syntax:
ERROR |XML Parser error: 'Error in input dataset:
'https://externaltest.dev.geocloud.com:443/server/services/PuertoRicoVector/MapServer/WFSServer?SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&TYPENAMES=PuertoRicoVector%3ARIVER_C&NAMESPACES=xmlns%28PuertoRicoVector%2Chttp%3A%2F%2Fwww.esri.com%29&OUTPUTFORMAT=application%2Fgml%2Bxml%3B%20version%3D3.2' line:1 column:908 message:expected end of tag 'HR''
When Client J exercises Q7 the following issue is encounter:
Query appeared to time out. Attempted to use WFS paging but only first page was returned.
2018-04-30 03:43:15| 14.9| 0.0|INFORM|Sending HTTP 'POST' request to 'https://externaltest.dev.geocloud.com/server/services/PuertoRicoVector/MapServer/WFSServer', waiting for response ...
2018-04-30 03:48:21| 16.0| 1.1|ERROR |HTTP transfer error: 'Timeout was reached'
Additional notes about roads and rivers type queries
The roads and rivers feature type queries could not be supported by this server because WFS 2.0 paging does not appear to be supported. Given that the datasets have about 11500 features for rivers, or around 240000 features for roads, if a single query is made the response times-out or generates transmission errors since it takes too long. Paging queries with startindex=0 and count = 1000 do not appear to work as only the first 1000 features are returned.
When Client J exercises Q4 the following issue is encounter:
https://externaltest.dev.geocloud.com:443/server/services/PuertoRicoVector/MapServer/WFSServer?SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&TYPENAMES=PuertoRicoVector%3ARIVER_C&NAMESPACES=xmlns%28PuertoRicoVector%2Chttp%3A%2F%2Fwww.esri.com%29&OUTPUTFORMAT=application%2Fgml%2Bxml%3B%20version%3D3.2&COUNT=3000&STARTINDEX=0'Rather than provide responses in pages of 3000, the service just transmits 3000 records and stops. So the result is incomplete. If we try to ask for more records, then the transmission seems to be terminated and the incomplete in terms of the xml syntax:
When Client J exercises Q7 the following issue is encounter:
Query appeared to time out. Attempted to use WFS paging but only first page was returned.
Additional notes about roads and rivers type queries
The roads and rivers feature type queries could not be supported by this server because WFS 2.0 paging does not appear to be supported. Given that the datasets have about 11500 features for rivers, or around 240000 features for roads, if a single query is made the response times-out or generates transmission errors since it takes too long. Paging queries with startindex=0 and count = 1000 do not appear to work as only the first 1000 features are returned.