Skip to content

Sources and attribution

Know what a destination page is grounded in.

Navly pages combine editorial route framing with linked sources. The source list is there so a traveler can continue checking the detail that matters to their own date, pace, and access needs.

Primary context

Place identity comes before a claim.

Destination and neighborhood pages use the place name, city relationship, and route anchors represented in Navly's destination dataset. This keeps a guide about the place a traveler actually selected rather than a generic city keyword.

When a page includes an external source, it is shown with the page so the reader can follow it. We do not imply that a source covers every venue or every date.

Official checks

Use the source that owns the changing detail.

Venue hours, admission rules, ferry and transit service, events, and local access are time-sensitive. The relevant official venue, tourism, transport, or map source is the right place to confirm them before a trip.

Navly's iPhone experience can connect place research and map context to a trip. It does not replace the source that publishes a changing rule or schedule.

  • Official venue or attraction pages for hours, access, and admission details.
  • Official city, tourism, ferry, or transit pages for service and visitor guidance.
  • Map and place data for identity and geographic context, not invented ratings or availability.

What we leave out

No unsupported numbers in the name of authority.

We do not publish made-up ratings, walk scores, crowd counts, place totals, tour totals, prices, or accuracy guarantees. A page can be useful without pretending to measure what it has not measured.

If a fact cannot be attributed to a source or verified in the product surface, it is not used as a public claim.

Questions

Tell us when a source or detail needs attention.

If a linked source is outdated, a place is misidentified, or a route description no longer reflects the area, send the page URL, the specific statement, and the source that supports the correction to hi@navly.tr.