Include request
Great idea
What about Excel reports?
For the report in excel, it would also be worth the change, since the user almost always looks for a specific point to consult the address, so before that, I imagine there is no need to show the address at all points in the report. The user will click on "view address" at a specific point of interest of him, and the rest continue as links. This will greatly improve the consumption of requests to the geocoder server. What do you think?
But what about trip report for example? I don't want to click on links in Excel. I just want to print a report with addresses.
I see it as a good optional behaviour, not a complete replacement.
By the way, if you want it ever to be implemented, you need to create a feature request on GitHub.
The travel report, we can leave as is, as it has different characteristics of the route report. I guess the ones that consume the most are the user area reports, excel report and vehicle status address. What we can do in the excel report, would be to automatically filter a repeated address, for example, if the device stayed in the same address for a certain period of time, when issuing the report, we would not see several points in the report, with date and time Different but with the same position, with this idea, when issuing the report, the system would show a unique position, with a schedule basically like this:
08h to 10h / address x
10h to 10:30h / address xx
instead of
08: 01h / address x
08:05h / address x
08:10h / address x
you understand? We would filter several equal positions in only one, and show the time the device stayed at that same address until it changed position. It would be one more option, and so the report would show the address for it to be viewed and printed, and we would have an economy in the use of geocoder requests.
There is already an option to not do a reverse geocoding request if device is not moving. I don't understand how "we can leave as is". It requires address to be available in the positions. Maybe you misunderstand how it works. Reverse geocoding is done when locations are stored in the database, not when you make a report.
I understood, forgive me if I said something wrong. "We can leave it as it is" would keep the sample address in the travel reports. Since geocoding is done when places are stored in the bank, this totally changes my concept on the subject. Was there any idea related to this so that the requisitions could be spared in some way, increasing their durability? Or when using the requisitions to the maximum, it becomes obligatory to hire a paid plan to increase the number of requisitions.
I think your original idea is still valid, but it should be options. Some people might not care about address in Excel reports. In that case we can disable automatic saving of address and show links in the web app.
As for the option not to make a reverse geocoding request if the device is not in motion, I looked in the configuration file, but I did not find this option, could you show me what it would be and how to use it?
It would be great then, instead of being a total change, it would be another configuration option when issuing the report. Now, would that save you from consuming requisitions?
Requisitions? It will obviously save quota because we would only do request when user clicks on the link.
That's exactly the point, use the quota only when the user clicks the link. It would be much better for sure.
So how should I proceed? In github should I put the post link for our conversation? To serve as a history
Yes, definitely provide a link to this discussion.
Anton, I'd like to check with you for a situation involving the sample address on the system. Today what happens, with a quota of 10,000 daily requests, with an average of 50 registered devices, the system easily consumes all this quota quickly, taking into consideration that the device updates every 1 minute, perhaps due to the sample Of the address in all points of the reports, what I would like to propose to you, to include in a future update if possible, is to change the way the address is shown in the reports, because each report issued, each address shown is a request, This ends quickly with the daily quota of the geocoder, so instead of showing the address when issuing a report, you put a link, which when clicked shows the address itself, this would only make points of interest to the user Shown. This idea would also serve the address field in the "Status" tab of the device. I'll cite an example in the following images