File Overview

Follow

To access the API source code, visit https://neon.trxsystems.com/downloads, login, and select the download for Neon API. This zip file contains the API source code as well as a full sample application. The compiled sample application is available at the same page.

 

  • Android device software includes two APK files: the Navigation Engine Software (NEON Location Service APK) as well as a sample developer application that shows how to integrate with the NEON API.

    • NEON Location Service APK - The NeonLocationService.apk Android package includes the NEON Location Service and is the only APK necessary to integrate with the NEON API.
    • NEON API Sample APK - The NeonAPISample.apk Android package includes a sample application available for learning the API.
  • com.trx.neon.api.*
    • This folder contains the main interface to the NEON API. The Neon class provides static functions that simplify the process of integrating with the NEON API. The INeonLocationListener and INeonEventListener are two interfaces that can be implemented by any class that desires to be notified of location and/or event updates respectfully. The NeonConfig class provides the capability to configure a headless Android device without user interaction.
  • com.trx.neon.beta.*
    • This folder contains beta features that are newly released and not yet part of the standard NEON API. Items in this folder may change readily and are not expected to be fully stable.
  • com.trx.neon.binder.*
    • This folder contains all of the low level binding code that transforms data going to and from the NEON Location Service. Modifying any of the files in this folder (even at the level of changing field names) could very easily break compatibility with the NEON Location Service. Application developers should not need to make modifications to this folder.
  • com.trx.neon.model.*
    • This folder contains all data types necessary to interface with the NEON API. These data types cover three primary categories: Location, Constraint (altitude, floor, position), and Event (binding, calibration, connectivity, motion level, posture, session, structural feature, vehicle state).

       

 

Was this article helpful?
0 out of 0 found this helpful

Comments

Powered by Zendesk