I don't have server 10.7 yet but I wanted a way to aggregate query results server side and should be getting 10.7 in the near future. However, based on the example given, I don't understand how the Query Top Features operation differs from any other standard query that includes order by field and results record count. Maybe it's a bad example because it looks like it only returns a single value from groupByFields.
Using the example given, I would like to assume that there would actually be more than one 'employeeName' returned but like I said, the example is not clear since it just gives a single employeeName but 2 counts as per the topCount. Can someone confirm that given a larger data set you would get something like the extended example below?
{ "exceededTransferLimit": false, "features": [ { "attributes": { "employeeName": "Jason", "deliveryNumber": 25 }, "geometry": { "x": -76.9505202472378, "y": 36.02168768903079 } }, { "attributes": { "employeeName": "Jason", "deliveryNumber": 24 }, "geometry": { "x": -80.28022828451529, "y": 34.9904342763449 } },
{ "attributes": { "employeeName": "Jill", "deliveryNumber": 54 }, "geometry": { "x": -76.9505202472378, "y": 36.02168768903079 } }, { "attributes": { "employeeName": "Jill", "deliveryNumber": 53 }, "geometry": { "x": -80.28022828451529, "y": 34.9904342763449 } },
{ "attributes": { "employeeName": "Albert", "deliveryNumber": 4 }, "geometry": { "x": -76.9505202472378, "y": 36.02168768903079 } }, { "attributes": { "employeeName": "Albert", "deliveryNumber": 3 }, "geometry": { "x": -80.28022828451529, "y": 34.9904342763449 } }
],
...}
