Evidence before recommendations
We use official tourism information, developer and operator publications, contractor statements and geographic datasets. A source is evidence for a specific claim: a masterplan shows an intention, an operator page shows what the operator publishes, and neither automatically confirms present access.
“Reviewed” means we read the source on the stated date. “Operator-published” means a business published it; “operator-confirmed” requires a direct dated check of the specific detail. No entry in this edition is operator-confirmed.
Original checklists are editorial planning guidance. They do not claim that a named supplier or service is available. We link material place and development facts to their source records.
Commercial independence
No sponsor is confirmed for this guide. The guide is not an official publication of a developer or tourism authority. There are no property lead forms, paid rankings or shared contact lists. Any future sponsorship will need a clear disclosure.
What the atlas actually shows
The field atlas keeps the source geometry of eight developer plan views and adds original guide annotations, selected feature traces and editorial analysis. Each edition has its own image-coordinate space, with no geographic registration or silent alignment between versions. Guide numbers identify reading points; repeated numbers refer to the same category reading, not official plots or precinct IDs. Programme components without reliable positions stay off the drawing.
Supplied document editions remain distinct. WhatsApp exports, contact details, voice notes, unit offers and sales availability are private research and are not published. The public guide uses selected generic plan imagery and original analysis; the source register identifies the relevant publication and pages.
Map points use GeoNames, individually linked OpenStreetMap records, and named project-map references published by developers, checked against satellite context. Developer pins remain published references rather than independently surveyed coordinates. A point may represent a cape, a city label or a representative position within a mapped destination. We record its method and source; it is not automatically an entrance. Ogami, June and Caesar use their explicitly named SODIC map components; Hacienda uses Palm Hills’ project register; Fouka Bay uses Tatweer’s project-linked directions reference.
The cape’s GeoNames coordinate is corroborated by the nearby OpenStreetMap Ras al Kanayis reference. These records locate the geographic feature; they do not define the wider region or the Modon development.
Every project boundary remains unknown in this edition. No ownership line or precise parcel is inferred from a brochure, road, area figure or satellite texture. A future approximate masterplan overlay must preserve publisher, date, control points and registration limits, and must be labelled as approximate plan coverage.
Satellite capture dates vary. The imagery is a geographic aid, not a current construction inspection. Roads and buildings visible in a tile do not establish public access. Our map does not provide turn-by-turn directions.
The atlas also provides original developer plans in a separate zoomable viewer, an interactive relationship diagram, a proportional chart of the October 2024 area allocation, and a dated announcement timeline. The plan viewer uses image coordinates only. Its guided views locate visible features within the original drawing; they are not geographic registration or confirmations of delivery. Straight-line comparisons use published reference points and cannot establish travel time.
3 October addition: regional arrival geography
The arrival atlas adds five existing airport references in a separate regional map. Land geometry comes from Natural Earth, version 5.1.1, at a scale of 1:10 million. This is a broad geographic view, not a detailed shoreline survey. The source polygons are cropped outside the visible map so the crop edges do not become a false coastline.
Named airport coordinates come from OurAirports, with airport identities checked against government and airline pages. Each point was inspected against satellite context. Points identify the broader airport area; they do not show passenger entrances or pickup gates. Comparisons measure straight-line distances between published points. They do not provide road routes or travel times. The planned Ras El Hekma airport and an unverified Wadi Yemm gate remain unpinned.
Made with Natural Earth, whose data is public domain. Named airport records are credited to OurAirports. The arrival page requests Esri satellite tiles only when you open satellite context.
The new everyday directory distinguishes official national numbers, operator-published enquiry contacts and seasonal closure notices. No entry becomes a directly confirmed local service. Travel-note fields are not submitted or saved automatically; readers choose whether to download their own text file.
Help improve the next edition
For this guide, send a correction through the chat where this guide was shared, or back to the person who shared it. Include the page, the disputed detail, a better source and the date checked. Do not send private contracts or personal documents.
Nothing is submitted by this button. You choose where to send the note.
Download a blank correction note
Send corrections back to the person who shared this guide, with the page, the detail and a dated source. Corrections will be assessed against evidence and logged with the next review date.
Maps, imagery & type
Satellite: Esri World Imagery and its contributors. Extent-dependent source attribution appears inside the map through Esri Leaflet, alongside a persistent Esri credit. Tiles load from the provider and are not bundled or altered.
Map and geographic references: © OpenStreetMap contributors, Open Database Licence. Cape reference from GeoNames, CC BY 4.0. Links to individual records appear in the atlas.
Original guide maps: source drawings are credited to their developers. Guide annotations, selected feature traces, comparisons and close readings are original editorial work by Ras El Hekma Guide. Each source edition retains its own provenance and stays separate from satellite imagery. They are not surveyed parcels, navigable route maps or construction inspections.
Supplied plan editions: Modon Wadi Yemm June 2026 toolkit and Palm Hills/Miran Hills July masterplan image. Selected plan pages are shown as intended development; no private offer pages or chats are reproduced.
Developer drawings: Hacienda Ras El Hekma: Miran Hills brochure, page 77, plan credited to OBMI. Modon city: Responsible Business Report 2024, page 30. Ogami: SODIC masterplan rendering. The Med: People & Places masterplan image. Original publisher links accompany every plan. All are intended-development visuals; no open republication licence was established. This independent review retains publisher credits and source records; no affiliation or endorsement is implied.
Coast photograph: “The north coast of Egypt” by Abdelrahman Abdelazeem, CC BY-SA 4.0. Uploader identifies Marsa Matruh; this is wider-coast context, not an exact Ras El Hekma photograph. The file is resized and displayed with a crop; the adapted image remains under the same licence.
Fonts: DM Sans and Cormorant Garamond, self-hosted under the SIL Open Font Licence. DM Sans licence · Cormorant licence.
A simple reading experience
We use Plausible to count visits to this guide. We do not send your form entries, buyer notes or calculator inputs to analytics. There is no signup, account or contact database. Map views request tiles and attribution from Esri or OpenStreetMap; those providers receive ordinary web-request data such as your IP address. External links open the original publisher’s website. Correction notes are copied or downloaded on your device and are not submitted to us.