Currently there is only a single attribute (isAccessPoint) used to describe whether or not a route can be accessed via a particular location, and it is only defined for RoutePoints. The semantics of this are unclear, and inadequate to many common use-cases - for example, urban environments, where routes can in principle be joined almost anywhere along their length.
The proposal is then to:
Rename isAccessPoint to isRecommendedAccessPoint, and restrict its use to indicating that this is considered the best, simplest, or most catered-for point at which to join a route or route segment. This attribute would be available on RoutePoint.
Define an additional attribute, isJoinable, indicating that a route may, as a matter of physical possibility, be joined at some given location. This attribute would be available both on RoutePoints and on RouteSegments.
Currently there is only a single attribute (
isAccessPoint
) used to describe whether or not a route can be accessed via a particular location, and it is only defined forRoutePoint
s. The semantics of this are unclear, and inadequate to many common use-cases - for example, urban environments, where routes can in principle be joined almost anywhere along their length.The proposal is then to:
isAccessPoint
toisRecommendedAccessPoint
, and restrict its use to indicating that this is considered the best, simplest, or most catered-for point at which to join a route or route segment. This attribute would be available onRoutePoint
.isJoinable
, indicating that a route may, as a matter of physical possibility, be joined at some given location. This attribute would be available both onRoutePoint
s and onRouteSegment
s.