1 / 4

Geometry Project

Geometry Project. Ed Guinness MC Face-to-Face Meeting UCLA November 28-29, 2012. Background. From the August MC meeting notes:

gage-hall
Download Presentation

Geometry Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Geometry Project Ed Guinness MC Face-to-Face Meeting UCLA November 28-29, 2012

  2. Background • From the August MC meeting notes: • Acton proposed PDS/IPDA ascertain functional requirements on geometry from an end user’s (scientist’s) perspective before setting out to specify what and where geometry items will be included in archives. • Showalter will have much more input in six months. • Guinness thinks that fixed set of keywords in labels may not be the solution for all data sets. • Acton proposed the topic be given real attention at some appropriate time in the future. • It was suggested that the DDWG report to MC at the next face-to-face meeting and table the discussion for six months. • About a month ago, Steve Hughes asked me to lead a DDWG subgroup on geometry. Geometry Project

  3. Approach • A chief concern expressed by Acton is the absence of a functional view overall role of geometry in the PDS4 archive. • Functions: • Metadata for search. • Metadata for science analysis. • Ancillary data files for (more robust or more accurate) science analysis. • Geometry services, e.g., WebGeoCalc, geometry engine, Rings Node backplane generator. • Location within the archive: • Labels. • Data records. • Backplanes. • Ancillary Files. • Capture geometry requirements from discipline nodes, data providers, and data users in a white paper. • Produce a class hierarchy of geometry objects and services needed to meet the requirements. Geometry Project

  4. Status • This approach is closely aligned with Acton's goal for the IPDA geometry project. • Acton believes the two efforts could be merged into one with PDS4 leading the charge and seeking IPDA concurrence. • Acton and I asked for inputs from MEX DAWG two weeks ago. • Nicolas Manaud agreed to send requirements based on PSA needs. • A MARSIS data user presented a scenario for searching for radar sounder data. • Action Item for discipline nodes: • Please provide Guinness and Acton vision of how geometry should fit into PDS4. • Include what should be done in PDS4 and what doesn’t work or is missing in PDS3. • Schedule: Have a draft of the white paper for the next MC face-to-face meeting. Geometry Project

More Related