Tabulations outstanding issues

[GoogleCodeExporter]

In writing a Case Study on Tabulations (Tools | Tabulate), I note a number of 
outstanding Tabulation issues

1. Defect: The drop down list includes a typo "Tillage practive - dominant 
(area)(class)". I am unsure where the list comes from as it is ok in the Layers 
Table (where I can edit it).

2. Enhancement: The tabulations are currently missing the contextual layers

   Surface geology (#60 Miles to get 250m grid data from Kristen Williams)
   Koppen Climate Classification*
   Koppen Climate Classification – sub areas*
   Land Cover Type – IGBP (2011)*

Original issue reported on code.google.com by leebel...@gmail.com on 28 Jan 2014 at 12:59

[GoogleCodeExporter]

Updates made to the layer names in the layers table are not flowing to the 
fields table.  Ran an update on dev and prod to update the fields table layer 
names.  This corrects the tabulations names.

Need to make it so the updates are automatic.

Original comment by adam.col...@gmail.com on 20 Mar 2014 at 11:52

• Changed state: Started

[GoogleCodeExporter]

Trigger added to push layer displayname changes to fields table.  This will 
keep the table names displayed with tabulations up to date.

Original comment by adam.col...@gmail.com on 24 Mar 2014 at 1:49

• Changed state: Fixed

[GoogleCodeExporter]

I noted that 

1. the layers names are not consistent between dev and prod (e.g., IBRA 7) and
2. the layer "stubble practice - dominant (number)" starts lower case and is 
therefore not sorted correctly.

Original comment by leebel...@gmail.com on 24 Mar 2014 at 1:57

[GoogleCodeExporter]

I am unsure of the dev/prod sync process, is it one of these?
1. After a layer is deployed to prod only prod is kept up to date with edits.   
2. All edits are done twice to keep dev and prod in sync.  
3. Edits are done only on dev and changes are deployed to prod regularly.  In 
this case no edits are made to layer properties on prod directly.

Original comment by adam.col...@gmail.com on 24 Mar 2014 at 2:34

[GoogleCodeExporter]

1. This is not advisable

2. This should be avoided

3. Yes please. Is there a process setup for the layers table dev -> prod?

PS: The 'Enhancements' (comment #1) aspect have not been addressed. E.g., why 
are contextual layers not tabulated. In some cases such as the GER layers, the 
spatial extent of the layer or that the layer is a single polygon would omit 
it. Where is the flag? Not in the layers table - and probably should be. In 
short, this has to be a part of the layer ingestion process - and one I 
probably need to advise on or prodded to edit the dev layers table.

Original comment by leebel...@gmail.com on 24 Mar 2014 at 2:41

• Changed state: Started