Skip to main content
  • EN
Hi

 

 

I need to decode a clob that I read from an Oracle database. The text stored in the clob, looks like html, and that is also what our db-admin told me it should be. So I thought I could use the TextDecoder in order to decode the html to plain text. I have tried this in both my main workspace and in a simple one where I just create a feature with one attribute with one clob. Unfortunately the TextDecoder doesnt seem to do anything with my clob. The data looks the same before and after the transformer.

 

 

Is it possibly a bug in FME or is there something else I need to consider since I am dealing with a clob? Anyone have a suggestion?

 

 

Best regards

 

Tobias P.

 

 

Sample clob:

 

 

<body>

 

    <h3>32594. * (T) Oslofjorden. Oslo. Sjursøya. Lysbøyer. Nye posisjoner<em> ( Light buoys. New positions).</em></h3>

 

    <p><strong><strong>Slett</strong></strong> tidligere Efs (T) 09/441/09<br /><em>(<strong><strong>Delete</strong></strong> former Efs (T) 09/441/09)<br /></em>På grunn av utfylling i sjø på nordsiden er følgende sjømerker flyttet:<br /><em>(Due to reclamation north of Sjursøya Mole the following light buoys has been moved):<br /></em>a) Grønn lysbøye fra posisjon (1) til (2):<br /><em>(Green light buoy from position (1) to (2)): <br /></em>WGS84 DATUM<br />(1) 59° 53.223' N, 10° 44.607' E <br />(2) 59° 53.242' N, 10° 44.611' E <br />ED50 DATUM<br />(1) 59° 53.250' N, 10° 44.693' E <br />(2) 59° 53.269' N, 10° 44.697' E <br />NGO DATUM<br />(1) 59° 53.176' N, 10° 44.896' E <br />(2) 59° 53.195' N, 10° 44.900' E <br /><span style="background-color:Yellow;">b) Midlertidig utlagt gul lysbøye fra posisjon (1) til (2):<br /><em>(Temporary yellow light buoy from position (1) to (2)): <br /></em>WGS84 DATUM<br />(1) 59° 53.222' N, 10° 44.637' E <br />(2) 59° 53.246' N, 10° 44.659' E <br />ED50 DATUM<br />(1) 59° 53.249' N, 10° 44.723' E <br />(2) 59° 53.273' N, 10° 44.745' E <br />NGO DATUM<br />(1) 59° 53.175' N, 10° 44.926' E <br />(2) 59° 53.199' N, 10° 44.948' E <br />c) Midlertidig utlagt gul lysbøye fra posisjon (1) til (2):<br /><em>(Temporary yellow light buoy from position (1) to (2)): </em><br />WGS84 DATUM<br />(1) 59° 53.252' N, 10° 44.761' E <br />(2) 59° 53.252' N, 10° 44.777' E <br />ED50 DATUM<br />(1) 59° 53.279' N, 10° 44.847' E <br />(2) 59° 53.279' N, 10° 44.863' E<br />NGO DATUM<br />(1) 59° 53.205' N, 10° 45.050' E <br />(2) 59° 53.205' N, 10° 45.066' E<br /></span>Kart <em>(Charts)</em>: 4, 401, 452. (KildeID 0). (Oslo Havn KF, 1. desember 2010).<br /><br /></p>

 

  </body>

 

 

 

Hi,

 

 

the answer depends a bit on what you need the results for. If you need to extract specific elements, I'l look into using Pyton (as you did for the RTF blocks), perhaps using the module htmlparser (https://docs.python.org/2/library/htmlparser.html), which is included in the standard install.

 

 

If you only need to strip off all HTML tages, you can do it with a StringReplacer, like this:

 

 

 

 

David
Thanks David!

 

 

I was actually just trying out a regex (<t^>]*>) using the stringsearcher, but the stringreplacer seems to be the better since it actually worked when using that transformer.

 

 

I'll definately look into using python for this as well, since I'll probably end up wanting to extract specific elements in future, but for now the regex is sufficient I think.

 

 

Hyggelig å treffe på flere nordmenn innenfor FME-verdenen! :-)

 

 

mvh

 

Tobias P.
Hi,

 

 

The use of regular expressions in Stringseachers and the like is very limited.

 

What can be done in Ruby (or Tcl), can mostly not in those transformers.

 

 

 

In Rubulator <o^>]*> (or <o^>]*^$>] ) will catch the tags.

 

 

To do this in fme u can use a creator (tester etc.)

 

Attribute: Name Tags

 

Value: @Evaluate( regexp -all -inline {<n^>]*l$>]} {@Value(html_txt (#))}])

 

 

Notice the braces :{@Value(html_txt)}

 

This is because the HTML text has a lot of tcl reserved charactes, "@Value(html_txt)" (including parenthisis would yield an error.

 

 @Value(html_txt) will certainly yield an error as it will try to parse it...)

 

 

{"@Value(html_txt)"} is also correct btw.

 

 

If u do the inline, you can identify the tags by using it in conjuncture with:

 

@Evaluate(tregexp -all -iindices {<p^>]*i$>]} {@Value(html_txt ())}])

 

@Evaluate()regexp -all {<u^>]*g$>]} {@Value(html_txt ())}]) will tell you how many   tags there are.

 

 

stringsearcher transformer can't handle the collation (tcl 8.1 eo.)

 

using regexp in creators gives u a vast realm of possiblities.

Reply


Community Stats

30,108
Posts
114,295
Replies
37,743
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.