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
When generating isochrones from multiple addresses, it would be great if the resulting layer includes a field that represents a join with an attribute from the original 'From address' layer, rather than just having a sequential Origin ID field.
For example, the 'Isochrone - Multiple Addresses' page in the Hqgis plugin could have the 'From address' parameter where you select the origin points, and then underneath this you could specify a 'Name field' parameter from the From address layer which is then retained after parsing through the HERE API so that the results layer includes the name field as the Origin ID.
The text was updated successfully, but these errors were encountered:
sorry for the late reply. And yes, you're absolutely right. Currently it uses the origin_id of the feature layer and let you create the joins after processing:
Result layer:
Original layer with appended $id column with name "origin_id"
So currently you can create joins based on $id in the address layer and "origin_id" in the isochrone layer. Yet I do understand that having a field that can be configured for the join makes it more convenient.
dear GitHubMLee, I can not generate isochrones. I want to generate isochrones of 100 points in the QGIS3.2. I Generated the API Key and followed the instructions and online tutorials, but nothing works. Clicking on "save credentials" I get the message "credentials saved to QGIS Global Settings", there is no file called credentials.json in my computer. thanks.
When generating isochrones from multiple addresses, it would be great if the resulting layer includes a field that represents a join with an attribute from the original 'From address' layer, rather than just having a sequential Origin ID field.
For example, the 'Isochrone - Multiple Addresses' page in the Hqgis plugin could have the 'From address' parameter where you select the origin points, and then underneath this you could specify a 'Name field' parameter from the From address layer which is then retained after parsing through the HERE API so that the results layer includes the name field as the Origin ID.
The text was updated successfully, but these errors were encountered: