Currently, features listed in the navigation pane are sorted simply by their string names (the name property in their GeoJSON properties member). This is not ideal when displaying items whose name begins with a number. If we allow for an optional sortKey property, that could be used instead of the name, but only if it exists, so no existing code will break.
Currently, features listed in the navigation pane are sorted simply by their string names (the name property in their GeoJSON properties member). This is not ideal when displaying items whose name begins with a number. If we allow for an optional sortKey property, that could be used instead of the name, but only if it exists, so no existing code will break.