Clueride Location Details

This is the data that is captured for a Location:


  • Id (surrogate key)
  • Name
  • Description
  • Featured Image (as URL)
  • Google Place (if it is such a thing)
  • Location Type ID
  • Location Type Name (make it easier on humans)
  • NodeId (non-nullable) indication where to show on the map

There are also relationships with other objects:

  • List of LocationTag (may be empty)
  • Tag to Score map (for ranking all locations possessing the tag)
  • LocationGroup (may be null)
  • List of Puzzles (one required to be considerd an Attraction)
  • Establishment (if any, may be a Google Place as well)
  • List of Image URLs
  • Location Types are grouped into Categories

Derived Attribute

  • On-network
  • Readiness (Completeness / Draft)
  • Various Scores for Strength Factors


Each Location progresses via meeting requirements as well as increasing its ranking. The table below shows the Levels of Location, the requirements to be met before the location can progress to the level, and factors which permit ranking the location.

Levels for Location

Level Usage Level Name Requirement Ranking Factors Map Icon Color
Utility Node Lat/Lon so it can be part of geometry Ease of Access (based on connecting routes) none
Open Issue Issue There is an open problem report against the location Problem Reports Red
Work-in-Progress Draft One or more attributes below; not yet adding up to Place Completeness Orange
Map-worthy Place Name; Type (allowing Icon); On network, Featured Image; Description - Green
Course-worthy Attraction Set of Puzzles Depth of Puzzles; Set of Courses Blue
Features Featured Destination Google Place Multiple, see list below Purple

Strength factors

  • Establishment documented for the location
  • Links to further info regarding place
  • Proximity to other locations with high scores
  • Rankings
  • Popularity (number of visits; visitors; views)
  • Future: Label Scores; ranking within categories


  • Locations will have a Node so they can be located on the map. That Node will be tied to Edges/Segments as part of the network. Not all Nodes will have a Location. For example, the lat/lng pair where three segments meet will require a Node, but it doesn't mean there is any reason to stop at that Node.
  • Locations may be part of a LocationGroup. Generally, if more than one Location could share the same bicycle parking, then those two locations are part of a LocationGroup, but those LocationGroups are formally defined by membership of a Location within that LocationGroup.
  • Each Attraction should have a set of puzzles for revealing the next clue (segment / Path). Those Paths are part of the Node's relationship according to a particular Course rather than the Attraction itself.
  • Visiting an Attraction may confer specific badges
  • A location has a profile which helps score it relative to other locations of a similar type or with a particular tag.
  • A location may be associated with an establishment with hours of operation. The establishment would have further features and/or restrictions. (Google Place can help with this.)
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License