You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not an issue but a feature enhancement. I use this tool a lot - it's one of the best QGIS plugins in my opinion (thank you Riccardo!). However, it could be enhanced with the following:
Upgrading to connect with the HERE v8 routing engine (https://isoline.router.hereapi.com/v8/isolines?). This would require some changes to the coding to use new format API specs - eg 'transportMode' rather than 'Mode'
Enabling other API parameters such as 'optimizeFor' and 'shape[maxPoints]' to control granularity of output
Retaining attributes of the original features (ie creating the table join as part of the output), preferably with the choice of which attributes to retain.
Unfortunately I have no coding experience and having gone into the hqgis.py file I am lost as to how to alter the code. But if others could help, this could become an incredible tool!
Thanks
Matt
The text was updated successfully, but these errors were encountered:
Hi Matt, my latest set of commits is migtrationg everything to v8 or 7.2 (irsoline routing is still 7.2, isn't it?)
regarding the last point: every result layer which has a origin layer will have a field called origin_id and this is the basis for every join. Or do you think it would be better to allow the user to set a "keep this field in the result dataset please"?
The new version of the plugin is available via the plugin manager
Riccardo, thanks for the latest update. Does this implement v8 for isolines?
I'm aware that the origin-id field is a usable join field, but I do think that the ability to retain other fields in the results would make it easier for users to analyse the results.
In relation to my second suggestion (opening up other parameters such as those that affect the resulting shape of the isoline) this would be a fantastic addition. Is this something you are likely to work on for future updates?
Thanks again for a great tool!
This is not an issue but a feature enhancement. I use this tool a lot - it's one of the best QGIS plugins in my opinion (thank you Riccardo!). However, it could be enhanced with the following:
Unfortunately I have no coding experience and having gone into the hqgis.py file I am lost as to how to alter the code. But if others could help, this could become an incredible tool!
Thanks
Matt
The text was updated successfully, but these errors were encountered: