{"id":6969,"date":"2018-11-12T06:36:02","date_gmt":"2018-11-12T05:36:02","guid":{"rendered":"http:\/\/www.sigterritoires.fr\/?p=6969"},"modified":"2023-04-28T14:58:49","modified_gmt":"2023-04-28T12:58:49","slug":"geometry-validation-tools-4-intergraph-geomedia","status":"publish","type":"post","link":"https:\/\/www.sigterritoires.fr\/index.php\/en\/geometry-validation-tools-4-intergraph-geomedia\/","title":{"rendered":"Geometry validation tools (4): Intergraph Geomedia"},"content":{"rendered":"\n

Wondering why discussing Intergraph Geomedia? It is true that in France\nit has an almost confidential diffusion. But it does not deserve this. Besides the\nfact that it has been the forerunner in many fields (the Esri geodatabase is\nonly the Intergraph Warehouse updated for Esri, but 10 years later), regarding\nour interest, it is the proof that a lot more can be done when we really want. Let’s\nsee how geometry validation works with Geomedia 2014.
\n <\/p>\n\n\n\n\n\n\n\n

The documentation<\/strong> <\/p>\n\n\n\n

In previous articles we have discussed the deficiency of documentation\nrelating the geometry checks. Here we have 34 pages with definitions and\nexamples. You can download here the part of the document   \u201cGeomedia Fusion Training Guide\u201d regarding\nthe geometry validation. <\/p>\n\n\n\n

A small example that will make you want to download the document: \u00ab\u00a0<\/em>Backspace: Applies to linear or\npolygon features when the geometry is doubled backward on itself.<\/em><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The line above is defined by a sequence of 10<\/em> nodes<\/em> \n(ABCDCDEFGH).<\/em> The<\/em> DCD sequence itself<\/em> \ndefined<\/em> as a backtrack.<\/em>
\nBacktracking is corrected by removing the<\/em> nodes<\/em> \nwhich constitute it.<\/em> In the example above<\/em> the second group of<\/em> nodes<\/em>\n C and D are removed.<\/em>
\nThe line is then defined by a series of 8<\/em> nodes<\/em> \n(ABCDEFGH).<\/em> This one is a simple example<\/em> simple of\nbacktracking …<\/em> \u00ab\u00a0<\/em> <\/p>\n\n\n\n

The Validate Geometry command from Geomedia<\/strong> \n\nThe command is located in the ribbon\ncorresponding to the Toolbox<\/em><\/strong> Menu\n\n\n\n<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

You will find three tabs: Entry<\/strong> , Anomalies<\/strong> , and Result<\/strong>\n. \n\nThe first tab is used to define the layer or\nlayers to be validated.   \n\n\n\n<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Therefore you can define all the layers you want to perform validation\nwithout having to go through one at a time. <\/p>\n\n\n\n

The Anomalies tab is used to indicate which anomalies to look for. They\nare grouped under three headings: <\/p>\n\n\n\n

  • Standard <\/li>
  • Specialized <\/li>
  • Z (height)<\/li><\/ul>\n\n\n\n
    \"\"<\/figure>\n\n\n\n

    \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nThe\nright window makes it possible to configure the action to perform if the\nanomaly is found:  \n\n\n\n<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    You can indicate, for each anomaly supported by the automatic\ncorrection, whether you want to apply it or not. The two commands, separated in\nthe other software, are associated. \n\nFinally, the last tab allows you to configure\nthe display of the results: \n\n\n\n<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    Placing anomalies in a queue will allow performing the manual corrections\nvery easily. <\/p>\n\n\n\n

    Placing the anomalies in a query allows you to have a layer with the entities\nwith anomalies, for example to see the made automatically corrections. <\/p>\n\n\n\n

    We will execute the command by selecting, only, all the standard\nanomalies and leaving the automatic correction disabled for all. \n\nThe result is as follows: \n\n\n\n<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    Unlike the previous examples, Geomedia detects 28 anomalies instead of\nthe 19 found in the previous examples. <\/p>\n\n\n\n

    In fact, it finds 19 entities with anomalies, but there are some that\ncontain more than one anomaly. If you look at the highlighted record you will\nnotice that the first of 5 records concern the same entity. <\/p>\n\n\n\n

    [In\nprevious cases, when an entity is marked as invalid, the search stops. Though\nnot the corrections. If we replay the test on the corrected entities, we see\nthat there are no anomalies left. The corrector deals with all the anomalies of\nthe same entity.] \n\nIn the left window you will find the details of\nthe anomalies. By clicking on a record you will, automatically, find the\nanomaly displayed on the left window. The usual editing commands allow you to\nmanually correct the desired anomalies. \n\n\n\n<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    If you edit an anomaly in the left window, it disappears from the right window.\n<\/p>\n\n\n\n

    The example of the screen capture above shows an anomaly with an inner\nring. As we have indicated in a previous example, this type of anomaly will be\ncorrected automatically by creating an outer ring and an inner ring. We, also,\nindicated that it was not necessarily the best solution. Obviously, here the\npoint that closes the water inlet should be separated, so as to form a creek\nand not a closed basin. <\/p>\n\n\n\n

    With Geomedia, it is easy to move the point and manually correct the\nanomaly, with the right solution. <\/p>\n\n\n\n

    Once we have finished with the manual corrections, we can re-execute the\ncommand, but by selecting the automatic corrections in the parameter window. In\nthis case, the anomalies do not appear anymore. <\/p>\n\n\n\n

    In addition to the Validate Geometry<\/em> command, Geomedia has\nanother command: VOID Surface Detection<\/em> that detects overlays or spaces\nbetween contiguous polygons. <\/p>\n\n\n\n

    The command simply asks for the layer   to validate and where to\nplace the detected surfaces. \n\nThe result is then: \n\n\n\n<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    Thus, we have discussed all the possibilities with Geomedia. When\nreading the different articles you will understand, we have a small preference\nfor this one, when it comes to validate the geometry of layers. We know what we\ndo, we see what we correct and everything remains at a level of difficulty\nquite within our reach … <\/p>\n\n\n\n

    But you will ask us, what\u2019s up with QGis? Well, that will be the topic\nof our next article. <\/p>\n","protected":false},"excerpt":{"rendered":"

    Wondering why discussing Intergraph Geomedia? It is true that in France it has an almost confidential diffusion. But it does not deserve this. Besides the fact that it has been the forerunner in many fields (the…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"give_campaign_id":0,"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"sfsi_plus_gutenberg_text_before_share":"","sfsi_plus_gutenberg_show_text_before_share":"","sfsi_plus_gutenberg_icon_type":"","sfsi_plus_gutenberg_icon_alignemt":"","sfsi_plus_gutenburg_max_per_row":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[1260],"tags":[],"class_list":["post-6969","post","type-post","status-publish","format-standard","hentry","category-non-classe-en"],"aioseo_notices":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p6XU0A-1Op","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/posts\/6969","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/comments?post=6969"}],"version-history":[{"count":0,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/posts\/6969\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/media?parent=6969"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/categories?post=6969"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sigterritoires.fr\/index.php\/wp-json\/wp\/v2\/tags?post=6969"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}