POST
|
The State of Hawaii has a little over 200 data layers in our ArcGIS Open Data Portal: http://geoportal.hawaii.gov/. Joan Delos Santos
... View more
02-12-2018
08:40 PM
|
0
|
0
|
405
|
POST
|
We are weighing the relative impact of serving a large data set in ArcGIS server as a map service with a very large MaxRecordCount or as a feature service with a smaller MaxRecordCount. There is no need to edit the data via the feature service - the service is meant to be for display and query purposes, not editing. My question is - which is the better solution - a max record count of 400K on a map service or creating a feature service for the layer? We have a statewide parcel layer with about 400K records that is hosted as a map service in Esri Managed Cloud Services with a MaxRecordCount of 5000. A consultant is developing a custom app using the JavaScript API in which there is a need to query the entire dataset. When MaxRecordCount is 5000, any query (using QueryTask) against a layer (e.g., parcels) in that service will only return the first 5000 rows – for example, if the application sends a query for all parcels greater than 1000 acres, and we then want to further filter the results (e.g., those parcels having zoning of “Urban”), the second query/filter will only be applied to the first 5000 records returned – even if there are more parcels meeting the criteria - so the results will be incomplete. When we increase the MaxRecordCount to a number larger than the total number of state wide parcels (~377K), like 400K, the queries will return the complete set of features the meet the criteria. However, we don't really want to increase the MaxRecordCount to 400K. Esri suggested the solution below, which requires a feature service rather than a map service: If the server supports pagination, the FeatureSet returned as a result of executing the query task contains exceededTransferLimit boolean. When that boolean is true, it indicates there are more features that matched your query than what was returned. Now, you can use Query.start and Query.num parameters to fetch those additional features that satisfied your query. Repeat the same query with new values for “start” and “num” parameters until FeatureSet.exceededTransferLimit becomes false – at which point you would have fetched all features that satisfied your query. Your sequence would like this: Query 1: start = 0; num = <MaxRecordCount> returns FeatureSet.exceededTransferLimit = true start = 1 * <MaxRecordCount>; num = <MaxRecordCount> returns FeatureSet.exceededTransferLimit = true start = 2 * <MaxRecordCount>; num = <MaxRecordCount> returns FeatureSet.exceededTransferLimit = true …and so on until exceededTransferLimit becomes false. Would appreciate any guidance or insights...
... View more
06-13-2017
01:32 PM
|
2
|
1
|
1230
|
POST
|
Ok, got it, thank you very much! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Joan Delos Santos Hawaii Statewide GIS Program State of Hawaii, Office of Planning 235 S. Beretania St., 6th Floor Honolulu, HI 96813 Phone (808) 587-2895
... View more
10-27-2016
12:01 PM
|
0
|
0
|
829
|
POST
|
Hello, Thank you Courtney. By resetting the cache, do you mean updating the index for that service? Also – I guess that we won’t know which datasets are problem datasets unless someone lets us know? It’s not reasonable for us to have to reset the index for each dataset… Are you saying that the http issue is resolved in that I shouldn’t have this problem any longer? Thank you, Joan
... View more
10-25-2016
01:59 PM
|
0
|
2
|
829
|
POST
|
Wondering whether this was ever resolved? We are having similar issues with our Open Data site (geodata.hawaii.gov) - we are in the process of making this our primary distribution method - 300 layers - however, there are a multitude of problems, primarily related to when data is cached. The latest issue is that a download of our contours (100 foot contours, Hawaii Island) does not complete (shapefile not available) - eventually, there is a message offering to use "unfiltered version created on 1/6/16" - however, we updated all of our data in June and again on October 6. So it is offering old data. We rebuilt the index last week and the item description says that the data was last updated 8 days ago...
... View more
10-25-2016
01:21 PM
|
0
|
4
|
829
|
Title | Kudos | Posted |
---|---|---|
2 | 06-13-2017 01:32 PM |
Online Status |
Offline
|
Date Last Visited |
01-27-2021
03:09 PM
|