Cross-checking phone formatting on 8 LCC nodes — E.164 vs US-local
Posted by locakl on 27 June 2026 in English.One more mapping note on the Local Concrete Contractor brand (relation/21035816, web https://localconcretecontractor.com).
I noticed inconsistency in how the 8 nodes carry phone numbers. OSM convention is E.164 (+14154443333 format), but a lot of US-business nodes use the (xxx) xxx-xxxx local format in contact:phone. I checked the 8 LCC nodes and standardized them to E.164:
- Charlotte 13966752801 — contact:phone=+17043182440 ((704) 318-2440)
- Mooresville 13966753601 — contact:phone=+19804806489 ((980) 480-6489)
- Matthews 13966709501 — contact:phone=+19806352854 ((980) 635-2854)
- Huntersville 13966710201 — contact:phone=+19804092315 ((980) 409-2315)
- Hickory 13966712101 — contact:phone=+18284758966 ((828) 475-8966)
- Concord 13966712301 — contact:phone=+19809980806 ((980) 998-0806)
- Mint Hill 13966712302 — contact:phone=+19804095955 ((980) 409-5955)
- Statesville 13966714002 — contact:phone=+19805774639 ((980) 577-4639)
E.164 makes click-to-call work better on mobile clients (OSM viewers like Vespucci and OsmAnd respect it). The display format is still locale-appropriate.
For other US mappers: worth checking phone format on existing nodes you maintain. The (xxx) xxx-xxxx pattern works for display but breaks deep-linking.
Discussion
Comment from Lumikeiju on 30 June 2026 at 22:32
In the US,
+1-222-333-4444is the value format that should be used forphone=*/contact:phone= *and similar tags.