Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open Trail specification requires heavier back end to maintain constant ids for named trails #1

Open
sainsb opened this issue Aug 28, 2014 · 1 comment

Comments

@sainsb
Copy link
Owner

sainsb commented Aug 28, 2014

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.

@sainsb
Copy link
Owner Author

sainsb commented Oct 24, 2014

From Jereme M. @ trailheadLabs:

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant