For a vast amount of applications with the TQL I need a TQL queries to get volume, min, max, average etc on buildings. The query functions already exist but they can’t be combined with buildings. This for example can be done with AREAS already. Therefore the current way is to make a copy of these features as areas and then run the queries.
I’ve made recommendations for the expansion of TQL queries in several locations but I see that the idea push is not one of those. Hence the request here aswell
If I want to switch to another version of my project, I first have to close Tygron, restart, change the settings of the project in my account, then start the project in the other version. It would be nice if it is possible to switch to another version without having to restart Tygron as a whole. This will help a lot when working on a project and you want to try different situations or builds.
Would it be possible to add the option to insert a map scale and a compass under tools -> screenshot. This way we could directly insert images and gifs into presentations and documents without having to add the map scale and north arrow in for example qgis.
Arcgis online does offer a scale, but when you do that, the legend is lost which is also very important for the images.
Being able to use queries like “GRID_AVG” (and many others) on building types. Core principle being a building and GRID combination where “LOTSIZE” is not sufficient. This combination currently is still not possible.
GRID_MAX and GRID_MIN combinations would also be a great addition to this functionality
At this time the arrows displayed for directional results types such as the Water Overlay’s direction result type, are limited to those built-in result types. All other Grid Overlays will use the default display styling for interpolated colors related to values. Therefore I need to access the results in an alternative GIS package such as QGIS, which offer more options for adding specific styling rules to your data. Would it be possible to make this an option? In my case this is usefull when I want to modify the Water Overlay’s direction result type with the combo-overlay.
The possibility to visualise cloths or canvases as a measure against heat stress. Currently, it is possible to create a workaround to calculate the impact of measures that create shade but do not obstruct wind. However, the visualisation of this is not useable.
On the LTS, an overlay showing the average PET during the day was available, but this is not available anymore on the Preview. Could you reintroduce this?
Currently, the distance sight overlay has a SOURCE_HEIGHT_M attribute, which dictates the height at which a distance sight ray is emitted from the structure with the distance sight attribute. As analyst of prospective plans, I would like the ability to configure a TARGET_HEIGHT_M as well, which would be the height at which a ray would be received.
I would like to be able to make this TARGET_HEIGHT_M negative as well, so that I can exclude the tops and far-sides of constructions from my studies.
It is currently possible to use the culvert as input for your watershed when you define a watershed_area. The algorithm combines the DIRECTION with the OBJECT_FLOW to connect the watersystem and gain an insight in the watershed connected to that point. The culvert setting however does not work when not defining the final interest area.
I frequently come across the use case where you want to understand the system and see the large watersheds of your entire system, thus the major hydrological (sub)systems. You don’t know the endpoints beforehand thus defining these is not an option. This results in the advanced option “Use culvert…propagated” to have no influence on the result.
To sum-up: Combining the “Discharge Remaining Water” result to larger Watersheds based on structure flow (mainly culverts).
The gridvalue of the Watershed overlay is not visible when clicking on the overlay. As information is the link to the discharge areas provided. The gridvalue however is needed for calculating (with TQL) the size of the watershed. To know the gridvalue, the overlay needs to be exported. It would be convenient if the gridvalue is also provided when clicking on the Watershed Overlay.