Changes from previous structure
This section is intended for software developers, power users, and other advanced users familiar with the pre-TeRaSys 2025 structure who wish to understand the differences between the previous and current structures, which apply starting from BR IFIC 3042 (published on 18 March 2025).
The following key changes have been implemented:
- Merge GE06 allotments into FMTV
- Move the column
target - Geographic coordinates
- Move FXM geographic coordinates
Merge GE06 allotments into FMTV
The table ge06_allot_terra and related tables were merged into fmtv_terra and related tables.
The column is_allot is added to the table fmtv_terra to differentiate assignments from GE06 allotments.
| Deleted tables | Data moved to | Added columns |
|---|---|---|
| ge06_allot_terra | fmtv_terra | is_allot, allot_name and typ_ref_netwk |
| ge06_allot_coord | fmtv_coord | |
| ge06_allot_plan_rmks | fmtv_ge06_plan_rmks | |
| ge06_allot_pub_hist | fmtv_pub_hist | |
| ge06_allot_rmks | fmtv_rmks | |
| ge06_allot_status | fmtv_status | |
| ge06_allot_target | fmtv_target |
The table ge06_allot_sub_area_xref is renamed to fmtv_ge06_sub_area_xref to comply with the prefix fmtv.
Move the column target
The column target contains the terrakey of the target assignment/allotment where the intent is SUPPRESS and/or MODIFY.
In the old structure, this column was in the terra tables:
- fmtv_terra
- fxm_terra
- lfmf_terra
It has been moved, respectively, to the target tables:
- fmtv_target
- fxm_target
- lfmf_target
The value of the column intent in terra tables, which is SUPPRESS and/or MODIFY, is copied to the column action in the target tables.
Geographic coordinates
The geographic coordinates columns in the tables lfmf_terra, fmtv_terra, ge06_sub_area_pt, and fxm_geo_pt have been simplified. The specific modifications made to these columns are outlined in the table below:
| Old columns | New columns | New column type | Value in the new column |
|---|---|---|---|
| long_dec | long_dec (preserved) | float | Longitude in decimal ° |
| lat_dec | lat_dec (preserved) | float | Latitude in decimal ° |
| long_deg, long_min, long_sec, long_ew | longitude_dms | float | DD * 10000 + MM * 100 + SS |
| lat_deg, lat_min, lat_sec, lat_ns | latitude_dms | float | DD * 10000 + MM * 100 + SS |
| seconds_in_use | string | TRUE or FALSE | |
| long_rdn | |||
| lat_rdn |
The columns longitude_dms, latitude_dms and seconds_in_use are migrated from the old structure using the following SQL statements:
longitude_dms = ( long_deg * 10000 + long_min * 100 + ISNULL(long_sec, 0) )
* CASE long_ew WHEN 'E' THEN 1 ELSE -1 END,
latitude_dms = ( lat_deg * 10000 + lat_min * 100 + ISNULL(lat_sec, 0) )
* CASE lat_ns WHEN 'N' THEN 1 ELSE -1 END,
seconds_in_use = CASE WHEN long_sec IS NULL THEN 'FALSE' ELSE 'TRUE' END
FXM geographic coordinates
In the previous database structure, the fxm_geo_pt table stored the geographic coordinates along with the site altitude (site_alt) for entries where the geo_type was designated as POINT, CIRCLE or MULTIPOINT.
This structure has been revised in the new database schema. The fxm_geo_pt table now exclusively contains the geographic coordinates for entries where the geo_type is MULTIPOINT.
For entries where the geo_type is POINT or CIRCLE, both the geographic coordinates and the site altitude (site_alt) have been relocated to the fxm_geo table.