Search results

From Earth Science Information Partners (ESIP)
  • MD Georectified (category ISO Explorer)
    MD_Georectified if not utilizing Imagery extensions Possible Parent Elements ISO_Spatial_Representation
    9 KB (21 words) - 07:53, October 30, 2018
  • completely removed template concept added get_range method to all relevant iso_time Time classes changed pync3 time filtering code to handle exact points
    9 KB (1,140 words) - 16:39, April 23, 2012
  • or upload metadata form. 3.The metadata record is validated to ensure it meets the minimum FGDC and ISO requirements established by GOS. 4.The metadata record
    4 KB (627 words) - 17:12, February 27, 2006
  • process. The different types of auditing models/approaches available (e.g. ISO 16363). Trade-offs between internal versus official auditing procedures. AGU’s
    6 KB (935 words) - 10:51, October 3, 2016
  • DocBuilder - QA Viewer has built in validation of keywords, can upload DIF/ECHO and will validate record against KMS, eventually ISO. -- no date for production
    3 KB (400 words) - 13:03, April 25, 2016
  • considerations may include the need to integrate with other metadata schemes such as ISO, and application to data citation formats and practices. Ultimate Benefit:
    16 KB (41 words) - 09:55, November 26, 2016
  • time zone they would like to receive the data in. ISO 8601 (http://www.iso.org/iso/home/standards/iso8601.htm) is an international standard covering the
    33 KB (4,946 words) - 16:26, June 25, 2014
  • al Committee on Geographic Information/Geomatics' (ISO/TC211) standard for geographic metadata, ISO 19115, was finalized in 2003. Since then, its use has
    47 KB (6,836 words) - 11:37, February 3, 2012
  • Time Session Leader 1:30-2:15 FGDC and ISO Geospatial Metadata Standards Ted Habermann 2:30-3:15 The Proliferation of Metadata Standards and the Evolution
    7 KB (386 words) - 12:28, May 23, 2008
  • wrappers to all the essential C calls, and the module datafed.iso_time helps in interpreting ISO 8601 time range encoding. All you need is a bunch of netCDF
    35 KB (5,236 words) - 12:07, July 29, 2012
  • time zone they would like to receive the data in. ISO 8601 (http://www.iso.org/iso/home/standards/iso8601.htm) is an international standard covering the
    28 KB (4,283 words) - 10:21, April 8, 2014
  • C:\OWS\web The folder datafed contains datafed package, which contains tools for ISO 8601 time parsing and python-NetCDF module nc3 (not in point). Web is the
    22 KB (2,866 words) - 12:29, October 12, 2012
  • Category:ISO Building Blocks (category ISO Building Blocks) (section ISO Building Blocks Contents)
    from other dialects into ISO, identifying common validation errors, and introducing some tools for improving metadata records. ISO extents provide one of
    1 member (1 subcategory, 0 files) - 17:02, March 14, 2017
  • not the validated) version by Jan 27 - add esip_data as the namespace (for now) for all non-name-spaced classes - Luis to help with fgdc/gml/iso review
    6 KB (912 words) - 16:51, January 9, 2009
  • long as the UTC offsets are included in the timestamps, probably using the ISO standard, that should provide sufficient data for retrieval using unambiguous
    7 KB (881 words) - 09:14, April 18, 2013
  • Interestes: ISO metadata for documentation, web services for interoperability, and netCDF technologies (THREDDS data server, CF convention) as applied
    400 bytes (52 words) - 09:58, July 20, 2012

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