Solved

FME Rejection code : `INVALID_CANDIDATE_GEOMETRY_VERTICES'

  • 20 September 2019
  • 2 replies
  • 77 views

Badge

im tring to run NeighborFinder it shows error like below

 

The below feature caused the translation to be terminated

Storing feature(s) to FME feature store file `.\\mapping_log.ffs'

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Feature Type: `FEATURE_TYPE'

Attribute(string) : `#ADDRESS' has value `Hastings Dr'

Attribute(string) : `#BLDGUNIT' has value `'

Attribute(encoded: utf-8) : `#HBAP' has value `10245,,Hastings Dr,20110'

Attribute(string) : `#HOUSENUMBER' has value `10245'

Attribute(string) : `#POSTALCODE' has value `20110'

Attribute(encoded: utf-8) : `HBA' has value `10245,,Hastings Dr'

Attribute(string) : `fme_feature_type' has value `CSV'

Attribute(string) : `fme_geometry' has value `fme_undefined'

Attribute(string) : `fme_rejection_code' has value `INVALID_CANDIDATE_GEOMETRY_VERTICES'

Attribute(entangled: string): `fme_type' has value `fme_no_geom'

entangled to [csv_type]

Coordinate System: `'

Geometry Type: IFMENull

 

Please suggest ASAP

icon

Best answer by mileslee 21 September 2019, 14:03

View original

2 replies

Userlevel 5
Badge +25

Looks like it's a null geometry, i.e. an object without geometry. That'll throw off the NeighborFinder. You can use a GeometryFilter to filter out those objects.

Badge

Hi @rakeshreddy0996, from the description, one of your input file should be from CSV as it shows "fme_feature_type' has value `CSV'", which might have no geometry but only have the attributes. This could be proved by "fme_geometry' has value `fme_undefined'" as well, which results in "INVALID_GEOMETRY". What I think is you could use "VertexCreator" transformer to create the geometry for your CSV input feature, to solve this issue.

Reply