Take the 2-minute tour ×
Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. It's 100% free, no registration required.

I am publishing 2 million records using ArcGIS Server. We are using ArcGIS for Desktop 10.1 and ArcGIS for Server 10.1.

We have district wise data for India (like State----District etc) all the data is coming from SQL Server.

I know that there are no limitations for ArcGIS Server and it can handle terabyte data and hence I am filtering data according to State and then District wise hierarchy and showing data after certain zoom extent. Because I know Web browsers can not display such data so dividing data by hierarchy.

Going through post1, post 2 and researching on Google too but not able to find the recommended methods to handle large data on ArcGIS Server.

So is there any recommended way or method to publish large datasets on ArcGIS Server?

share|improve this question

1 Answer 1

up vote 5 down vote accepted

If your data will not change frequently I would design your map in ArcMap with all of the scale dependent rendering and group layers based on scale. You'll have the layers you want in each scale group--meaning multiple times in ArcMap--but designed to display only the way you want it for that scale, labels, symbology, etc. Once you finish your design publish that map and then CACHE the map service. This is the critical step for fast web service, if you're planning to render the map in web clients. Your web apps will query, search, and interact with the data, but the heavy processing to generate a map image each time the user moves the map is eliminated.--cache is the key.

Caching will work on anything in your map service. It basically pregenerates the map images that your server will display. This works great with maps with layers that don't change frequently because the map server and SQL server don't have to "spin up" new images each time the map is moved. The server simply selects the map tile ( cached image) and returns that. The data behind the service is still present for query, info, search, etc. If data changes but geometry or symbology of features doesn't caching is still a great option. Even if your layers do change you can script caching to rebuild only areas that have changed. It takes a while to build your cache the first time but updates to changed areas only run much faster because you're only updating areas instead of rebuilding the entire tile library (cache).

share|improve this answer
    
Thanks for the answer.. will it applicable for Point data? because I have lots of Point data related to each state & district. –  Sunil May 25 '13 at 11:05
    
You may want to make separate cached services for your poit layers wit labels and symbology for each zoom label. Another method is to use clustering for point services. –  Brad Nesom May 25 '13 at 16:49
    
@user18424 Thanks for the answer : ) –  Sunil May 27 '13 at 9:55

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

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