OS4CSAPI
CSAPI @ OGC Builder Days 2026 Coordination Follow-up #39
Replies: 3 comments 1 reply
-
|
@nsnarayanam — thanks again for taking the time to look through the client-library work and flag issues. I wanted to move the detailed follow-up here so we do not turn the OGC Builder Days participant thread into a repo-specific implementation discussion. One important clarification: the Phase 7 branch you reviewed is no longer active. More broadly, for this particular client-library project, I’d like to keep direct code changes with me for now. The work is part of a specific contribution path back to the upstream There are also a lot of broader CSAPI areas where extra eyes would be useful during the sprint: documentation gaps, example requests, CSAPI Explorer feedback, server/client interoperability observations, conformance/test ideas, Part 3 Pub/Sub ideas, Part 5 binary encoding feedback, or issues in the official CSAPI standards repo. For standards development, the most important activity to the OGC CSAPI SWG is the Part3 Pub/Sub work that @tipatterson-dev is prototyping here opensensorhub/osh-addons#194, closely followed by the Part 5 binary encoding work here https://github.com/tipatterson-dev/SWECommonBinaryEncodings also being spearheaded by @tipatterson-dev. Personally, I am very interested in the emerging agent work you are doing with CSAPI, as well as this project https://github.com/nsnarayanam/anvikshana-nscic-prototype which appears to have CSAPI implementation in its roadmap. Please feel free to use the live servers I have up, along with 52 North's to assist your work during the event:
I look forward to working with you this week! Respectfully, |
Beta Was this translation helpful? Give feedback.
-
|
Dear @Sam-Bolling <https://github.com/Sam-Bolling>,
Good to hear from you, and thanks for the heads-up on the Phase 7 branch
saved me from going further down that path.
On the client library, fully understood. It's your contribution to land,
and the cleaner you keep it, the better the upstream PR will go. I'll stick
to review notes, issues, and test cases where I think they help, and stay
out of the code itself.
Where I'd like to spend the week is where you pointed — Travis's Part 3
Pub/Sub work in opensensorhub/osh-addons#194 and the Part 5 binary encoding
work. I'll get into both, test against the live servers you shared
(CSAPI-Go v2, OSH, the 52°North demo, and the pygeoapi deployment), and
open issues where I have something worth raising.
Also, thanks for the kind note about the agent work and the anvikshana
repo. That one is an early public sketch and the real CSAPI integration is
in our internal build. Happy to walk through it during the sprint if you're
curious.
See you in the threads this week.
Respectfully,
@nsnarayanam
…On Sun, May 10, 2026 at 8:54 PM Sam Bolling ***@***.***> wrote:
@nsnarayanam <https://github.com/nsnarayanam> — thanks again for taking
the time to look through the client-library work and flag issues. I wanted
to move the detailed follow-up here so we do not turn the OGC Builder Days
participant thread into a repo-specific implementation discussion.
One important clarification: the Phase 7 branch you reviewed is no longer
active. More broadly, for this particular client-library project, I’d like
to keep direct code changes with me for now. The work is part of a specific
contribution path back to the upstream camptocamp/ogc-client project, and
I need to manage the scope, branch history, tests, and final PR carefully.
That said, review notes, issues, questions, and suggested test cases are
genuinely helpful. They help me identify what needs to be checked, cleaned
up, or improved as I continue the implementation work.
There are also a lot of broader CSAPI areas where extra eyes would be
useful during the sprint: documentation gaps, example requests, CSAPI
Explorer feedback, server/client interoperability observations,
conformance/test ideas, Part 3 Pub/Sub ideas, Part 5 binary encoding
feedback, or issues in the official CSAPI standards repo. For standards
development, the most important activity to the OGC CSAPI SWG is the Part3
Pb/Sub work that @tipatterson-dev <https://github.com/tipatterson-dev> is
prototyping here opensensorhub/osh-addons#194
<opensensorhub/osh-addons#194>, closely followed
by the Part 5 binary encoding work here
https://github.com/tipatterson-dev/SWECommonBinaryEncodings also being
spearheaded by @tipatterson-dev <https://github.com/tipatterson-dev>.
Personally, I am very interested in the emerging agent work you are doing
with CSAPI, as well as this project
https://github.com/nsnarayanam/anvikshana-nscic-prototype which appears
to have CSAPI implementation in its roadmap.
Please feel free to use the live servers I have up, along with 52 North's
to assist your work during the event:
Live CSAPI server Implementation / purpose Endpoint
CSAPI-Go v2 Go + PostGIS server based on connected-systems-go; useful for
independent server/client interoperability testing.
https://129-80-248-53.sslip.io/csapi-go-v2
OSH (OS4CSAPI) OpenSensorHub instance hosted for OS4CSAPI testing; useful
for richer CSAPI Part 1 / Part 2 workflows.
https://129-80-248-53.sslip.io/sensorhub/api
52North CSA Demo Public 52°North Connected Systems demo endpoint; useful
as a public comparison target. https://csa.demo.52north.org
52North pygeoapi (Live) 52°North connected-systems-pygeoapi deployment on
Oracle Cloud; useful for testing the emerging pygeoapi-based implementation.
https://129-80-248-53.sslip.io/csapi-pygeoapi
I look forward to working with you this week!
*Respectfully*,
@Sam-Bolling <https://github.com/Sam-Bolling>
—
Reply to this email directly, view it on GitHub
<#39 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BKUGDBDO6V3TYPKESUKP7DL42CNMNAVCNFSM6AAAAACYYBXI7CVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMOBXGA2DQNQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Awesome, @nsnarayanam and thank you! I gave @tipatterson-dev (goes by Ian) a heads up that you expressed interest in reviewing his active work. For your awareness, I have localized my efforts to address the findings you shared with me as phase-9 of the typescript client library CSAPI code contribution. I have a first draft of my research on it here https://github.com/OS4CSAPI/ogc-client-CSAPI_2/blob/phase-9/docs/research/phase-9/01-discovery-layer-lesson-propagation.md, which has shaken out a preferred COA. My next steps are to experiment that COA thoroughly, here is my draft experimentation plan https://github.com/OS4CSAPI/ogc-client-CSAPI_2/blob/phase-9/docs/research/phase-9/02-live-testing-experiment-plan.md. Both documents will get iterated on before finalized and executed. I have a bit of prep work to do on the data publishing work and the webapp to prepare my testing environment before I begin which might actually take most of the next 3 days. Afterwards I will implement the fix in my working repo, port the clean update into my pr repo and update the PR for the upstream. The one work item I am tracking that I will want to discuss with the upstream maintainer is the parsers for SWE Common work, which I am triaging behind OS4CSAPI/ogc-client-CSAPI_2#187. Additionally, I was apprised of another CSAPI implementation based out of Europe and invited to review it and provide feedback. It is still internal and early prototype stages, so there won't be much visibility on that background activity this sprint. Lastly, I have two big visions beyond the scope of this event. Both my CSAPI Explorer App and my fork of OSHConnect-Python have just about completed their purposes. As soon as I finish up the rest there is to immediately learn from them, I intend to begin a new CSAPI Publisher App and a new CSAPI Explorer App to replace them, both of which would be more use-case and purpose driven than the exploratory nature of their predecessors. I will likely keep the legacy projects alive for some time for experimental use. Respectfully, |
Beta Was this translation helpful? Give feedback.
-
|
Dear @Sam-Bolling,
Thanks for the heads-up to @tipatterson-dev
<https://github.com/tipatterson-dev>(Ian), appreciated.
Glad the findings folded cleanly into Phase 9. I'll read through your
research draft and the experimentation plan today and follow along as they
iterate. If anything jumps out worth raising I'll do it as an issue or
comment in the right place rather than pile onto your inbox. The SWE Common
parsers question in #187 is the one I'm most curious about; will hold off
until you've had the conversation with the upstream maintainer.
On my end this week, I'll start with Ian's Part 3 Pub/Sub prototype and the
Part 5 binary encoding repo, and exercise the four live servers in parallel
for interoperability observations. If anything useful comes out of that for
either of your tracks, I'll surface it.
Good to hear about the new Publisher and Explorer apps too — it makes sense
to let the current ones graduate. Happy to be a sounding board on use cases
when you get to that stage.
Respectfully,
@nsnarayanam
Respectfully,
@nsnarayanam
…On Sun, May 10, 2026 at 10:31 PM Sam Bolling ***@***.***> wrote:
Awesome, @nsnarayanam <https://github.com/nsnarayanam> and thank you!
I gave @tipatterson-dev <https://github.com/tipatterson-dev> (goes by
Ian) a heads up that you expressed interest in reviewing his active work.
For your awareness, I have localized my efforts to address the findings
you shared with me as phase-9 of the typescript client library CSAPI code
contribution. I have a first draft of my research on it here
https://github.com/tipatterson-dev, which has shaken out a preferred COA.
My next steps are to experiment that COA thoroughly, here is my draft
experimentation plan
https://github.com/OS4CSAPI/ogc-client-CSAPI_2/blob/phase-9/docs/research/phase-9/02-live-testing-experiment-plan.md.
Both documents will get iterated on before finalized and executed. I have a
bit of prep work to do on the data publishing work and the webapp to
prepare my testing environment before I begin which might actually take
most of the next 3 days. Afterwards I will implement the fix in my working
repo, port the clean update into my pr repo and update the PR for the
upstream. The one work item I am tracking that I will want to discuss with
the upstream maintainer is the parsers for SWE Common work
<OS4CSAPI/ogc-client-CSAPI_2#171>, which I am
triaging behind OS4CSAPI/ogc-client-CSAPI_2#187
<OS4CSAPI/ogc-client-CSAPI_2#187>.
Additionally, I was apprised of another CSAPI implementation based out of
Europe and invited to review it and provide feedback. It is still internal
and early prototype stages, so there won't be much visibility on that
background activity this sprint.
Lastly, I have two big visions beyond the scope of this event. Both my CSAPI
Explorer App <https://github.com/OS4CSAPI/ogc-csapi-explorer> and my fork
of OSHConnect-Python
<https://github.com/%5BOS4CSAPI/OSHConnect-Python%5D(https://github.com/OS4CSAPI/OSHConnect-Python)>
have just about completed their purposes. As soon as I finish up the rest
there is to immediately learn from them, I intend to begin a new CSAPI
Publisher App and a new CSAPI Explorer App to replace them, both of which
would be more use-case and purpose driven than the exploratory nature of
their predecessors. I will likely keep the legacy projects alive for some
time for experimental use.
*Respectfully*,
@Sam-Bolling <https://github.com/Sam-Bolling>
—
Reply to this email directly, view it on GitHub
<#39 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BKUGDBG4YQMGEZLDU74HULL42CYVZAVCNFSM6AAAAACYYBXI7CVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMOBXGEYDCOI>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
This discussion is a place to continue CSAPI coordination conversations that started in the OGC Builder Days “what are you working on?” issue, without overloading that thread.
Use this space for CSAPI-related follow-up, including sprint focus areas, review notes, blockers, demos, implementation ideas, repo links, and daily coordination details.
Main participation guide:
https://os4csapi.github.io/code-sprint-guide/builder-days-2026/
Beta Was this translation helpful? Give feedback.
All reactions