HALCON Extension Package Programmer's Manual

4.2. REGION DATA (’HRLREGION’) 51ØÝÔ ×ØÖÙØ ßÐÓØ Ö » ÖÐ Ñ ÔÖØ »ÐÓØ Ñ » ÑÒÖÝ Ñ ÔÖØ »Ð ÀÓÑÔÐÜÈÜÐØÝÔ ×ØÖÙØ ßÁÆ̾ Ô » ÔÜÐ »ÁÆ̽ ÒÙÑØ× » ÒÙÑÖ Ó Ù× Ø× »Ð ÀÁÒؾÈÜÐØÝÔ ×ØÖÙØ ßÁÆ̽ ÖÓÛ » ݹÖØÓÒ »ÁÆ̽ ÓÐ » ܹÖØÓÒ »Ð ÀÈÜÐØÝÔ ×ØÖÙØ ßÀÌ » ¼ºº¾ »ÁÆÌ ÒÙÑÐÙØ » ÐÒØ Ó ÓÐÓÖ ØÐ »ÀÌ Ö¾℄ÀÌ ÖÒ¾℄ÀÌ ÐÙ¾℄Ð ÀÄÙØÈÜÐFigure 4.3: Data types for ÀÑ.Please see section 3.2.2 for routines to allocate image data within ÀÑ.4.2 Region Data (ÀÖÐÖÓÒ)In HALCON region data is represented by a special variant of the runlength encoding – a chordencoding: For every line (chord) of a region its row index (“y coordinate”,“line number”) andthe column index (“x coordinate”) of its start and end point is stored. Both the start point andthe end point belong to the region.Chord data must fulfill the following conditions:¯ a chord is limited to one row¯ chords may not overlap¯ chords are sorted in ascending orderIf a region is read from the HALCON data base, its representation fulfills all the conditionsabove. When writing a region, condition 2 and 3 need not to be sufficed in all cases, as theExtension Package Interface automatically modifies the data (at cost of computation time).Fig. 4.4 shows the type declaration for chords. All chords are stored in an array of the type ÀÖÙÒ,where ÒÙÑ is the current and ÒÙÑ ÑÜ the maximum allowed number of chords (depending onthe size of the region specified at its creation, see also sections 3.2). The flag × ÓÑÔÐ allows anHALCON 6.0