From Exchange Network Wiki

Draft Agenda May 27 Geo Team II Call

With the EN National meeting come and gone, it's time to get to our chartered work. This meeting will focus on updates and discussion about how to focus and organize ourselves around our products. As it has been many weeks since our last call, there is a lot to catch up on.

1. Agenda Review and Roll Call 2. Review Team Charter and Proposed Products

2a. Review Draft Interoperability matrix.

2b. Identify/refine the BUSINESS CASES for the USE Cases (e.g. for schema design, we know we want to be able to carry lines and areas...but what is a compelling/illustrative business case)? Same question for the demonstration and WFS stuff - What is the compelling business case for these geo applications so that the team's work is relevant?

3. Quick updates and impressions from the national meeting

• What did people who watched the presentations think?
• What questions did presenters or others get?
• What adjustments/re-focus should be made for our proposed products list?

--do presentations on website really capture message? Under the hood stuff. --John: location editor interest (on capture and correction of geometry) e.g. link to presentation --how to get started defining geoRSS schema, guidance and working examples, examples of operational stylesheets --whatever produced, people wanted to be able to re-use, some software that was re-usable. Reading native EN flows and making geoRSS or other availible. --interest in exploring georss as alterting/notification. [current demo only takes WQ...we need to make it generic]

4. Update/briefing on Schema Design and exciting new information on WFS/WFSS - We were unable to schedule a full schema design team meeting but have done some research we want to share that addresses questions from the last two calls.

5. Jerry, et al. help us peek under the hood of the demo to see where more work is needed and what the real issues are.

• Is this the functionality we want to demonstrate? What linkages are missing?
• What did we mock up that we actually need to do/test?

5a. Review straw proposal for an "EN geo mapping and feature service"

6. Organizing Next steps

May 27 Geo Task Force call summary bullets

Impressions from the National Meeting

• PowerPoint presentations don’t fully capture the message
• There was interest in the WA location editor on capture and correction of geometry
• People want to know how to get started using GeoRSS schema (e.g., guidance and working examples, examples of style sheets that do the translation well).
• People want to be able to re-use whatever is produced
• Interest in GeoRSS alert/notification
• Glen suggests doing more work on the demo and inviting a wider audience to have a webcast discussion.

Jerry’s presentation – under the hood

• Two options when a user zooms in on an area:
  • Ability to create a watch/feed for changes to a facility or analyte of interest
  • Discovery of data (Haven’t yet created a live translation for ENDS and CSW).
• Project, station, analyte, and facility data are done amic html. One EN call to stations. Stations executes a query and transforms it into GeoRSS.
• The demo uses a map service with embedded EN data. It does not tell people how they might use WFS and link WFS to EN.
• Jerry’s hopeful Image Matters guys can come back to work in two weeks (~6/10) when military contract comes through.
• Showing discovery integration is key to the mission of this group.

Schema design

§ Group to come up with examples of what GeoRSS would look like in EN schema. (We’re just using GeoRSS GML profile schema – a subset of GML.)

§ A 303d listed stream would be a good line segment to relate to. (Streams can be curved).

§ There’s a group in Austin that has led geo database work and have a complex arc hydro database.

§ We will just point people to GML examples if they absolutely cannot use GeoRSS.

§ WFS can take an attribute query and always returns a GML file.

§ In some cases WFSS might suffice for what people need to have WFS and GML services running side by side.