Point Layer Best Practices

06-20-2017 08:50 AM
New Contributor III

I had asked this in another thread, with no replies. I thought I might add it here as well:

I am relatively new to the ArcGIS platform. I have been using Google Fusion Tables to display a lot of my data. I have seen the drawbacks of having too many points displayed on one map, so I need clarification of the best practices when handling a list of points that number at 3,000+.


All of my locations are of a similar geographic feature (waterfall), in the same state. The state is broken up into tourism regions, which I could use for filtering purposes, but at least two of these regions would have 1,000 or more locations inside of it. They are further broken into counties. There will be text, at least one photo and eventually at least one GPX (or comparable trail mapping file) file.


My question centers around the best way to create maps ( the feature layers) that will cause the least amount of lag while loading, but also not hinder the built in functionality or require the need for multiple maps. Is this a matter of breaking the data into separate layers by region, county or zip code? 


I have wasted countless hours in the past and want to be sure when I set this up it is done right from the start.


Any suggestions will be greatly appreciated!
An example of my present map is: Search Waterfall Locations In New York | Dig The Falls 

0 Kudos
0 Replies