Hi @asadamjad​ is this warming related to one particular shapefile? Is it possible the particular file is corrupt?

I see that the files are zipped, how is your reader set up, can you share the parameters?

This how i setup my Paramater

HI @asadamjad 

I have the same problem, and I’m suspecting that it’s to do with the shapefile having zero attributes (other than FID and Shape). Would that be the same for you: did your shapefile have any attributes?

I created my shapefile by drawing  polygon in ArcGIS and then converting it from Graphics to Features.

Hey, @arnold_bijlsma.

Thank you for asking on this forum. For your question to have the best visibility, we recommend posting a question to the Community.

Thanks!

This is not a “problem” as such, but a warning about the SHX Record Index file that coexists with the SHP and DBF files.

I would guess that whichever software/process was used to create the SHP file in the first place made a “dummy” zero byte SHX file.  This is because some downstream software must have an SHX file present in order to not throw an error since SHX is a “mandatory” file and is consumed by some GIS Desktop software programs.

FME is less picky.  It doesn’t need the SHX file to read the data since it isn’t using it like a desktop GIS software with a live layer/connection to the file to render in GIS, but rather does a one-off read, and can infer which geometry in each SHP file row  goes with with Attributes in the each DBF file row.

For example, if I give a sample SHP file I have a dummy 0 byte SHX file, then get the same warning

...Data.shp' contains a Record Index file that is not a sufficient length to be useful and will be ignored. Features can still be read but performance may be impacted

Data still gets read in by FME just fine, however.  So not a “problem” for FME, and not caused by FME, but rather likely caused by whatever authored the SHP in the first place.