RTE in occurrence interpretation

17324
Reporter: trobertson
Type: Bug
Summary: RTE in occurrence interpretation
Priority: Critical
Status: Open
Created: 2015-02-26 19:31:19.095
Updated: 2015-03-02 16:27:11.475
        
Description: Logs showing:
{code}
java.lang.ArrayIndexOutOfBoundsException: 1
    at org.gbif.common.parsers.geospatial.CoordinateParseUtils.parseVerbatimCoordinates(CoordinateParseUtils.java:126) ~[occurrence-cli.jar:0.26]
    at org.gbif.occurrence.processor.interpreting.util.CoordinateInterpreter.interpretCoordinate(CoordinateInterpreter.java:179) ~[occurrence-cli.jar:0.26]
    at org.gbif.occurrence.processor.interpreting.LocationInterpreter.interpretCoordinates(LocationInterpreter.java:100) ~[occurrence-cli.jar:0.26]
    at org.gbif.occurrence.processor.interpreting.LocationInterpreter.interpretLocation(LocationInterpreter.java:32) ~[occurrence-cli.jar:0.26]
    at org.gbif.occurrence.processor.interpreting.VerbatimOccurrenceInterpreter.interpret(VerbatimOccurrenceInterpreter.java:78) ~[occurrence-cli.jar:0.26]
    at org.gbif.occurrence.processor.InterpretedProcessor.buildInterpreted(InterpretedProcessor.java:111) [occurrence-cli.jar:0.26]
    at org.gbif.occurrence.processor.messaging.VerbatimPersistedListener.handleMessage(VerbatimPersistedListener.java:43) [occurrence-cli.jar:0.26]
    at org.gbif.occurrence.processor.messaging.VerbatimPersistedListener.handleMessage(VerbatimPersistedListener.java:23) [occurrence-cli.jar:0.26]
    at org.gbif.common.messaging.MessageConsumer.handleCallback(MessageConsumer.java:101) [occurrence-cli.jar:0.26]
    at org.gbif.common.messaging.MessageConsumer.handleDelivery(MessageConsumer.java:65) [occurrence-cli.jar:0.26]
{code}

CC [~fmendez] [~omeyn] [~mdoering]]]>
    

Author: mdoering@gbif.org
Created: 2015-02-26 20:21:32.141
Updated: 2015-02-26 20:21:32.141
        
sounds like a bug in the parsers. I came across a NPE one earlier this week too which is not yet released:
https://github.com/gbif/parsers/commit/8d01354f7d8ae62ab4a8b62f5cf682eda536f4eb