NoPublic, bureaucrat, administrator
6,632
edits
Changes
no edit summary
* X and Y.
When data has been migrated or imported it is possible that the column userinputformat in the table ''geopoint'', which controls coordinate display, has not been set correctly. When the display field is set correctly the columns are high-lighted with yellow. If the user tries to edit a row which does not have one of the rules set, the coordinates will not be populated in the Point window. This In 5.08.04 this issue only affects the edit of Auxiliary data coordinates and Data Entry Forms in the Workbench [[Coordinate display rules|(query)]].
{| class="wikitable"
|}
{{Note |
* The real values of Distance and Bearing are stored in other columns then the ones above and what is stored in ''userenteredcoord'' is in the same format as the '''first''' point* In V6.0 ''userenteredcoord'' is replaced by three different columns (user_entered_x, user_entered_y and user_entered_mgrs) without the locale part}}
Later in the upgrade process the calculated area/length of polygons/polylines need to be recalculated and with the upgrade script the field ''userenteredcoord'' will be split up in three different columns:* user_entered_x, * user_entered_y;* user_entered_mgrs. The three fields ''coordrefsys'', ''coordformat'' and ''userinputformat'' '''mustMUST''' be in a valid combination AND they '''mustMUST''' be consistent with the value of ''userenteredcoord'' e.g.
* ''coordrefsys'' = WGS 84
* ''coordformat'' = Degrees:Minutes:Seconds
in combination with
* ''userenteredcoord'' = 17.2345|25.5678|en|UK
is '''not''' a valid combination[[Coordinate display rules|(query)]]. {{ Warning | If invalid combinations are not corrected , the area/length recalculation and the database upgrade will '''not''' work [[Coordinate display rules|(query)]].}}
===Length of Point ID===__NOEDITSECTION__