Data quality checks before upgrading to V6.0: Difference between revisions

From IMSMA Wiki
Jump to navigation Jump to search
← Older editNewer edit →
No edit summary
No edit summary
Line 11: Line 11:


===MGRS coordinates===__NOEDITSECTION__
===MGRS coordinates===__NOEDITSECTION__
In V5.xxx it was possible to enter MGRS with wrong format. The first query checks for coordinates written with lower-case letters e.g. 4qfj12345678 and the second query checks for blanks.
In V5.xxx it was possible to enter MGRS with wrong format. The first query checks for coordinates written with lower-case letters e.g. 4qfj12345678 and the second query checks for blanks e.g. 4 QFJ 1234 5678.


===Coordinates display rules===__NOEDITSECTION__
===Coordinates display rules===__NOEDITSECTION__
In IMSMA NG there are 3 rules on how to handle and display coordinates, based on how they were entered;
* MGRS,
* Distance/Bearing
* 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 issue only affects the edit of Auxiliary data coordinates and Data Entry Forms in the Workbench.




Revision as of 16:57, 6 February 2014

Invalid / space coordinates

How To

{{#if:Space coordinates |

|}}{{#if:MGRS coordinates |

|}}{{#if:Coordinate display rules |

|}}{{#if:|

  • {{{4}}}|}}{{#if:|
  • {{{5}}}|}}{{#if:|
  • {{{6}}}|}}{{#if:|
  • {{{7}}}|}}{{#if:|
  • {{{8}}}|}}{{#if:|
  • {{{9}}}|}}{{#if:|
  • {{{10}}}|}}{{#if:|
  • {{{11}}}|}}{{#if:|
  • {{{12}}}|}}{{#if:|
  • {{{13}}}|}}{{#if:|
  • {{{14}}}|}}{{#if:|
  • {{{15}}}|}}{{#if:|
  • {{{16}}}|}}{{#if:|
  • {{{17}}}|}}{{#if:|
  • {{{18}}}|}}{{#if:|
  • {{{19}}}|}}{{#if:|
  • {{{20}}}|}}{{#if:|
  • {{{21}}}|}}{{#if:|
  • {{{22}}}|}}{{#if:|
  • {{{23}}}|}}{{#if:|
  • {{{24}}}|}}{{#if:|
  • {{{25}}}|}}{{#if:|
  • {{{26}}}|}}{{#if:|
  • {{{27}}}|}}{{#if:|
  • {{{28}}}|}}{{#if:|
  • {{{29}}}|}}{{#if:|
  • {{{30}}}|}}{{#if:|
  • {{{31}}}|}}{{#if:|
  • {{{32}}}|}}{{#if:|
  • {{{33}}}|}}{{#if:|
  • {{{34}}}|}}{{#if:|
  • {{{35}}}|}}{{#if:|
  • {{{36}}}|}}{{#if:|
  • {{{37}}}|}}{{#if:|
  • {{{38}}}|}}{{#if:|
  • {{{39}}}|}}{{#if:|
  • {{{40}}}|}}{{#if:|
  • {{{41}}}|}}{{#if:|
  • {{{42}}}|}}{{#if:|
  • {{{43}}}|}}{{#if:|
  • {{{44}}}|}}{{#if:|
  • {{{45}}}|}}{{#if:|
  • {{{46}}}|}}{{#if:|
  • {{{47}}}|}}{{#if:|
  • {{{48}}}|}}{{#if:|
  • {{{49}}}|}}{{#if:|
  • {{{50}}}|}}

It was not possible to upgrade to V5.08.04 if there are invalid coordinates in the database. Please run this SQL query anyhow because importing may overrun application rules. If you get any rows here, you have more SQL queries that will identify which object has the invalid coordinates in “Invalid_coordinates_ver2.doc” on PI.

MGRS coordinates

In V5.xxx it was possible to enter MGRS with wrong format. The first query checks for coordinates written with lower-case letters e.g. 4qfj12345678 and the second query checks for blanks e.g. 4 QFJ 1234 5678.

Coordinates display rules

In IMSMA NG there are 3 rules on how to handle and display coordinates, based on how they were entered;

  • MGRS,
  • Distance/Bearing
  • 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 issue only affects the edit of Auxiliary data coordinates and Data Entry Forms in the Workbench.


Length of Point ID

Retrieved from "http://mwiki.gichd.org/IM/index.php?title=Data_quality_checks_before_upgrading_to_V6.0&oldid=13351"