Job description
Our new system has been working for some time in the production version for a certain group of users, however, users have some habits from the old system regarding "service impressions" and not quite the new ones they like.
Test login to the old one:
and to the new one:
In short: you have to adjust the behaviour of individual elements to how it was in the old one.
1. Click on the object on the list - on the map we have its approximation (the scale is to be the same), in addition, the icon of the selected object cannot be aggregated with others only a single one. In the new group, up to 2 icons are grouped if they are in the neighbourhood and the aggregation function is enabled. The minimum for aggregation should be 5.
2. The selected object is to be automatically tracked, but the map should not center at each change of position, but only when the object's icon leaves the visible area (this is the old one), but you can still give a margin to center the map when approaching the view border instead of leaving it.
3. Clicking the icon on the map will cause selection of the object on the list and its scrolling to be visible and not hidden.
4. The selection of the object deletes the previous selections, eg a route generated for the other object on the map.
4. Choosing by clicking the icon or label (in the new label does not select the object)
5. The label of the selected object is to be distinguished from the others, eg change the colour/thickness of the font.
Manufacturers of the new system do not offer "custom development", but allow any modification in the web application. If I present it in the form of a proposal for the next issue, I can wait a long time and there is nothing certain that everything will be done just like my users expect.
The difference between systems is to use leaflet js in the new and google maps API in the old one. In the leaflet, you can probably do the same.
The next order is reports.
