Administrative mapzones - Giswater/giswater_dbmodel GitHub Wiki

The administration of a drinking water network requires mapzones in terms of administrative boundaries. As a result, two diferent types of administrative boundaries have been defined: Exploitation & Municipality.

Both have rules and special capabilities. Let's explain the characteristics of some default value variables that acts with this mapzones:

basic_search_exploitation_vdefault: User default value for exploitation used on search tool button.

basic_search_municipality_vdefault: User default value for municipality used on search tool button.

edit_municipality_vdefault: User default value for municipality, used when new feature is inserted into the network.
If the variable is disabled, geospatial intersection will be executed using the geometry of new feature and municipality layer with limit 1 and value will be showed on feature dialog. On the other hand if variable is enabled value shall prevail over geospatial intersection.

edit_exploitation_vdefault: User default value for exploitation, used when new feature is inserted into the network.
If only one exploitation is chosen on the selector, this value will be automatically set on newly inserted feature. If more than one exploitation is selected, this variable will be automatically disabled. In this case, if user wants, it can be set using config form. If the variable is disabled, geospatial intersection will be executed using the geometry of new feature and exploitation layer with limit 1 and value will be showed on feature dialog. On the other hand if variable is enabled value shall prevail over geospatial intersection.
Is there any case where user should activate variable in terms of overwrite geospatial intersection?
Yes, there is. Imagine, that you have selected two exploitations, because you want to see both on the map, and let's say that they overlap. In this case, no geospatial intersection is possible in order to get default value of exploitation.

Remember that on insert process, user can always modify combo value of the feature. We are talking about proposed value showed on form after clicking on the map but before inserting data on the DB.