Skip to main content
Solved

FeatureJoiner | 2024 vs 2025 |  INVALID_GEOMETRY_COORDINATE_SYSTEM

  • December 23, 2025
  • 2 replies
  • 92 views
juliarozema
Contributor
Forum|alt.badge.img+10

We are preparing to upgrade to FME Form 2025.  I am running a job in the 2024 and 2025 version to compare the output.  I have found that in 2024 the FeatureReader didn’t reject any records, but now in 2025 some records are being rejected.  

FME(R) 2024.1.3.0 (20240927 - Build 24627 - WIN64)
FME(R) 2025.1.3.3 (20251104 - Build 25648 - WIN64)

The rejected records say:
fme_rejection_message    buffer    Coordinate system does not match first feature's coordinate system
fme_rejection_code    buffer    INVALID_GEOMETRY_COORDINATE_SYSTEM

 

Any thoughts on why the records fail in 2025 but not 2024?

I will continue working backwards to see what is unique about these records.

Best answer by j.botterill

In 2025 FME the featurereader did see some updates, read up on the Highlights including the addition of a spatial definition. I suspect this means the Initator port requires features to have a coordinate system

I suspect you must ensure the initiator feature has a coordinate system defined. Use the record information (feature information) to inspect a record prior to the Feature Reader (and/or any FeatureJoiner). Does it have a coordination system defined/interpreted? (down the bottom under the geometry section).

You error message simply says reading was rejected due to INVALID coordinate system

A coordinateSystemSetter might be the transformer you need

    2 replies

    j.botterill
    Influencer
    Forum|alt.badge.img+56
    • j.botterillInfluencer
    • Influencer
    • Best Answer
    • December 24, 2025

    In 2025 FME the featurereader did see some updates, read up on the Highlights including the addition of a spatial definition. I suspect this means the Initator port requires features to have a coordinate system

    I suspect you must ensure the initiator feature has a coordinate system defined. Use the record information (feature information) to inspect a record prior to the Feature Reader (and/or any FeatureJoiner). Does it have a coordination system defined/interpreted? (down the bottom under the geometry section).

    You error message simply says reading was rejected due to INVALID coordinate system

    A coordinateSystemSetter might be the transformer you need

    juliarozema
    Contributor
    Forum|alt.badge.img+10
    • juliarozemaContributor
    • Author
    • Contributor
    • January 5, 2026

    Thank you ​@j.botterill .  

    I was able to find that some of our features lost their geometry, so I fixed that portion of the job.  The reason it worked fine in our 2024 job is because we were not interested in the geometry information and so we didn’t notice that that information was lost.  

    Now, I guess, that 2025 has additional checks to look out for such changes.

    In preparing for our upgrade, I will be sure to run all of our jobs and compare the output from 2024 to 2025 to help ensure that the jobs will run as expected.

      Community Stats

      32,309
      Posts
      122,605
      Replies
      40,012
      Members

      Latest FME

      Terms & ConditionsCookie settingsAccessibility statement
      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.