Meeting minutes
RobSmith: Autonomous vehicle usage demo video
[10 min] Future work of WebVMT and update on GeoPose (Rob Smith)
RobSmith: 2 csv files: 1 contains pos & orientation of vehicle; other contains lidar detections
RobSmith: Issue: how to turn detections into coords to plot on map
RobSmith: orange line is vehicle trajectory; dots represent signposts and pullouts
RobSmith: Puzzle to track cyclist, turn trajectory into moving feature object
RobSmith: Eliminate static; classify anything we see in radius as static
RobSmith: if in 2 consec frames, not moving
RobSmith: predictor algorithm yields no identity linking things together
RobSmith: as video moves, detections / static are eliminated
RobSmith: Blue trajectory is detected moving feature (cyclist)
RobSmith: Success; tracking algorithm isn't perfect, has gaps but pretty good
RobSmith: Tracked for 300m over a minute. Can calculate avg speed, etc
RobSmith: A car was also detected. Even short detections are useful
RobSmith: All tracks done with WebVMT.
RobSmith: Idea to release as community tool. Requires funding.
RobSmith: Multiple cameras, in order to associate observations. Either concurrently or
RobSmith: also distributed in time and space. e.g. dist along a rod, can get additional info can get info from gaps between cameras
RobSmith: Anonymization of reg plates on vehicles necessary.
RobSmith: Use case: traffic cameras that become stuck, showing same thing all the time, an AI could determin something wrong
RobSmith: Final suggestion: collision mitigation. Proximity detection for e.g. parking, or pre-emptive collision mitigation.
RobSmith: If combine camera deployments, traffic camera and vehicle cameras, could improve pre-emptive system
RobSmith: Testbed 18; if any interest in funding distribution as community tool, please get in touch
ClaraB: does the cyclist know he's being tracked? or is it an OS person?
RobSmith: All of this does have privacy implications
RobSmith: Other standard: geopose. Position and orientation in a common format.
RobSmith: Explainer videos on OGC youtube channel
RobSmith: GeoPose handles streams, particularly interesting for videos.
RobSmith: Vote at OGC for GeoPose expires early April
<brinkwoman> This group is working on automotive and transportaton related stuff: https://
RobSmith: Also working on Geoalignment idea. C Perey has mobilised geopose team to get involved.
brinkwoman: Is GeoPose a web standard?
<RobSmith> Explainer videos: https://
Best Practices update from Timo
Timo: BP github repository: https://
<RobSmith> Testbed-17 Moving Features - Autonomous Vehicle Analysis: https://
Timo: improvements to coverages (clarifications)
Timo: addition of section on GeoPose and POI SWG activities
Timo: DCAT2 changes updates
Timo: 2 pull requests. One about FAIR principles. Now there's a mapping of which BP relates to which FAIR principle.
Timo: Discussion of whether FAIR should extend to include "Q" for example (quality).
Timo: If you define quality as fitness for purpose: if you have a use case in mind you need to have an idea of if the data is useful for that
Timo: Q is now included and relates to one BP in particular
Timo: FAIR-V verfication: does this have anything to do with FAIR? Conclusion is maybe not.
Timo: the PR needs some reviews, welcome from others.
PeterParslow: that's a good summary of the PR
Timo: PR about gaps in the current BP document
brinkwoman: inaudible
brinkwoman: OGC API Features, geosparql. Would be good to get a review from at least one other person. I will look at next week.
Timo: Issues discovered, some examples no longer accessible. Solution may be to self-host. Others possibly outdated, need revision.
Timo: This is a call for anyone interested to get involved.
Timo: section about coverages has been updated. Might be interesting to have examples of different coverage types.
Timo: outside our community, "coverage" is not well understood. Needs illustrations, especially in this section of document.
Timo: Search engine indexing. RDF-a, other approaches. Interesting to figure out what is a best practice, include in doc.
Timo: Dynamic CRS would be a welcome contribution to BP doc
Timo: TODO and future work.
Timo: Emerging technology, e.g. MapML. PeterR is assigned to that.
Timo: other tech might be interesting. If you are an expert in: POI, GeoPose, other, please PR
Timo: RobSmith will write a section on ethics of location sharing
Timo: GeoFences (volunteers needed).
Timo: OGC API Tiles section volunteers needed
Timo: TB 17 implementation reports should be scanned, volunteers needed
Timo: Timeline: release summer 2022
Timo: we have tackled 25% of anticipated changes.
Timo: can provide updates in SDW meetings.
Timo: Biweekly conference calls, next meeting 10 March 3pm CET
Timo: If you have something you want to discuss, please add to agenda via PR in GitHub
Timo: contact Timo or Clara via email or on GitHub
brinkwoman: thank you for update and thanks for this work
brinkwoman: if you would like to volunteer or discuss, please step forward!
[10 min] Solid - what does it mean for us? (discussion)
brinkwoman: https://
brinkwoman: I followed up with the people who made the presentation, but haven't heard back.
brinkwoman: The project was very interesting. People can host their own data pod, for free.
brinkwoman: I was wondering if this group should do something in relation to (data pods).
brinkwoman: Jeremy and I discussed, thought it might be early days for this technology.
Timo: Here at university, we have a student who has experimented with spatial data and solid.
Timo: coming from linked data background, solid pods aren't implementing sparql. Not sure if that belongs in BP, maybe in emerging practices.
brinkwoman: If you could in a future meeting, review what the student has done, that would be of interest!
Timo: ok, I can summarize in a future meeting.
brinkwoman: People from Flanders, were using linked data event streams. Sound more lightweight method to interact with linked data.
Timo: Concern, if you don't have a sparql service, need to download and execute js sparql locally. Sparql 1.1 compatibility missing.
Timo: idea of Solid is to not overload server. Can understand removing sparql from solid server. may want to limit amount of data you download, so
Timo: how do you handle, no solution for now.
Timo: geodata you want in query, you process on client side, not sure if that is suitable at scale.
TPAC Sep 2022? Any plans
brinkwoman: TPAC meeting. Hybrid meeting September 12-16 in Vancouver. Remote or in-person attendance possible.
brinkwoman: We should determine as a group if we'll have a meeting there. Jeremy and I hope that all our work will be mostly done by then.
brinkwoman: <informal poll of potential in person attendees at TPAC>
brinkwoman: Results: good potential for hybrid meeting
<Bert> /drive.verborgh.org/publications/buyle_egose_2019.pdf/[10 min] Solid - what does it mean for us? (discussion)