esri / nmea-for-geoevent

ArcGIS GeoEvent Server sample NMEA connector for receiving raw data in the NMEA format.

nmea-for-geoevent

ArcGIS GeoEvent Server sample NMEA input connector for receiving raw data in the NMEA format.

Features

• NMEA Inbound Adapter

Instructions

Building the source code:

1. Make sure Maven and ArcGIS GeoEvent Server SDK are installed on your machine.
2. Run 'mvn install -Dcontact.address=[YourContactEmailAddress]'

Installing the built jar files:

1. Copy the *.jar files under the 'target' sub-folder(s) into the [ArcGIS-GeoEvent-Server-Install-Directory]/deploy folder.

Requirements

• ArcGIS GeoEvent Server.
• ArcGIS GeoEvent Server SDK.
• Java JDK 1.8 or greater.
• Maven.

Resources

• Download the connector's tutorial from the ArcGIS GeoEvent Extension Gallery
• ArcGIS GeoEvent Server Resources
• ArcGIS Blog
• twitter@esri

Issues

Find a bug or want to request a new feature? Please let us know by submitting an issue.

Contributing

Esri welcomes contributions from anyone and everyone. Please see our guidelines for contributing.

Licensing

Copyright 2013 Esri

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

A copy of the license is available in the repository's license.txt file.

nmea-for-geoevent's Issues

NMEA validation appears to have a bias for 'North' and 'East' coordinates

This issue was originally reported by Samuel Richmond June 2014. Refer to his post on the product forum here.

Validation code in the NMEAGPRMCMessageTranslator.java file appears to check that coordinate values are in the 'North' and 'East' quadrant of the globe - devices which report coordinates as 'South' and/or 'West' cause the adapter to reject the sentence as invalid.

NMEA Connectors disappear from GeoEvent 10.5 when server restarts

@mpEsri I have 10.5 ArcGIS Server / GeoEvent Extension on a single windows 2012 Server vm federated with an ArcGIS Base deployment on another machine.

At first the connector worked, then the server restarted, and my input could not find the NMEA adapter ("Adapter Not Available"). I tried to reload the NMEA 10.4.X connector to the Site>Components>Adapters>Add Local Adapter. There was a message saying that it was successfully added.

I moved over to Site > GeoEvent > Connectors>Inputs and saw that there was an input but it contained a lot of Java string information rather than human readable labels (ie. ${com.esri.geoevent.adapter.nmea-adapter.CONNECTOR_LABEL}.... etc). Inside this connector in the edit dialogue it contained that type of JAVA string information in each of the inputs. The NMEA option in the "adapter" parameter did not appear. I deleted this input and tried to upload .jar file again.

The third time I tried to upload the .jar file to the local adapter, GeoEvent did not recognize anything was uploaded in the ..Connectors>Inputs.

In each of these uploads, the "deploy" folder on the server had the "nmea-adapter-10.4.0.jar" file in the folder.

I tried uploading the "nmea-adapter-10.3.0.jar" and a similar experience happens. It works the first time, and then continues to work.

NMEA adapter fails to translate GPGLL and GPRMC messages

See forum post http://forums.arcgis.com/threads/103085-NMEA-Adapter
for further details.

NMEA frames when navigation satellite system receiver talker identify is set to multiple system

After an attempt to use the connector, we find that GeoEvent is potentially not able, in its current form, with this connector, to listen NMEA frames when navigation satellite system receiver talker identify is set to multiple system e.g. $GNSS

We are able to listen the terminal in event TEXT UDP input, we get;

$GNRMC,161603.50,A,4620.62629,N,07232.60380,W,1.326,,090822,14.68,W,A,V*75

The same frame cannot be listened to by the NMEA connector.

When we modify this frame and send it to the system by geoevent simulator;

$GPRMC,161603.50,A,4620.62629,N,07232.60380,W,1.326,,090822,14.68,W,A,V*75

We can listen information using the connector.

Any idea where the code/system interacts with the Talker identifier?