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

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

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

    לאתר החברה

    נתונים ודיווח

    ערים, רחובות וכתובות

    מקורות גאוגרפיים ובחירת כתובת ארצית בנתוני המוצר.

    בעמוד הזה

    The product map and reference directory select localities by government code. The map has dependent city, street and charging-address dropdowns. Changing city clears street/address; changing street clears address. The list and map share the same filter, including provider preferences, fast-charge reports and favorites. An empty selected-provider result offers a separate all-network view when matching sites exist; it never changes the workspace's saved provider choices.

    Reference snapshot · 2026-11-08#

    • 1,316 locality records from the Population and Immigration Authority, including the source's classification entries. Codes are preserved as strings.
    • All 63,662 rows from the official street list, modified 2026-11-01. Streets are scoped by locality code; names are not globally unique.
    • 152,221 rows from the official streets and synonyms list. Only aliases pointing to an existing official city/street identity participate in matching. Example: Ashdod שוהם resolves to official שהם, code 741.
    • 1,808 polygon features from the public municipal/local committee boundary layer, hosted by the Society for the Protection of Nature in Israel / Deshe Institute. This is a secondary geographical source, not a live government geocoder. All pages were retrieved in stable OBJECTID order and checked against the exact count.
    • The current 2,261 Ministry of Transport sites are assigned by point-in-polygon: 1,982 have an unambiguous locality; 279 remain unassigned. All 2,261 remain on the national map. No nearest-city guesses or substring city matches are used. There are 40 sites inside Ashdod and six in Hazor-Ashdod; a street called Rosh Pina in Ashdod does not reclassify the station as the locality Rosh Pina.
    • 872 sites match an official street name or alias using complete name tokens and the locality identity. Source surname/first-name ordering is accepted. The longest unambiguous identity wins; remaining streets are unassigned. The UI tells users how many city sites are missing a street assignment and keeps them accessible through all streets and reported station addresses.

    These are reference-data counts, not claims of complete station coverage or live availability. The street dataset does not contain every Israeli building/house number. The address dropdown contains all nonempty reported station addresses within the selected city/street, grouping identical normalized addresses. Source contradictions and missing addresses are not silently corrected. English-only or otherwise unmatched addresses can still be selected under all streets. The existing charging integration/readiness restrictions remain in effect.

    Serving and update contract#

    lib/reference/data/geography.json and streets.json are compact, versioned public reference snapshots, bundled only on the server. Client components import types/filter functions, never the full national street registry. /api/reference/geography returns the complete locality list; /api/reference/streets?city=<code> returns every street for that city with explicit total and validation. No per-keystroke government call, first-page truncation, geolocation permission or third-party geocoder key is required.

    /api/reference/map still reads the complete paginated public Supabase station snapshot and enriches it on the server. An assignment is accepted only when the current station's source ID and exact coordinates match the prepared snapshot. A changed address invalidates its street assignment while preserving a coordinate-verified city. Moved/new stations stay visible nationally until enrichment is refreshed. /api/reference/locations?city=<code> uses the same enrichment and returns paginated exact-city results in the directory. No schema, RLS, tenant records, supplier preferences, vehicle records or charging capability changes are required for this release.

    Street/locality responses are cacheable public reference data. Map snapshots retain the existing five-minute CDN freshness window. The map client versions its request URL so a new UI cannot reuse a pre-geography browser-cached response. A selected city with no result uses its known polygon bounds to orient the map; no synthetic stations are added. Errors keep the city results available and provide retry for streets.

    Refresh runbook#

    1. Install scripts/reference-requirements.txt in a virtual environment.
    2. Refresh and review the base source with scripts/import-israel-reference.py --input <reference-work> --fetch, using the existing public-reference import procedure.
    3. Run python scripts/prepare-israel-geography.py --work <geography-work> --reference <reference-work>/normalized.json --fetch.
    4. The preparation refuses truncated pages, duplicate scoped identities, changing source versions, unknown city references, and unexpected coverage shrinkage. Inspect the coverage report, source dates, SHA-256 checksums and city/street diffs. Review boundary provenance when replacing its publisher/version. Generated snapshots are written only after validation; the script does not deploy or write to Supabase.
    5. Run unit tests, lint, production build and geography browser acceptance; deploy the reviewed code and snapshots together. Refresh enrichment whenever base station locations/addresses change. This is a reproducible release-time refresh, not an unattended scheduled synchronization.

    Acceptance#

    Unit tests cover complete scoped reference identities, geographical Ashdod/Hazor distinction, official aliases, moved/new source IDs, unknown locations and exact address matching. Browser checks exercise the full city/street dropdowns, Ashdod map/list results, street and address selection, dependent reset, empty-result recovery, street-source failure/retry, directory consistency and 320px layouts. Existing map, favorites, themes and registration-only entry points are regression checked. Production acceptance and deployment identity are recorded after rollout.

    Production acceptance · 2026-11-08#

    • Runtime commit: d0a30dfb0dd497988a6925ceba980b79fc33d488.
    • Vercel deployment: [operational-id-redacted], READY; product.linknodesenergy.com assigned without alias errors.
    • 156 unit tests, ESLint, TypeScript and the production build passed. Nine distinct local browser scenarios passed, including the theme regression; focused checks were repeated after the cache-version and narrow-directory fixes.
    • Five production browser scenarios passed: full dropdown/city/street/address flow, source failure/retry, 320px directory/map flow, map-source failure, and the registration-only vehicle entry point. Production API assertions use browser fetch to share the browser network/proxy context.
    • Independent HTTPS requests with certificate verification confirmed 1,316 locality records, 63,662 national street records, 715 Ashdod streets, 2,261 national sites and 40 Ashdod sites. The official street alias and Hazor-Ashdod distinction were checked against the deployed responses.
    • No tenant data, vehicle records, provider selections or payment settings were written by the verification. Test-only network failures were intercepted in the test browser.
    • Live product: https://product.linknodesenergy.com/.