Great to hear! And yes, your points are a bit different, but I figured I’d first help you with the first steps so you can gradually learn how things fit together
In RDF terms, the points on your route are blank nodes (i.e. they don’t have a URL), whereas the route itself is a named node (i.e. it has a URL: currently
http://example.org/myRoute, though it should’ve been
So we’ve been calling e.g.
getString() to get properties of the route, but how can we do the same for points on that route?
In Tripledoc, the library you’re using to access the data, you can access those points through
getLocalSubject() (to access one of them) and
getAllLocalSubjects() (to access multiple).
So in code, you could get access to the points using:
const points = route.getAllLocalSubjects('http://arquisoft.github.io/viadeSpec/point');
And then you can read values of a single point using the same methods you can use on the route, e.g.
const firstPointOrder = points.getInteger('http://arquisoft.github.io/viadeSpec/order');
A working code example can be found here: