You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the title states, the Open Trail specification entails the addition of a named trail aggregate table or identifier.
RLIS Trails represents an 'atomic' dataset with a unique identifier for each trail segment. At this time we don't maintain a separate id for a collection of segments.
Included in this repository is an example entity relationship diagram (ERD) that might be used to match the Open Trail Specification standard.
The text was updated successfully, but these errors were encountered:
After looking and thinking about it for a while, I can say that the best path forward is to definitely
create unique IDs for the agencies, trail segments and trails that will be maintained over time on the
RLIS side. That is the best way to allow updates to happen that will for the long term association of
the OpenTrails data with other pieces of information, like notifications, photos, events and other
things.
As the title states, the Open Trail specification entails the addition of a named trail aggregate table or identifier.
RLIS Trails represents an 'atomic' dataset with a unique identifier for each trail segment. At this time we don't maintain a separate id for a collection of segments.
Included in this repository is an example entity relationship diagram (ERD) that might be used to match the Open Trail Specification standard.
The text was updated successfully, but these errors were encountered: