analyzing points on routes

Sorry, the "Input is Ordered by" didn't work as expected in my quick test.

 

?Now, I cannot provide any idea to resolve the memory issue...

I found that the parameter works as I intended if you sort points and lines together like this.

 

Hi Takashi,

the "YES" in INput is ordered by group should be right.....one step forward...but now i have a new problem....

it seems the memory problem is now anyhow solved....but FME writes one feature after PoinONLIneOverlayer and MeasureExtractor in the Geodatabase but the it stops and log the error NULL pointer check failed...

what is this? what can I Do?

Thanks and greetz

Franco

Could you please paste the error message as-is?

2> NeighborFinder(ProximityFactory): Processing 15.62% complete

 

NULL pointer check failed. File: geodbfeatureclass.cpp Line #: 1010

 

A fatal error has occurred. Check the logfile above for details

 

A fatal error has occurred. Check the logfile above for details

 

|ERROR |

 

... Last line repeated 2 times ...

 

Output_From_6::TransporterReceiver(TransporterFactory): A fatal error has occurred. Check the logfile above for details

 

A fatal error has occurred. Check the logfile above for details

 

A fatal error has occurred. Check the logfile above for details

 

f_32(TransformFact): A fatal error has occurred. Check the logfile above for details

 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 

Feature output statistics for `FFS' writer using keyword `W_1':

 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 

Features Written

 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 

==============================================================================

 

Total Features Written 0

 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 

GeodatabaseRelationshipFeaturesPipeline::GeodatabaseRelationshipFeatures(SortFactory): Sorted 0 feature(s)

 

Transaction #1 rolled back. Rerun translation specifying transaction #0 for the keyword 'TRANSACTION'

 

Closing the Geodatabase writer

 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 

Feature output statistics for `GEODATABASE_FILE' writer using keyword `GEODATABASE_FILE_2':

 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 

Features Written

 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 

locate_pts_5_3 1

 

==============================================================================

 

Total Features Written 1

 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 

A fatal error has occurred. Check the logfile above for details

 

FME Session Duration: 38 minutes 55.3 seconds. (CPU: 2077.2s user, 221.7s system)

 

END - ProcessID: 138332, peak process memory usage: 3341676 kB, current process memory usage: 407360 kB

 

 

 

 

 

A fatal error has occurred. Check the logfile above for details

 

Program Terminating

 

 

 

Translation FAILED.

 

 

 

screenshot

 

 

Looks like the error occurred during parallel processing in the NeighborFinder.

 

I'm not sure what the exact reason for the error is, but the parallel processing might be concerning to that.

 

How about setting "No Parallelism"?

With " No Parallelism" in the NeighborFinder nothing changed.....

sad to hear that...

 

sorry, I don't have any idea to resolve the error.