Solved

Clipping ECW Files

  • 26 January 2016
  • 3 replies
  • 18 views
dfresh
Badge

Vendor sent lots of data ~11.2 GB of ECW files (8 files),

I have a shape file for clipping the ECW, and I have been unsuccessful, i have done lots of research to determine if this is even possible, as clipping an ECW will always still have the "Black" and white areas that are part of the image seen below,

I have converted to other formats (png, jp2, geotiff) and attempted to clip in FME and ESRi, but still no progress (esri crashes, and FME wont clip areas I need clipped),

My fme process consists of and this file is pretty standard for basic clips, unfortunately I can't provide the ECW file due to restrictions, but any suggestions would be helpful, as I have searched for all the previous ones,

Thanks,

Doug

icon

Best answer by jdh 26 January 2016, 23:29

View original

3 replies

jdh
Rank
Badge +22

Your workspace seems to have a lot of unnecessary transformers.

 

 

You've explicitly set the Coordinate system of both the ECW and Shp file on their respective readers, but you also have 3 reprojectors to the same coordinate system in the workflow.

 

 

If the source info is not in UTM83-10 then you need to remove the setting on the readers, if it is, then the reprojectors are useless. The 3rd is entirely unneccesary regardless, especially since you explicitly set the projection on the writer as well.

 

 

You don't need the RasterSelecto to select all the bands, since you've done nothing upstream to change it from the default.

 

 

Is there a NoDataValue (ex 255) on the original ecw? If so you probably want to deal with that before the RasterExpressionEvaluator.

 

 

A RasterBandNoDataSetter followed immediately by the NoDataRemover does nothing. Are you sure you don't want the NoDateRemover after the mosaicker?

 

 

The main issue is probably with your clipper. Since you tiled your mosaic, it's likely that most of the tiles are entirely inside the clipper, whereas you only have a connection to the ClippedInside port. Note the clipper is Version 5 whereas the latest version is 10, and the ports have changed between versions.

 

 

The counter/tester combo also seems entirely unnecessary.

 

 

G
Badge +3

Apart from unnescesay reprojecting and rasterbandselections etc. i would not mosaick the tiles. (takes time and increases subsequent clipping procestime.)

Use a RasterextentCoercer and filter these with the clipper feature. Then Use clipper only on those that pass the filter.

The extents coercer is pretty fast. I just did 138 tiles in 20.5 sec on a quadcore 16Gb mem.

J
Badge +2

You're going to always have the black bits around the edge with ECWs in FME because v2 doesn't support transparency. FME doesn't write/read v3, but you can work around it if you have software that will.

Reply


Community Stats

28,723
Posts
109,510
Replies
36,559
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.