Search results

From Earth Science Information Partners (ESIP)
  • Alvaro How do we populate information for the tools? * New user - the goal is for the user to provide feedback about the tool and/or the site. * Developer
    36 KB (5,864 words) - 13:13, May 30, 2013
  • netCDF4 and HDF5 introduce the idea of User Defined Types (UDT) which are essentially structures that can be defined by users to address specific needs. These
    22 KB (2,892 words) - 07:44, July 10, 2013
  • to provide improved user interoperability with data center data? (Alternately, should data centers provide the data and let users determine how to manipulate
    3 KB (495 words) - 16:53, January 7, 2009
  • Formulate and consistently present user requirements for data quality ... Suggested speakers: Eloquent representative from a user community who present a compelling
    3 KB (355 words) - 13:53, January 6, 2011
  • develop the interface, adding scatter plot functionality, making the site more user-friendly, and expanding the number of GOES-11 images included. A portal (http://zulu
    3 KB (482 words) - 12:41, August 19, 2012
  • to classify these articles into broad research topics to provide the end user of Usage Based Discovery with a way to browse the many articles. We have
    2 KB (354 words) - 12:10, September 29, 2021
  • and permissions - what is difference between ESIP member and authenticated user? what is the authentication plan for ESIP portal in general? do multiple
    3 KB (393 words) - 15:02, March 12, 2012
  • Workspace Template Queries set up by the "admin" at the beginning then guide the user in how to tag content for easier contributions.
    253 bytes (63 words) - 22:58, January 16, 2008
  • < GEO User Requirements for Air Quality | Report | Documents | Resources | Edit with Form Doc #: Title: DIRECTIVE 2008/50/EC OF THE EUROPEAN PARLIAMENT
    1 KB (132 words) - 18:54, March 28, 2012
  • Evaluation City Center Linking Earth Sciences and GEOSS: The role of the GEOSS User Requirement Registry (URR) Mt. Vernon
    526 bytes (4 words) - 08:38, January 2, 2012
  • < GEO User Requirements for Air Quality | Report | Documents | Resources | Edit with Form Doc #: Title: Reduction in personal exposures to particulate
    587 bytes (106 words) - 12:35, September 30, 2009
  • data and information Goal 2: Strengthen the ties between observations and user communities (e.g. technologies, research, education and applications) Goal
    4 KB (496 words) - 13:24, April 14, 2015
  • science data and information. Strengthen the ties between observations and user communities (e.g. technologies, research, education and applications). Promote
    3 KB (374 words) - 08:59, March 8, 2016
  • https://docs.google.com/document/d/1ymt5vsP2jw2YMVnc2B8uEI0BKTHcT4jSNVQzruLIFPA/edit User cases for :Discovery mandate: Jump in front with a simple, demonstrable concept
    2 KB (275 words) - 13:01, May 6, 2014
  • < GEO User Requirements for Air Quality | Report | Documents | Resources | Edit with Form Doc #: 1 Title: Impacts of Roadway Emissions on urban particulate
    927 bytes (129 words) - 20:57, October 20, 2009
  • < GEO User Requirements for Air Quality | Report | Documents | Resources | Edit with Form Doc #: 108 Title: Frameworks For Regional Co-operation on Air
    1 KB (179 words) - 09:53, October 8, 2021
  • includes links to tools and methods relevant for each step of the EE rule. The User Support section is a grouping of help resources for the EE tools, as well
    1 KB (201 words) - 15:27, April 14, 2013
  • to the document * WKT subset description as per OGC/CWIC Best Practices * User 'via' relation for metadata links * xlink element as child of atom:link to
    2 KB (260 words) - 07:19, April 2, 2014
  • < GEO User Requirements for Air Quality | Report | Documents | Resources | Edit with Form Doc #: 102 Title: Will the Circle Be Unbroken: A History of the
    427 bytes (87 words) - 21:03, October 20, 2009
  • < GEO User Requirements for Air Quality | Report | Documents | Resources | Edit with Form Doc #: 104 Title: Particulate MAtter Science for Policy Makers;
    324 bytes (54 words) - 15:20, October 20, 2009
  • Cluster in the future. It would be good know how the application groups develop user strategies. The results from the meeting could be published as a white paper
    2 KB (409 words) - 02:35, December 16, 2009
  • Investigator Data Originator User Services Instrument Distributor Quality Assessment For detailed guidance see the ECHO Data Partner User Guide. People and Organizations
    27 KB (1,217 words) - 12:35, September 21, 2015
  • The software or user processor is responsible to update these attributes as part of the processing, but some software processes and user practices leave
    20 KB (2,763 words) - 14:02, January 5, 2015
  • (DIP), which is a collection of information distributed in response to a user order. The OAIS RM identifies "Archive Information Units" (AIUs) that are
    9 KB (1,339 words) - 16:07, January 6, 2014
  • will grow to cover the breadth of Earth Science, including our variety of users and the entire data life cycle. The use cases are intended to be characteristic
    3 KB (374 words) - 23:44, December 12, 2013
  • draft of testbed proposal: Testbed Proposal Draft NSTA - Recap EarthCube End User Workshop Recap Other Ideas? CLEAN was featured on the ESIP blog. Might be
    3 KB (411 words) - 08:00, April 17, 2014
  • and ESC are similar, but the user groups are different Earth Cube focusing on long-tail communities ESIP focused on user side of things 3. Develop agenda
    5 KB (870 words) - 04:30, June 21, 2012
  • data need to be put out there. NASA: direction from a user community. ie, look at actual needs for users, then find data to meet them. these are “focus areas”
    60 KB (9,067 words) - 17:41, December 14, 2015
  • additional annotation information. This additional information is available to the user so they may not need to look up the resource cited in the CI_Citation. These
    17 KB (846 words) - 14:59, January 4, 2017
  • Connor's content for the "Usability Test Script" 2) Presentation on "Measuring User Experience" 3) Discussion of the Framework's "Post-Test Reflection" section
    640 bytes (82 words) - 15:40, April 18, 2018
  • result 3 mdq:specification 1 cit:CI_Citation Citation for the specification or user requirement used to evaluate the data. 4 mdq:explanation 0..1 gco:CharacterString
    2 KB (23 words) - 07:47, August 17, 2017
  • Community catalog for finding and accessing data through standard formats WMS. User-oriented ... Tagging Screencasting - show how to do something instead of
    1 KB (128 words) - 19:47, June 2, 2012
  • +1 (872) 240-3212 Access Code: 194-160-661 1) Presentation on "Measuring User Experience" 2) Discussion of the Framework's "Post-Test Reflection" section
    625 bytes (79 words) - 09:51, July 30, 2018
  • the agenda): Stresa debrief David: UIC injected new energy; activity plan; user classes to help portal functionality; AQ- GEOSS session & Pannel discussion
    767 bytes (93 words) - 08:05, May 29, 2009
  • communication facilities. Matching the mechanical support system to the human user needs is an art that is difficult to master. This figure represents an attempt
    7 KB (869 words) - 14:59, March 20, 2008
  • < GEO User Requirements for Air Quality | Report | Documents | Resources | Edit with Form Doc #: 59 Title: Ground-level ozone in the 21st Century: Future
    1 KB (156 words) - 22:16, October 20, 2009
  • Infrastructure (GCI) work collaboratively across GEO committees (e.g. UIC to get user needs) AIP 2 Achievements Community of Practice Scenarios Reusable Processes
    3 KB (353 words) - 14:09, July 22, 2012
  • search interface supporting free text and faceted searching would expand user options, and allow integration of software library specific keywords (i.e
    2 KB (246 words) - 14:36, November 4, 2020
  • < GEO User Requirements for Air Quality | Report | Documents | Resources | Edit with Form Doc #: 94 Title: European Exchange and Monitoring Information
    1 KB (213 words) - 16:35, October 21, 2009
  • that momentary science needs of a user. Various parts of the PCCS matrix apply to different levels of data. Certain users will only be interested in some
    2 KB (301 words) - 10:50, January 25, 2012
  • Chris Lynnes (EOSDIS) - Lead Bob Downs (SEDAC): Intrigued by user perspective, looking to broaden discovery to include the exploration needed before deciding
    2 KB (331 words) - 13:36, March 20, 2020
  • frequency and status. GEO Portal: user can search for something (eg energy/environment)- for a more focused search, the user can go to the thematic Portal
    36 KB (5,793 words) - 20:39, July 26, 2011
  • data and information. GOAL 2: Strengthen the ties between observations and user communities (e.g. technologies, research, education and applications). GOAL
    6 KB (778 words) - 09:38, March 14, 2017
  • OpenSearch Best Practices status CMR OpenSearch Status NLP technology (Doug) User drive data exploration tie-ins Minutes
    673 bytes (99 words) - 15:53, November 8, 2016
  • wide variety of end users. Data interoperability requires a human dimension to consistently implement best practices and standards. User acceptance should
    1,017 bytes (155 words) - 13:23, November 22, 2013
  • its effectiveness. Here are a few to get us started: Register and create a user page for yourself. It may be useful to list a common set of descriptors listing
    1 KB (173 words) - 09:28, May 13, 2009
  • build template with the key features What are the user needs? 2010-01-12: Gap Analysis between user needs and workspace capabilities What scenario is it
    4 KB (524 words) - 12:40, January 24, 2010
  • better connections with the users We need someone to represent the users Getting tools out to the community. Get the user community involved in case studies
    3 KB (510 words) - 12:53, February 24, 2010
  • topics this summer. Logistics (5 min) Got User_Id? Can you sign on? If not, see Hook Hua or Emily Law to get a user_id and/or help signing on. Basic capabilities
    3 KB (392 words) - 15:58, July 26, 2012
  • User mri:MD_DataIdentification if documenting Data User srv:SV_ServiceIdentification if documenting a Service Possible Parent Elements
    8 KB (16 words) - 06:25, August 16, 2017

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)