EpochField 5.2.19 Release

What’s New in EpochField 5.2.19

We’re pleased to announce the release of EpochField 5.2.19. The following highlights new enhancements and other items addressed.

New Features

• HTTP-Based GPS Data Source (Windows Only): Added support for using an HTTP-based GPS location service as the source of real-time positioning on Windows devices. This allows integration with a locally running GPS service that supplies device location via configurable HTTP endpoints.

Mobile

HTTP-Based GPS Data Source (Windows Only)

EpochField Mobile now supports retrieving real-time GPS location data from a locally hosted HTTP service on Windows devices. This option allows the application to work with advanced GPS setups that use a background service to collect and provide location data through a RESTful API.

This enhancement is ideal for environments where direct access to the COM port is not possible or reliable, and where Windows Location Services are insufficient. It also supports secure setups using self-signed certificates.

Key Capabilities:

• Periodically polls a configured local URI to retrieve current location data.
• Supports integration with services running on localhost (e.g., Current Location Endpoint).
• Converts the retrieved JSON response into a usable coordinate format for the app.
• Gracefully handles transient errors and shows a toast notification only after repeated failures.
• Works with services that supply latitude and longitude in EPSG:4326 or other CRS.
• Windows-only implementation; other platforms will raise an error if configured.

Configuration – Enable HTTP-Based GPS Source

<GPSSettings>
    <UseGPSDevice>5</UseGPSDevice>

Then add the HttpLocationServiceSettings section: 

<HttpLocationServiceSettings>

    <!-- Required: URI of the local HTTP GPS service -->

    <GetCurrentLocationUri>https://localhost:33112/api/location/current</GetCurrentLocationUri>

    <!-- Optional: Friendly name for error messaging -->

    <ServiceName>Secure Mobile Locate service</ServiceName>

    <!-- Optional: Polling frequency in milliseconds -->

    <PollingIntervalMilliseconds>1000</PollingIntervalMilliseconds>

    <!-- Optional: Max number of consecutive failures before showing toast -->

    <MaxConsecutiveErrors>10</MaxConsecutiveErrors>

    <!-- Optional: EPSG code of the returned coordinates -->

    <LocationResponseCrsWkid>4326</LocationResponseCrsWkid>

</HttpLocationServiceSettings>

</GPSSettings>

Error Handling Logic:

• Up to MaxConsecutiveErrors failed requests are tolerated before displaying a message.
• When errors occur, the previous known location is used temporarily.
• If the maximum error count is exceeded, a toast message appears:
  “[ServiceName] is currently unavailable”
• The error count resets upon receiving valid location data.

Failure conditions include:

• HTTP service not running (connection refused)
• Timeout (service takes >10 seconds to respond)
• HTTP response is not 2XX
• Invalid or malformed response body

This update allows greater flexibility and reliability when operating in environments that require a custom or centralized GPS data source on Windows devices.

Bug Fixes