Right now only two index types are supported: the classic "Streets and selected amenities" index, and the very specific POI marker index currently exclusively used for requests coming in via the neighborhood maps frontend.
Ideally there should be a plugin API for custom index types that allows for:
[ ] different data choices
[ ] different presentation
Some preconditions:
[x] split StreetIndex classes into GenericIndex handling the classic index rendering (the "how") and actual StreetIndex* class collecting the data to be rendered (the "what")
[x] add alternative HealthIndex* classes as alternative to StreetIndex, using the same GeneralIndex rendering, but collecting a different set of POI categories and no streets at all
[x] add name of index class to use to job settings
[x] have single and multi page renderers choose actual index class to use on above new setting
Right now only two index types are supported: the classic "Streets and selected amenities" index, and the very specific POI marker index currently exclusively used for requests coming in via the neighborhood maps frontend.
Ideally there should be a plugin API for custom index types that allows for:
Some preconditions: