`, under the `<-- Subcenter 0 -->` comment, add an entry:
+
+
+ CPTI
+ 161
+ 0
+ 600640
+
+ 97
+
+
+
+Save the model file and restart edex:
+
+ sudo service edex_camel restart ingestGrib
+
+Now if you drop `cpti.grib2` into the manual endpoint again, it should ingest without any persistence errors.
+
+---
+
+## Adding a Table
If you ingest a piece of data and the parameter appears as unknown in the metadata database, ensure that the correct parameter tables are in place for the center/subcenter.
-Make sure the latitude and longitude entries in your coverage specification file match those of your ingested raw grib file. There is a tolerance of +/- 0.1 degree to keep in mind when defining your coverage area.
+The tables are located in **/awips2/edex/data/utility/common_static/base/grib/tables/**. They are then broken into subdirectories using the following structure: **/[Center]/[Subcenter]/4.2.[Discipine].[Category].table**.
-If some of the information is unknown, using a grib utility application such as *wgrib* and *wgrib2* (not delivered) can be useful in determining the information that must be added to correctly process a new grib file.
+### Grib products
+
+The center and subcenter have been identified previously [here](#grib-products) and [here](#grib-products_1), as 7 and 0, respectively. So, the corresponding directory is:
+
+ /awips2/edex/data/utility/common_static/base/grib/tables/7/0/
+
+To find the **discipline** of a grib product, you need the **process** and **table** values from the grib file. These are output with the `wgrib -V` command:
+
+
+wgrib -V wrf.grib
+rec 799:27785754:date 2014102318 ALBDO kpds5=84 kpds6=1 kpds7=0 levels=(0,0) grid=255 sfc 6hr fcst: bitmap: 736 undef
+ ALBDO=Albedo [%]
+ timerange 0 P1 6 P2 0 TimeU 1 nx 201 ny 155 GDS grid 3 num_in_ave 0 missing 0
+ center 7 subcenter 0 process 89 Table 2 scan: WE:SN winds(grid)
+ Lambert Conf: Lat1 42.283000 Lon1 -72.361000 Lov -67.077000
+ Latin1 45.368000 Latin2 45.368000< LatSP 0.000000 LonSP 0.000000
+ North Pole (201 x 155) Dx 4.297000 Dy 4.297000 scan 64 mode 8
+ min/max data 5 21.9 num bits 8 BDS_Ref 50 DecScale 1 BinScale 0
+
+
+For our example, the process is **89** and table is **2**. Next, take a look in:
+
+ /awips2/edex/data/utility/common_static/base/grid/grib1ParameterConvTable.xml
+
+And find the entry that has grib1 data with TableVersion 2 and Value 89:
+
+
+ 7
+ 2
+ 89
+ 0
+ 3
+ 10
+
+
+Here, we can see the discipline and category values (referred to as x above) are 0 and 3, respectively.
+
+So, the table needed for our example file is:
+
+ /awips2/edex/data/utility/common_static/base/grib/tables/7/0/4.2.0.3.table
+
+### Grib2 Products
+
+If you are using a grib2 file, then you can use either the log output or the `-center`, `-subcenter`, and `-full_name` options on `wgrib2` to get the center, subcenter, discipline, category, and parameter information:
+
+The table would be found in the directory structure using this file's center and subcenter. The center can be found by either:
+
+ * Running the following command:
+
+ wgrib2 -center cpti.grib2
+ 1:0:center=US NOAA Office of Oceanic and Atmospheric Research
+ ...
+
+ And then looking up the corresponding value for "US NOAA Office of Oceanic and Atmospheric Research" at [**this website**](https://www.nco.ncep.noaa.gov/pmb/docs/on388/table0.html), where it happens to be **161**.
+
+**OR:**
+
+* Running the following command:
+
+wgrib2 -varX cpti.grib2
+ 1:0:var209_255_1_161_3_61
+...
+
+ Where the 4th argument after "var" is the center id, in this case **161**.
+
+To get the subcenter, simply run:
+
+wgrib2 -subcenter cpti.grib2
+ 1:0:subcenter=0
+...
+
+The subcenter of this file is **0**.
+
+So based on the center and subcenter, the corresponding directory is:
+
+ /awips2/edex/data/utility/common_static/base/grib/tables/161/0/
+
+To find the exact table, we need the discipline and category:
+
+
+wgrib2 -full_name cpti.grib2
+ 1:0:var209_3_61.500_m_above_mean_sea_level
+ ...
+
+
+In this case the **discipline is 209** and **category is 3**, so the corresponding table is:
+
+ 4.2.209.3.table
+
+So, the full path to the corresponding table would be:
+
+ /awips2/edex/data/utility/common_static/base/grib/tables/161/0/4.2.209.3.table
+
+The parameter ID was also listed in that output as **61**. Make sure that specific parameter information is defined in the table:
+
+...
+56:56:Reflectivity at -20C:dBZ:ReflectivityM20C
+57:57:Reflectivity At Lowest Altitude (RALA):dBZ:ReflectivityAtLowestAltitude
+58:58:Merged Reflectivity At Lowest Altitude (RALA):dBZ:MergedReflectivityAtLowestAltitude
+59:59:CPTI 80mph+:%:CPTI80mph
+61:61:CPTI 110mph+:%:CPTI110mph
+
+
+You will have to restart ingestGrib for the changes to take place:
+
+ sudo service edex_camel restart ingestGrib
+
+Now you can try [re-ingesting the grib2 file](#grib2-products).
+
+---
+
+## Troubleshooting Grib Ingest
+
+* Make sure the latitude and longitude entries in your coverage specification file match those of your ingested raw grib file. There is a tolerance of +/- 0.1 degree to keep in mind when defining your coverage area.
+
+* If some of the information is unknown, using a grib utility application such as *wgrib* and *wgrib2* can be useful in determining the information that must be added to correctly process a new grib file.
+
+* If you are experiencing `Segmentation fault` errors when running wgrib2, it may be best to install the latest version using the following command:
+
+ yum install wgrib2
+ And then you may either need to change where `wgrib2` points to, or use `/bin/wgrib2` to run the recently downloaded version.