On 13-Sep-17 05:20 PM, marc marc wrote:
Le 13. 09. 17 à 02:04, Warin a écrit :
If you need to tag a specific check than possibly check_date:flow=*
it doesn't say how the check was done... if you read flow number
from a info panel, an opendata database or do a functional check.
it just mean
what can a operational_status be net specific enough for a hydrant ?
if you test that water is going out the hydrant, I didn't see what is
not specific enough to call it "a functional check"
+1
Let's say if the hydrant meets the requirements in terms of
pressure/flow rate it status is ok.
Le 13. 09. 17 à 02:04, Warin a écrit :
> If you need to tag a specific check than possibly check_date:flow=*
it doesn't say how the check was done... if you read flow number
from a info panel, an opendata database or do a functional check.
it just mean "you do a check related to the flow"
>
On 13-Sep-17 08:52 AM, Richard Welty wrote:
On 9/12/17 6:44 PM, marc marc wrote:
Le 12. 09. 17 à 22:52, Viking a écrit :
In the discussion page [0] someone says that check_date=* is a synonymous of
survey:date=* in common usage. Is this correct? Should we use another tag
functional_check=* ?
On 9/12/17 6:44 PM, marc marc wrote:
> Le 12. 09. 17 à 22:52, Viking a écrit :
>> In the discussion page [0] someone says that check_date=* is a synonymous of
>> survey:date=* in common usage. Is this correct? Should we use another tag
>> functional_check=* ? But I don't like to introduce a new
Le 12. 09. 17 à 22:52, Viking a écrit :
> In the discussion page [0] someone says that check_date=* is a synonymous of
> survey:date=* in common usage. Is this correct? Should we use another tag
> functional_check=* ? But I don't like to introduce a new tag.
>
> [0]
>
