lightweight/right-tree
1
0
Fork 0
Code Issues 17 Pull requests Projects Releases Packages Wiki Activity Actions

Turn off soil order exclusion filter for Dune System, Coastal Banks & Bush #24

New issue
Closed
opened 2021-11-18 13:32:19 +13:00 by danalambert · 2 comments
danalambert commented 2021-11-18 13:32:19 +13:00 (Migrated from gitlab.catalyst.net.nz)
Copy link

In the spec there is a statement
10 (10) Dune System, Coastal Banks & Bush
Use zones and designated column headings [CV-DI] & [DQ-DT]

Unlike other statements similar to this, there is no prefix Ignore Soil Order -. I'm just wondering if this is a typo or for this case we do NOT ignore soil order?

(WW suggested answer: ?)
This was just a reminder that this relates to the diagrams for sand dunes and for the spray zone (banks, cliffs and coastal bush).

I'm assuming this means we just have to turn off the soil order exclusion flag for these zones.

> In the spec there is a statement > 10 (10) Dune System, Coastal Banks & Bush > Use zones and designated column headings [CV-DI] & [DQ-DT] > > Unlike other statements similar to this, there is no prefix `Ignore Soil Order -`. I'm just wondering if this is a typo or for this case we do NOT ignore soil order? > > (WW suggested answer: ?) > This was just a reminder that this relates to the diagrams for sand dunes and for the spray zone (banks, cliffs and coastal bush). I'm assuming this means we just have to turn off the soil order exclusion flag for these zones.
danalambert commented 2021-11-18 13:32:20 +13:00 (Migrated from gitlab.catalyst.net.nz)
Copy link

assigned to @danalambert

assigned to @danalambert
danalambert commented 2021-11-18 13:52:34 +13:00 (Migrated from gitlab.catalyst.net.nz)
Copy link

mentioned in merge request !25

mentioned in merge request !25
alistairmcintyre (Migrated from gitlab.catalyst.net.nz) closed this issue 2021-11-18 14:13:06 +13:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
v1.0.1
No results found.
Labels
Clear labels   
Bug

A software bug we've noticed. (These may not necessarily be show-stoppers)

  
Client: Biosphere Capital

   
Client: Central Hawkes Bay District Council

   
Client: Forward Works Viewer

   
Client: Kea/Kākā Databases

   
Client: Otorohanga District Council

   
Stage: Blocked

Something is causing us to be unable to currently fix this issue.

  
Stage: Doing

An issue that's assigned and being worked on

  
Stage: Peer review / Staging

An issue waiting to be given the all clear for production deployment.

  
Stage: Ready

For tickets that have been quanitifed, have acceptance criteria, and can be safely moved to the To Do column.

  
Stage: UAT AT

Work waiting to be deployed to production.

No labels
Bug
Client: Biosphere Capital
Client: Central Hawkes Bay District Council
Client: Forward Works Viewer
Client: Kea/Kākā Databases
Client: Otorohanga District Council
Stage: Blocked
Stage: Doing
Stage: Peer review / Staging
Stage: Ready
Stage: UAT AT
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lightweight/right-tree#24
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?