Knowledge RAG
Submit principleDesign Knowledge Base
Community-maintained principles reviewed before publication and retrieved as Agent design constraints.
2 published principles / 192 in library
Data Visualizationmaps / geospatial
Map Data Attribution and Alternatives
Map interfaces must separately record runtime library, tiles, styles, glyphs, sprites, geodata, and provider attribution, while providing list/table alternatives and keyboard-reachable paths.
A map is not a background image. It combines complex data visualization, interactive controls, and licensed materials; users must understand location, scope, selected object, data source, update time, and alternate access paths.95%Visual Foundationsmap / geospatialMap and Geospatial Layout
Map and Geospatial Layout turns a frequent interface judgment into an executable constraint before generation.
Geospatial interfaces depend on synchronization between location, scope, objects, and selection state.84%