What is the maximum number of records returned by WFS protocol? What is maximum number of records returned by a Feature Layer in ArcGIS Server 10.1? What is maximum number of records the ArcGIS JavaScript 3.1 feature layer can display?

I am facing a peculiar problem in ArcGIS Server 10.1 and ArcGIS JavaScript API 3.1. In the capability tab, if I set the maximum number of records to more than 13,000 records, then the layer is not displayed. I am using a relational database and joining 5-6 tables to get the desired data.


It sounds like you've reached your browser's memory limits in regards to the data returned by arcgis server 10.1. The maximum number of records returned by WFS and ArcGIS Feature Layer depend on how it was set up by the server (default is 1000 for anything running through ArcGIS Server). You can reconfigure it to send more, but then you run into poor browser performance.

The question is, do you really need to juggle that much data client-side?
Here are some links to help with that juggling act.
High Performance Web Apps
Be Successful at Geoprocessing
Maintaining High Performance (Derek has some great insight into your direct question).
You don't mention the data "type/use" for your data, this article about parcel fabric has some good memory joggers that can be helpful. Best practices for migrating
Finally a must link to the video section of the recource center. This one with Sterling.
Best Practices for Designing Effective Map Services
Point Clustering can help also
It seems that this subject just keeps poping up. Here is another blog from today.
Even if you don't use cache it has more usable information.
Accelerating map caching creation

  • Actually feature class has 92 thousand records.but I need to show around 20-30 thousand data.which might increase over the period.so any suggetion.Thanks.
    – Gunner
    Nov 19 '12 at 16:53
  • 2
    but the question is do you need to "show" that many. What I do is use a scale dependent view and let the request for more data be driven by actual view determining what data is returned. Still can be a large request but much smaller than all the data every time a request is made.
    – Brad Nesom
    Nov 19 '12 at 16:58
  • 1
    What you could do is create a graphics layer that shows regions, get the count of how many features match the query you pass in, by region, and display that number in the center of each region. Or you could try point clustering, per this example: help.arcgis.com/en/webapi/javascript/arcgis/help/…
    – raykendo
    Nov 19 '12 at 17:54
  • @BradNesom how did you do the scale dependent request.Could you direct me to some link.Thanks.
    – Gunner
    Nov 20 '12 at 6:57
  • 2
    when setting up the service in arcmap. you can set the layer properties to "not show out beyond" a certain scale. You can then create another simplified version of the data (or use geoprocessing) to show when you are zoomed out. when a user selects data (with whatever means you are programming) that zooms in past the simplified version. There are many techniques that are used to accomplish this simple explanation. But the bottom line is the mapmaker is responsible for creating a managable view of the data that answers all the questions of the user.
    – Brad Nesom
    Nov 20 '12 at 14:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.