...

This was an exercise to show that the decision of how to represent a data set can greatly affect the performance of its service. In this instance, would using the simpler polygons of the Real Property data source been any less true than

Suggestions

...

Data that can be cached should be cached

...

Data that can’t be cached should be stored and displayed in the fewest and simplest features possible

data may be as appropriate as using an intersection with flood waters. Creating a related points layer to use at small scales would allow users to find affected properties visually. While being unsure of the goals of the layer, showing only the current floodwater, or setting a target time value, may also simplify the data shown.

Suggestions

• Best practices for publishing and symbolizing data must be followed regardless of our hardware.

  • Create map caches where possible

  • Data that can’t be cached should be stored and displayed in the fewest and simplest features possible

  • Follow ESRI’s Performance tips for uncached maps

• Re-project all data to WGS84 Web Mercator

  • Avoid all re-projection on the fly

  • Debate?

• Test performance on all layers?

  • Web hooks, test new layers?

Also, when reports of poor performance are made, create a test using this framework, and track the improvement as different options are considered.