דילוג לתוכן
מרכז התיעוד
לאתר LinkNodes Energy
LinkNodesENERGYתיעוד

טוענים את החיפוש…

    חיפוש גם בתוך המאמרים ↑ ↓ לניווט Esc לסגירה

    לאתר החברה

    מוצר ויכולות

    מיקום במכשיר

    בקשת מיקום בחזית, הרשאה, מיקום עדכני והתנהגות כשאין גישה.

    בעמוד הזה

    The existing production product could request a single browser position and sort national station records by straight-line distance. It used a cached fix up to 60 seconds old and did not request high accuracy or show the reported uncertainty. This was verified on the live domain with an emulated Ashdod position before changing the implementation.

    Current behavior#

    • Opening the normal driver map requests foreground location automatically after station/provider data is ready. A click on “קרוב אליי” or the map location control can retry or recenter. One browser watchPosition uses enableHighAccuracy: true, maximumAge: 0, timeout: 20000. Browser/OS permission is still required; high accuracy is a request, not a GPS guarantee. Favorites and explicit station deep links retain their existing view without an automatic location request.
    • The default map waits for the first fresh location before showing station markers, then centers near the user. Provider and fast-charging filters preserve this nearby view. Permission failure leaves manual city/address selection and the national overview available. Selecting a city or station while location is pending takes precedence over the later GPS fix.
    • A separate 25-second deadline bounds a silent request. Permission denial, unavailable coordinates, timeout, and unsupported/insecure contexts have actionable messages and manual locality/address fallback.
    • A temporary signal-loss/timeout event after a valid fix hides the previous position and allows the same authorized watch up to 25 seconds to recover. A new valid fix restores ranking and recenters the position; permission denial always stops immediately. This case was reproduced with native Chromium geolocation during the production check.
    • Every fix is checked for finite coordinates, coordinate bounds, nonnegative finite accuracy, and a current timestamp. A fix older than one minute or more than five seconds in the future is rejected. Out-of-order updates are ignored. A foreground freshness check retires a stationary stale fix after one minute (checked every five seconds).
    • A successful explicit recenter clears only city/street/address filters and the old selected station. The automatic first fix does not discard a city or station the user selected while waiting. Provider selection, provider scope, fast-charging and favorites filters remain intact. If permission fails, city selection is retained.
    • Valid station coordinates are ranked using great-circle distance. Stations without valid coordinates remain in the list after ranked records and cannot be recommended as nearest.
    • The nearest card states that it is nearest among the current filtered results. This is straight-line distance, not a road route, ETA, guaranteed availability or permission to access a private site. The source remains the national reference catalog; live operator availability is not introduced.
    • Reported accuracy and update time are visible. Approximate fixes (>100 m) have an explanation; fixes worse than 1 km do not claim an exact nearest station. Distance text accounts for uncertainty instead of implying metre-level proximity from a coarse fix.
    • The user's active vehicle is shown at the current device position using its existing approved model image, contained without cropping, alongside the geodesic uncertainty circle. A generic car icon is used only when no matching vehicle/image is available. Station markers remain unchanged. Theme changes retain the vehicle marker. New position updates do not repeatedly recenter the map.
    • A unique vehicle assigned to the current driver, or the account's single active vehicle, is selected automatically. With several possible vehicles, the existing toolbar offers an explicit vehicle selector. Its saved ID is scoped by account, tenant and user, and is revalidated against current active vehicles before display. No image is generated or guessed from an unrelated vehicle.

    Lifetime and privacy#

    Location begins when the normal map becomes usable, subject to browser consent. Data/provider error screens release tracking and never start a hidden watch without location controls. Hiding the tab or leaving the page releases the watch, removes the current fix and pauses proximity ranking. Resuming is explicit. Permission revocation, stale data, stop and component unmount release the watch and ignore late callbacks. A stopped or failed request does not silently restart. One active watch is maintained per mounted discovery scope.

    Coordinates are held only in component memory. They are not saved to local/session storage, tenant records or product analytics. Reference-station requests do not include the user's coordinates. The map-tile provider receives tile requests for the viewport, which can imply its approximate area; external navigation offers Waze or Google Maps with the station destination. The product privacy text reflects these behaviors.

    The HTTPS product receives Permissions-Policy: geolocation=(self), camera=(self), microphone=(). This allows first-party location/camera usage and does not bypass browser consent. No paid geolocation vendor, reverse geocoding service or backend tracking table is required for nearest-station discovery.

    Verification#

    Unit coverage checks stale/future fixes, invalid coordinates, missing-coordinate ranking, antipodal distance, accuracy geometry at the dateline/poles, uncertainty-aware distance labels and tenant-scoped vehicle selection. Browser cases use explicitly simulated device fixes for automatic startup, high-accuracy options, moving between cities, provider and city-filter behavior, denial, timeout, coarse positioning, revoked permissions, hidden tabs, stale/silent devices, data failures, delayed fixes after explicit city selection, dark mode and the approved Smart image at the reported map position. Browser test execution still requires a supported Chromium environment; local test definitions alone are not device acceptance evidence.

    A real phone's GPS accuracy depends on hardware, OS/browser permissions and surroundings. Browser emulation verifies the application flow, not physical GPS performance or provider station-coordinate accuracy. This feature does not implement background employee tracking, fleet telematics, live charging or route-distance calculations.