Dynamic Map Service maxRecordCount ignored

[ChrisDalla_Piazza]

Hello,

I thought at one time there was a way to protect a dynamic, non-cached map service from attempting to draw too many features by using maxRecordCount.

But my map service is ignoring this parameter.  This link seems to indicate the capability was recently removed although it references AGO services.

Does this capability to limit feature count drawn dynamically still exist?

Thanks for your help!

[berniejconnors · Accepted solution]

Chris,

The max record count does not apply to the number of features drawn for a map image request (export). The max record count applies to a query request. For example, I publish a dynamic map service for our parcel map and it includes about 600,000 polygons. The MaxRecordCount is set at 2000. This will limit the number of records that can be returned when a user attempts to query the map service. A query for a very large number of records will take longer and consume more server resources and slow down responses for all of your other users. If you want to limit the number of features drawn when your map service does an export operation you should apply scale thresholds in your map document. In our parcel map service the Min Scale is set to 31,999 to limit the number of parcels that are drawn.

The support document you referenced refers to a feature service, not a map service.  When a user requests a map draw from a feature service the vector data is transferred to the client and rendered on the client side.  When a user requests a map draw from a map service the service will generate an image of the data on the server side and send a jpg or png file to the client.

Bernie.

[ChrisDalla_Piazza]

Hi Bernie,

Thanks for the pointers!

One of the other parcel viewers I was comparing to is querying a map service for geometry rather than using the server side rendering.  That solves the mystery!

[TanuHoque]

Thanks @berniejconnors.

Just want to add a note to that. MaxRecordCount basically sets the max number of features/rows you can get in a single query response.

When `supportsPagination = false` (e.g. with shapefiles), that means a hard limit. You can't access any features/rows beyond that unless you set different where-clause or spatial-filter.

When `supportsPagination = true` (with file gdb or enterprise db), you can use resultOffset and resultRecordCount parameters to page through to retrieve records beyond the maxRecordCount. Please note, for each query/response you are still limited to maxRecordCount.

Therefore, when you add/use a 'feature layer' in your web app that points to a 'sub layer of a map service or a feature service', the client app uses pagination technique to retrieve all features so that you won't see any gaps etc. while having them all drawn on your client app.

I hope this helps.