Parquet Drawing Time Improvement

[FRAPKimberlyWallin]

I have a wall to wall 30-m vegetation raster dataset for California which has two fields I'd like to serve to the public via AGOL.  One is a 13 class vegetation type, and the other a 62 class vegetation type.  I've converted these to polygons (not simplified, kept as single part) and published as parquets, but I'm finding their drawing times to be exceptionally slow.

It seems they are drawing faster as single part polygons, instead of as multiparts, but can you please help with drawing speeds?

I'm attaching a sample of drawing time in southern CA.

[JessiePartenoEsri]

Hi Kimberly, 

Thanks for sharing this example. Drawing performance for a statewide vegetation dataset can be impacted by several factors, including the total number of features, vertex density, and the number of vertices per feature—similar to what you would see with hosted feature layers.

In cases where multipart polygons are generated from raster analysis workflows, the resulting features can contain a very large number of vertices. Converting the data to single-part features is often recommended and can improve drawing performance by reducing the complexity of individual geometries being rendered.

Since Parquet feature layers are currently in beta, we're actively working on performance improvements and optimization opportunities. We'd be interested in learning more about your dataset characteristics (feature count, vertex count and file size) to better understand this specific use case and help guide future improvements.