Last-mile delivery breaks down
Drivers end up calling repeatedly, returns rise, and actual delivery time drifts far beyond what operations teams planned for.
LandMarX presents Bawsaltak
Bawsaltak gives every building in Syria a precise digital address.
LandMarX’s National Digital Address System combines standardized addressing, intelligent search, API verification, and 3D urban modeling so services can rely on one trusted spatial identity.
- Damascus is the live pilot geography
- National address + short code + spatial reference
- Search by address, place, code, and coordinates
- 3D model for dense informal urban neighborhoods
Why this matters
When addresses are descriptive, every service becomes slower and more expensive.
Non-standard addressing is not just a user inconvenience. It increases operating cost, slows response times, and makes reliable digital services harder to build.
Emergency response loses critical time
Directions like “behind the mosque” or “next to the old bakery” are not enough when an ambulance or fire crew needs an exact building target.
Digital public services stay incomplete
Verification, service routing, and field operations all need a shared address layer that people and systems can use consistently.
Who it serves
One address layer for the Syrian market, from everyday navigation to operational infrastructure.
Residents
Share a clear, compact address instead of repeating a different description every time.
Commerce and Delivery
Reduce calls, failed drop-offs, and address ambiguity inside operational systems.
Mobility Services
Improve pickup and drop-off precision and reduce rider-driver confusion.
Emergency Services
Reach the right building faster when seconds matter.
Public Institutions
Use one addressing reference for service delivery, verification, and planning.
What the platform includes
A full addressing system, from national reference data to daily search and map use.
Standardized address structure
A national address model that works for people, systems, and downstream operational use.
Search and API verification paths
Address, code, coordinate, and place search are handled as explicit UI and API verification flows instead of a single mixed search box.
Governed places and services layer
POIs and service locations live inside a review-and-publication model rather than an unmanaged overlay.
Modern spatial visualization
A 2D/3D urban interface helps users identify real buildings, understand dense informal neighborhoods, and supports a broader digital-twin direction over time.
Product experience
Turn vague directions into a verifiable address workflow.
See the partner-facing path: find the right building quickly, read its structured data, then reuse the same reference in delivery, field service, and API workflows.
01
Address search on the map
A clear search path for addresses, codes, and places inside the same map experience.
02
Readable building card
The code, structured address, coordinates, and local context become shareable and verifiable data.
03
3D urban neighborhood model
Explorable building massing helps users understand dense and informal urban fabric visually.
04
Drone and reality layers
Drone imagery exposes street-level detail that generic map layers often miss.
/api/viewer/
Product proof
Bawsaltak is already explorable as a live 2D/3D map experience.
The current interface shows how users search by address, code, coordinates, or places, then move directly to the right building inside one 2D/3D map workflow.
- Structured building, street, and area search
- A dedicated POI mode that does not pollute address search
- Direct switching between 2D map context and 3D urban massing
- Building information cards that keep the address code and location readable
API verification and integration path
This is not only a demo page. It is designed to become an embeddable verification layer.
Delivery companies, field-service teams, and public institutions can use the same address reference through both the interface and API services, with a clear separation between working data and published data.
Address verification example
GET /api/address/verify?code=SY-01-00-00123-045678
{
"status": "verified",
"city": "Damascus",
"precision": "building"
}Address verification
Confirm that a code points to a published building or unit in the live reference.
Operational integration
Use structured addresses in delivery and field-service systems instead of storing unverified text directions.
Publication governance
Data is exposed to end users only after explicit review and publication.
Why generic maps are not enough
The real gap is not map visibility. It is the lack of an operational address standard.
Descriptive directions
Easy to start with, but hard to standardize, verify, or operate at scale.
Generic map layers
Helpful for navigation, but not necessarily designed to function as national address infrastructure.
Bawsaltak by LandMarX
Human-readable, system-verifiable, and structured for real service delivery, integration, and operational trust.
From Damascus outward
Start in Damascus, including dense informal neighborhoods, then extend a system built to scale.
Damascus → national rollout
Start, verify, then scale the national reference
Damascus is the current pilot for operating method, validation, product proof, and dense-neighborhood 3D modeling.
The target is not a local numbering tool but a national addressing model.
The same reference layer is meant to serve residents, businesses, and institutions together.
Why the platform is credible
The platform does not just collect data. It governs what becomes live.
Clear contracts between ingestion, review, publication, and live usage.
Separation between working data and the published corpus shown to end users.
Integration paths that fit delivery systems, field operations, and public-sector services.
Common questions
What it takes to make this part of everyday service delivery
Is this just another map product?
No. The map matters, but the core value is a standardized address layer that can be used operationally and programmatically.
Is it only for government use?
No. Government is one major beneficiary, but delivery, mobility, commerce, and everyday users all benefit from the same shared address system.
Is Damascus the final scope?
No. Damascus is the current pilot and proof geography, not the long-term ceiling.
What role does AI play here?
AI helps users explore the map and reach answers faster, but it does not replace the address reference or the published data layer.
Can this connect to external systems?
Yes. That is a core part of the platform value: address retrieval, verification, and map workflows that other services can consume.
Start with a pilot or integration discussion
Talk to LandMarX if your service depends on reliable addresses.
The current Bawsaltak product is suitable for showing the operating model, testing key flows, and discussing pilots, institutional partnerships, or commercial integrations in Syria.