I am looking at posting our District's 2m Lidar derived contour data on AGOL. When we initially loaded the data up to AGOL we noticed that we were chewing through our credits at a rate of 53 credits per-day, by the end of the year we would have been in the red. We had loaded our 2 and 5m Contour data which equated to 6GB of data on AGOL.
The contour data is roughly 3GB in size and I was wanting to know if anyone has any good methods for reducing the overall footprint (size) of the data for loading into AGOL as a feature service or tile service.
I initially thought that I would dissolve the Lidar Data and then explode the data to ensure where features aren't next to each other are individual features. What I noted when I ran this process is that my machine froze after about 20 mins of processing/dissolving the data.
2m Contour Coverage