{"id":8,"date":"2012-03-28T17:05:51","date_gmt":"2012-03-29T00:05:51","guid":{"rendered":"http:\/\/blog.light42.com\/wordpress\/?page_id=8"},"modified":"2022-03-19T16:33:26","modified_gmt":"2022-03-19T23:33:26","slug":"8-2","status":"publish","type":"page","link":"http:\/\/blog.light42.com\/wordpress\/?page_id=8","title":{"rendered":"Info"},"content":{"rendered":"

<\/code>
\nby Brian M Hamlin, OSGeo California Chapter<\/p>\n

https:\/\/firms.modaps.eosdis.nasa.gov\/usfs\/<\/p>\n

https:\/\/earthdata.nasa.gov\/learn\/articles\/usfs-firms-us-canada<\/p>\n

https:\/\/earthdata.nasa.gov\/earth-observation-data\/near-real-time\/firms<\/p>\n

https:\/\/gwis.jrc.ec.europa.eu\/about-gwis\/technical-background\/active-fire-detection<\/p>\n

https:\/\/wiki.earthdata.nasa.gov\/pages\/viewrecentblogposts.action?key=FIRMS<\/p>\n

https:\/\/firms.modaps.eosdis.nasa.gov\/usfs\/map\/#d:24hrs;@-122.2,38.5,10z<\/p>\n

https:\/\/earthdata.nasa.gov\/collaborate\/open-data-services-and-software\/data-information-policy\/data-levels<\/p>\n

 <\/p>\n

LANCE Citation, Acknowledgements and Disclaimer<\/i>\u00a0<\/a><\/h3>\n
\n

NASA promotes the full and open sharing of all data with the research and applications communities, private industry, academia, and the general public. Read NASA’s\u00a0Data and Information Policy<\/a>.<\/p>\n

If you provide NASA’s Land, Atmosphere Near real-time Capability for EOS (LANCE<\/a>) \/ Fire Information for Resource Management System (FIRMS<\/a>) data to a third party, we request you follow the guidelines below and replicate or provide a link to the\u00a0disclaimer<\/span><\/a>.<\/p>\n

Acknowledgements<\/strong><\/h3>\n

We request that end users who make use of LANCE data products or imagery for subsequent distribution, deriving value added products, or using or referencing LANCE products in written or oral presentations to add the following acknowledgment.<\/p>\n

LANCE<\/h4>\n

We acknowledge the use of data and\/or imagery from NASA’s Land, Atmosphere Near real-time Capability for EOS (LANCE) system (https:\/\/earthdata.nasa.gov\/lance<\/a>), part of NASA’s\u00a0Earth Observing System Data and Information System (EOSDIS).<\/em><\/p>\n

Worldview<\/h4>\n

We acknowledge the use of imagery from NASA’s Worldview application (https:\/\/worldview.earthdata.nasa.gov<\/a>), part of NASA’s Earth Observing System Data and Information System (EOSDIS).<\/em><\/p>\n

Worldview Snapshots<\/h4>\n

We acknowledge the use of imagery from the Worldview Snapshots application (https:\/\/wvs.earthdata.nasa.gov<\/a>), part of the Earth Observing System Data and Information System (EOSDIS).<\/em><\/p>\n

GIBS<\/h4>\n

We acknowledge the use of imagery provided by services from NASA’s Global Imagery Browse Services (GIBS), part of NASA’s Earth Observing System Data and Information System (EOSDIS).<\/em><\/p>\n

FIRMS<\/h4>\n

We acknowledge the use of data and\/or imagery from NASA’s Fire Information for Resource Management System\u00a0(FIRMS) (https:\/\/earthdata.nasa.gov\/firms<\/a>), part of\u00a0NASA’s Earth Observing System Data and Information System (EOSDIS).<\/em><\/p>\n

 <\/p>\n

Please note – FIRMS distributes near real-time and standard\u00a0fire products from: Moderate Resolution Imaging Spectroradiometer (MODIS<\/a>) from the Terra and Aqua platforms, and Visible Infrared Imaging Radiometer Suite (VIIRS<\/a>) (375m) from the Suomi NPP and NOAA-20 platforms. \u00a0If you are using the data in a scientific publication, we encourage you to be\u00a0clear which source you use, and whether the data are NRT or Standard (more information\u00a0on the difference between NRT and standard fire data<\/a>). We recommend you read the\u00a0MODIS Fire User Guides<\/a>\u00a0to ensure you are using the most appropriate source of MODIS active fire data for your application.<\/p>\n

For Active Fire Data distributed via FIRMS:<\/strong><\/p>\n\n\n\n\n\n\n
VIIRS 375m NRT
\n(NOAA-20)<\/td>\n		NRT VIIRS 375 m Active Fire product\u00a0VJ114IMGTDL_NRT<\/a>\u00a0distributed from NASA FIRMS.<\/em>\u00a0Available on-line [https:\/\/earthdata.nasa.gov\/firms<\/a><\/u>]. doi:\u00a010.5067\/FIRMS\/VIIRS\/VJ114IMGT_NRT.002<\/a><\/td>\n<\/tr>\n
VIIRS 375m NRT
\n(Suomi NPP)<\/td>\n		NRT VIIRS 375 m Active Fire product\u00a0VNP14IMGT<\/a>\u00a0distributed from NASA FIRMS. Available on-line [https:\/\/earthdata.nasa.gov\/firms<\/a><\/u>].\u00a0\u00a0doi:10.5067\/FIRMS\/VIIRS\/VNP14IMGT_NRT.002<\/a><\/td>\n<\/tr>\n
MODIS Collection 61 NRT<\/td>\nMODIS Collection 61 NRT Hotspot \/ Active Fire Detections\u00a0MCD14DL<\/a>\u00a0distributed from NASA FIRMS.<\/em>Available on-line [https:\/\/earthdata.nasa.gov\/firms<\/a>].\u00a010.5067\/FIRMS\/MODIS\/MCD14DL.NRT.0061<\/a><\/td>\n<\/tr>\n
MODIS Collection 6 & 61(standard processing)<\/td>\nMODIS Collection 6 Hotspot \/ Active Fire Detections\u00a0MCD14ML<\/a>\u00a0distributed from NASA FIRMS.<\/em>\u00a0Available on-line [https:\/\/earthdata.nasa.gov\/firms<\/a>]. doi:\u00a010.5067\/FIRMS\/MODIS\/MCD14ML<\/a>Please note:\u00a0<\/strong><\/p>\n

MODIS Collection 61\u00a0<\/strong>has a temporal coverage from 01 Nov 2020 – present and
\nMODIS Collection 6\u00a0<\/strong>has a\u00a0<\/strong>temporal coverage from 11 Nov 2000 \u2013 30 Nov 2020<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Please read the\u00a0LANCE disclaimer<\/a>\u00a0for more information about using this data.<\/p>\n

For more specific data citations \/ acknowledgements:<\/h3>\n

Atmospheric Infrared Sounder (AIRS) and Microwave Limb Sounder (MLS) – GES DISC Data Use Acknowledgement<\/a><\/p>\n

AMSR2 Data citations by product<\/a><\/p>\n

Disclaimer<\/h4>\n

The LANCE system is operated by NASA’s Earth Science Data and Information System (ESDIS<\/a>) Project. The information presented through LANCE, Global Imagery Browse Services (GIBS<\/a>),\u00a0Worldview<\/a>, and FIRMS are provided \u201cas is\u201d and users bear all responsibility and liability for their use of data, and for any loss of business or profits, or for any indirect, incidental or consequential damages arising out of any use of, or inability to use, the data, even if NASA or ESDIS were previously advised of the possibility of such damages, or for any other claim by you or any other person. ESDIS makes no representations or warranties of any kind, express or implied, including implied warranties of fitness for a particular purpose or merchantability, or with respect to the accuracy of or the absence or the presence or defects or errors in data, databases of other information. The designations employed in the data do not imply the expression of any opinion whatsoever on the part of ESDIS concerning the legal or development status of any country, territory, city or area or of its authorities, or concerning the delimitation of its frontiers or boundaries. For more information please contact\u00a0Earthdata Support<\/a>.<\/p>\n<\/div>\n

 <\/p>\n

—<\/p>\n

\n

Data Processing Levels<\/h3>\n

https:\/\/earthdata.nasa.gov\/collaborate\/open-data-services-and-software\/data-information-policy\/data-levels<\/p>\n

NASA’s Earth Observing System Data and Information System (EOSDIS<\/a>) data products are processed at various levels ranging from Level 0 to Level 4. Level 0 products are raw data at full instrument resolution. At higher levels, the data are converted into more useful parameters and formats. All EOS instruments must have Level 1 Standard Data Products (SDPs); most\u00a0have SDPs at Level 2 and Level 3; and many have Level\u00a04 SDPs. Some EOS Interdisciplinary Science Investigations also have generated Level 4 SDPs. Specifications for\u00a0the set of SDPs to be generated are reviewed by the Earth Observing System Project Science Office (EOSPSO) and NASA Headquarters to ensure completeness and\u00a0consistency in providing a comprehensive science data\u00a0output for EOS. Standard data products are produced at NASA’s Distributed Active Archive Centers (DAACs<\/a>) or Science Investigator-led Processing Systems (SIPS<\/a>).<\/p>\n\n\n<\/colgroup>\n\n<\/colgroup>\n\n\n\n\n\n\n\n\n\n\n\n\n
Data Level<\/strong><\/td>\nDescription<\/strong><\/td>\n<\/tr>\n
Level 0<\/td>\nReconstructed, unprocessed instrument and payload data at full resolution, with any and all communications artifacts (e.g., synchronization frames, communications headers, duplicate data) removed. (In most cases, NASA’s EOS Data and Operations System [EDOS<\/a>] provides these data to the DAACs\u00a0as production data sets for processing by the Science Data Processing Segment [SDPS<\/a>] or by one of the SIPS\u00a0to produce higher-level products.)<\/td>\n<\/tr>\n
Level 1A<\/td>\nLevel 1A (L1A) data are reconstructed, unprocessed instrument data at full resolution, time-referenced, and annotated with ancillary information, including radiometric and geometric calibration coefficients and georeferencing parameters (e.g., platform ephemeris) computed and appended but not applied to L0 data.<\/td>\n<\/tr>\n
Level 1B<\/td>\nL1B data are L1A data that have been processed to sensor units (not all instruments have L1B source data).<\/td>\n<\/tr>\n
Level 1C<\/td>\nL1C data are L1B data that include new variables to describe the spectra. These variables allow the user to identify which L1C channels have been copied directly from the L1B and which have been synthesized from L1B and why.<\/td>\n<\/tr>\n
Level 2<\/td>\nDerived geophysical variables at the same resolution and location as L1 source data.<\/td>\n<\/tr>\n
Level 2A<\/td>\nL2A data contains information derived from the geolocated sensor data, such as\u00a0ground elevation, highest and lowest surface return elevations, energy quantile heights (\u201crelative height\u201d metrics), and other waveform-derived metrics describing the intercepted surface.<\/td>\n<\/tr>\n
Level 2B<\/td>\nL2B data are L2A data that have been processed to sensor units (not all instruments will have a L2B equivalent).<\/td>\n<\/tr>\n
Level 3<\/td>\nVariables mapped on uniform space-time grid scales, usually with some completeness and consistency.<\/td>\n<\/tr>\n
Level 3A<\/td>\nL3A data are generally periodic summaries (weekly, ten-day, monthly) of L2 products.<\/td>\n<\/tr>\n
Level 4<\/td>\nModel output or results from analyses of lower-level data (e.g., variables derived from multiple measurements).<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

—<\/p>\n

\n

OSGeo-Live 9.5 Construction, Python, netCDF and hdf5<\/h4>\n

by Brian M Hamlin, OSGeo California Chapter
\nTwo major layers define software installation on OSGeo-Live<\/a>. The first are build scripts in the form install_xxx<\/code> — where xxx is a project name — that are called in order from the VM build main.sh<\/code>. The second and increasingly important layer of software installation, are the Debian Packages, which declare a dependency tree in the Debian way. This document looks at the install process for netCDF, hdf5 and their python interfaces, at both layers of install on the OSGeo-Live, for the purpose of documentation and coming architectural decisions as the installs evolve.
\n\"live-install-work0F\"<\/a><\/p>\n

\"netcdf1_sm\"<\/a>
\nfrom Wikipedia<\/em>:<\/p>\n

NetCDF<\/strong> (Network Common Data Form) is a set of software libraries and self-describing, machine-independent data formats that support the creation, access, and sharing of array-oriented scientific data. The project homepage is hosted by the Unidata program at the University Corporation for Atmospheric Research (UCAR<\/strong>). They are also the chief source of netCDF software, standards development, updates, etc. The format is an open standard. NetCDF Classic and 64-bit Offset Format are an international standard of the Open Geospatial Consortium<\/strong>.[ netCDF<\/a> ]<\/p><\/blockquote>\n

Since the release of netCDF4 by Unidata<\/a>, internal data format hdf5<\/a><\/strong> is natively supported. Therefore, an hdf5 library is a build-dependancy for a debian package install of netCDF4. There are several similar-sounding packages and versions of netCDF software. The historical netCDF situation on OSGeo-Live is discussed -here-<\/a>.<\/p>\n

Examining the Install Process and Results in OSGeo-Live 9.5<\/strong><\/p>\n

In the OSGeo-Live 9.5 build system, two scripts among others, trigger apt<\/code> python package install actions: install_jupyter.sh<\/code> and install_iris.sh<\/code>. These two scripts both install python packages which in turn install the netCDF core libraries (in practice install_jupyter<\/code> is first to execute and brings in the bulk of the dependancies).<\/p>\n

Jupyter<\/a> and IRIS<\/a> trigger netCDF installs.<\/em><\/p>\n

The defacto install sequence is shown using an OSGeo-Live build log parse<\/a> chroot-build.log<\/code>. A python tool parses the build log and extracts apt<\/code> output, emitting comma-separated rows to stdout, and optionally building a postgres<\/strong> table directly at the same time.<\/p>\n

During the OSGeo-Live 9.5<\/strong> build, an install script called install_jupyter<\/code> ran which caused apt<\/code> to install debian packages listed.<\/p>\n

dbb=# select * from parseout95_rc1 where script_name = 'install_jupyter' order by pkg_name,action;\r\n\r\n   script_name   | action |        pkg_name         \r\n-----------------+--------+-------------------------\r\n install_jupyter | NEW    | fiona\r\n...\r\n install_jupyter | NEW    | libgfortran3\r\n install_jupyter | NEW    | libhdf4-0-alt\r\n install_jupyter | NEW    | libhdf5-7\r\n...\r\n install_jupyter | NEW    | python-netcdf\r\n install_jupyter | NEW    | python-netcdf4\r\n install_jupyter | NEW    | python-notebook\r\n install_jupyter | NEW    | python-numpy\r\n...\r\n install_jupyter | NEW    | rasterio\r\n(245 rows)\r\n<\/pre>\n
parseout95_rc1<\/code> table: script_name<\/code> the name of the install script running when an apt action occurred; action<\/code> the name of the apt action; pkg_name<\/code> the apt package name affected. A SQL query result above (abbreviated) to show hdf5 and netCDF related packages, triggered to install via script install_jupyter<\/code> at OSGeo-Live build time.<\/p>\n
Summary of all install actions: selected install scripts and the corresponding number of debian packages they install:<\/em><\/p>\n
setup, 145\r\ninstall_language, 30\r\ninstall_services, 2\r\ninstall_java, 14\r\ninstall_tomcat, 9\r\n...\r\ninstall_postgis, 33\r\ninstall_jupyter, 137\r\ninstall_iris, 17\r\ninstall_osm, 62\r\ninstall_gmt, 10\r\ninstall_liblas, 3\r\ninstall_mapnik, 6\r\ninstall_mysql, 11\r\ninstall_R, 71\r\ninstall_pycsw, 5\r\n...\r\n<\/pre>\n
note: the number of debian packages installed by each script is highly dependent<\/em> on the execution order of the build, since common dependencies will be brought in by the first script to invoke them.<\/p>\n
 <\/p>\n
Reading a Debian Pool Directory<\/h4>\n
An experimental toolset PPA-Pool-Parse<\/strong> reads a Debian\/Ubuntu PPA pool directory, finds source package control files dot-dsc, copies them and parses their contents, one key-value pair at a time. The result is a cross-referenced attribute table for every package described, for all architectures and all OS versions, in the PPA. Here three PPA<\/strong>s have been analyzed: stable<\/strong>, unstable<\/strong> and testing<\/strong>.<\/p>\n
http:\/\/ppa.launchpad.net\/ubuntugis\/ppa\/ubuntu\/pool\r\nhttp:\/\/ppa.launchpad.net\/ubuntugis\/ubuntugis-unstable\/ubuntu\/pool\r\nhttp:\/\/ppa.launchpad.net\/ubuntugis\/ubuntugis-testing\/ubuntu\/pool\r\n<\/pre>\n
Each extracted source control file (.dsc) has a set of key-value pairs :<\/p>\n
dbb=# select dsc_name,dsc_key,dsc_val from dsc_all where ppa_name = 'stable_dsc' and dsc_name ~ 'cdf'\r\n        order by dsc_name,dsc_key;\r\n--------------------------------+-------------------+--------------------------------------\r\n python-netcdf4_1.1.0-0~trusty1 | Architecture      | any\r\n python-netcdf4_1.1.0-0~trusty1 | Binary            | python-netcdf4\r\n python-netcdf4_1.1.0-0~trusty1 | Build-Depends     | debhelper (>= 9), dpkg-dev (>= 1.16.1~), python-all-dev, libnetcdf-dev (>= 4.1.1~), python-numpy (>= 1:1.6.1~), zlib1g-dev, libhdf5-serial-dev (>= 1.8.4~) | libhdf5-dev (>= 1.8.4~), netcdf-bin\r\n python-netcdf4_1.1.0-0~trusty1 | Checksums-Sha1    | \r\n python-netcdf4_1.1.0-0~trusty1 | Checksums-Sha256  | \r\n python-netcdf4_1.1.0-0~trusty1 | Files             | \r\n python-netcdf4_1.1.0-0~trusty1 | Format            | 3.0 (quilt)\r\n python-netcdf4_1.1.0-0~trusty1 | Hash              | SHA1\r\n python-netcdf4_1.1.0-0~trusty1 | Homepage          | http:\/\/code.google.com\/p\/netcdf4-python\/\r\n python-netcdf4_1.1.0-0~trusty1 | Maintainer        | The Mer  -rememberthemer @gmail.com-\r\n python-netcdf4_1.1.0-0~trusty1 | Package-List      | \r\n python-netcdf4_1.1.0-0~trusty1 | Source            | python-netcdf4\r\n python-netcdf4_1.1.0-0~trusty1 | Standards-Version | 3.9.3\r\n python-netcdf4_1.1.0-0~trusty1 | Version           | 1.1.0-0~trusty1\r\n python-netcdf4_1.1.0-0~trusty1 | Version           | GnuPG v1\r\n(15 rows)\r\n\r\n<\/pre>\n
A second pass reads the key-value pair Build-Depends<\/code>, parses the named dependancies and builds a table of those. example: querying all source control descriptions in PPA ‘stable’, list dependancies whose names match hdf<\/code> or netcdf<\/code>:<\/p>\n
dbb=# select * from dsc_bdepends where ppa_name = 'stable_dsc' and (bdepends ~ 'hdf5' or bdepends ~ 'netcdf') order by dsc_name, bdepends;\r\n  ppa_name  |              dsc_name               |                   bdepends                   |  bd_constr   \r\n------------+-------------------------------------+----------------------------------------------+--------------\r\n stable_dsc | cartopy_0.11.0-0~trusty1            | libhdf5-serial-dev                           | ()\r\n stable_dsc | cartopy_0.11.0-0~trusty1            | libnetcdf-dev                                | ()\r\n stable_dsc | cartopy_0.11.0-0~trusty1            | netcdf-bin                                   | ()\r\n stable_dsc | gdal_1.10.0-1~precise1              | libhdf5-serial-dev                           | (>= 1.6.6)\r\n stable_dsc | gdal_1.10.0-1~precise1              | libnetcdf-dev                                | (>= 1:4.0.0)\r\n stable_dsc | gdal_1.10.0-1~precise1              | netcdf-bin                                   | ()\r\n stable_dsc | gdal_1.11.2+dfsg-1~exp2~trusty      | libhdf5-dev                                  | (>= 1.8.8)\r\n stable_dsc | gdal_1.11.2+dfsg-1~exp2~trusty      | libnetcdf-dev                                | (>= 1:4.0.0)\r\n stable_dsc | gdal_1.11.2+dfsg-1~exp2~trusty      | netcdf-bin                                   | ()\r\n stable_dsc | gdal_1.9.2-2~precise4               | libhdf5-serial-dev                           | (>= 1.6.6)\r\n stable_dsc | gdal_1.9.2-2~precise4               | libnetcdf-dev                                | (>= 1:4.0.0)\r\n stable_dsc | gmt_5.1.2+dfsg1-1~exp8~trusty       | libnetcdf-dev                                | ()\r\n stable_dsc | grass_7.0.1-1~exp1~trusty           | libnetcdf-dev                                | ()\r\n stable_dsc | grass_7.0.1-1~exp1~trusty           | netcdf-bin                                   | ()\r\n stable_dsc | insighttoolkit4_4.7.1-1otb1~trusty1 | libhdf5-serial-dev                           | ()\r\n stable_dsc | iris_1.6.1-0~trusty2                | libhdf5-serial-dev                           | ()\r\n stable_dsc | iris_1.6.1-0~trusty2                | libnetcdf-dev                                | ()\r\n stable_dsc | iris_1.6.1-0~trusty2                | netcdf-bin                                   | ()\r\n stable_dsc | iris_1.6.1-0~trusty2                | python-netcdf4                               | ()\r\n stable_dsc | mbsystem_5.5.2252-0~trusty          | libnetcdf-dev                                | ()\r\n stable_dsc | python-netcdf4_1.1.0-0~trusty1      | libhdf5-serial-dev (>= 1.8.4~) | libhdf5-dev | (>= 1.8.4~)\r\n stable_dsc | python-netcdf4_1.1.0-0~trusty1      | libnetcdf-dev                                | (>= 4.1.1~)\r\n stable_dsc | python-netcdf4_1.1.0-0~trusty1      | netcdf-bin                                   | ()\r\n(23 rows)\r\n<\/pre>\n
Debian Packages<\/h4>\n
A Debian source .dsc<\/strong> file describes a source package<\/a>. Here is a .dsc file for a python iris package. Notice the key-value pair Build-Depends<\/code> and the netCDF-related dependencies.<\/p>\n
iris_1.9.0-0~trusty2.dsc<\/a><\/p>\n
Build-Depends: libnetcdf-dev, netcdf-bin, python-netcdf4, …<\/p><\/blockquote>\n
see apt-cache depends packagename<\/code> and apt-rdepends<\/code><\/p>\n
some netCDF data from U.W.
\nftp:\/\/ftp.hydro.washington.edu\/pub\/blivneh\/CONUS\/<\/code><\/p>\n
Debian git endpoint: git:\/\/anonscm.debian.org\/pkg-grass\/netcdf.git<\/code><\/p>\n
Debian system package tracker for netCDF<\/a><\/p>\n
Debian VCS-Watch page -here-<\/a><\/p>\n
Popularity Contest page for netcdf source group : -here-<\/a><\/p>\n
Most of the base Debian packages in the OSGeo-Live ecosystem are maintained by Debian Developer (DD) Sebastic<\/a><\/p>\n
The latest versions available in Debian and upstream are
\nincluded in the Debian GIS DDPO<\/a><\/p>\n
Sebastic DD says in an email, look at Ben http:\/\/ben.debian.net\/
\nClicking twice showed a temporary “transition” document : href=\"https:\/\/release.debian.org\/transitions\/html\/auto-netcdf.html<\/code><\/p>\n
Ultimate Debian Database: udd.debian.org<\/a><\/p>\n
psql --host=public-udd-mirror.xvm.mit.edu --user=public-udd-mirror udd --password<\/code><\/p>\n
\n
udd=> select * from debtags where package ~* 'netcdf' order by tag,package;\r\n      package       |           tag           \r\n--------------------+-------------------------\r\n libpdl-netcdf-perl | devel::lang:perl\r\n python-netcdf      | devel::lang:python\r\n libnetcdf-dev      | devel::library\r\n libpdl-netcdf-perl | devel::library\r\n python-netcdf      | devel::library\r\n libpdl-netcdf-perl | implemented-in::c\r\n libnetcdf6         | implemented-in::fortran\r\n netcdf-bin         | implemented-in::fortran\r\n python-netcdf      | implemented-in::python\r\n netcdf-bin         | interface::commandline\r\n netcdf-doc         | made-of::html\r\n netcdf-doc         | made-of::info\r\n netcdf-doc         | made-of::postscript\r\n python-netcdf      | role::app-data\r\n netcdf-dbg         | role::debug-symbols\r\n libnetcdf-dev      | role::devel-lib\r\n netcdf-doc         | role::documentation\r\n netcdf-bin         | role::program\r\n libnetcdf6         | role::shared-lib\r\n libnetcdfc++4      | role::shared-lib\r\n libnetcdfc7        | role::shared-lib\r\n libnetcdff5        | role::shared-lib\r\n netcdf-bin         | scope::utility\r\n(23 rows)\r\n\r\nudd=> select * from all_sources where source = 'netcdf' and release = 'xenial';\r\nsource                | netcdf\r\nversion               | 1:4.4.0-2\r\nmaintainer            | Debian GIS Project \r\n...\r\nbuild_depends         | \r\ndebhelper (>= 9), cmake (>= 2.8.12), chrpath, m4, doxygen, graphviz,\r\nlibjs-jquery, libhdf5-dev (>= 1.8.6-1~), \r\nlibcurl4-gnutls-dev | libcurl-ssl-dev\r\n\r\n\r\nudd=> select source,version from all_sources where source ~* 'netcdf' and release = 'xenial';\r\n       source       |     version     \r\n--------------------+-----------------\r\n libpdl-netcdf-perl | 4.20-1.1build2\r\n netcdf             | 1:4.4.0-2\r\n netcdf-cxx         | 4.2.1-3\r\n netcdf-cxx-legacy  | 4.2-4\r\n netcdf-fortran     | 4.4.3-1\r\n netcdf4-python     | 1.2.2-2\r\n pnetcdf            | 1.7.0~pre1-1\r\n r-cran-rnetcdf     | 1.6.3-1-1build2\r\n ruby-netcdf        | 0.7.1.1-6build3\r\n(9 rows)\r\n\r\n\r\nudd=> select source,version from all_sources where source ~* 'hdf5' and release ~ 'xenial';\r\n       source        |       version        \r\n---------------------+----------------------\r\n hdf5                | 1.8.16+docs-4ubuntu1\r\n libpdl-io-hdf5-perl | 0.6501-2build2\r\n libsis-jhdf5-java   | 14.12.1-2\r\n python-hdf5storage  | 0.1.13-1\r\n r-cran-hdf5         | 1.6.10-3build2\r\n yorick-hdf5         | 0.8.0-5build2\r\n(6 rows)\r\n\r\nudd=> select * from debtags where package ~* 'hdf5' order by tag,package;\r\n        package        |           tag            \r\n-----------------------+--------------------------\r\n libhdf5-doc           | devel::doc\r\n libpdl-io-hdf5-perl   | devel::lang:perl\r\n libhdf5-dev           | devel::library\r\n libhdf5-doc           | devel::library\r\n libhdf5-lam-dev       | devel::library\r\n libhdf5-mpich2-dev    | devel::library\r\n libhdf5-mpich-dev     | devel::library\r\n libhdf5-mpi-dev       | devel::library\r\n libhdf5-openmpi-dev   | devel::library\r\n libhdf5-serial-dev    | devel::library\r\n libpdl-io-hdf5-perl   | devel::library\r\n r-cran-hdf5           | field::mathematics\r\n libhdf5-doc           | field::physics\r\n libhdf5-lam-dev       | field::physics\r\n libhdf5-mpich-dev     | field::physics\r\n libhdf5-serial-dev    | field::physics\r\n libpdl-io-hdf5-perl   | implemented-in::c\r\n r-cran-hdf5           | implemented-in::r\r\n hdf5-tools            | interface::commandline\r\n libhdf5-doc           | made-of::html\r\n libhdf5-dev           | role::devel-lib\r\n libhdf5-lam-dev       | role::devel-lib\r\n libhdf5-mpich2-dev    | role::devel-lib\r\n libhdf5-mpi-dev       | role::devel-lib\r\n libhdf5-openmpi-dev   | role::devel-lib\r\n libhdf5-serial-dev    | role::devel-lib\r\n hdf5-tools            | role::documentation\r\n libhdf5-doc           | role::documentation\r\n libhdf5-lam-dev       | role::documentation\r\n libhdf5-serial-dev    | role::documentation\r\n hdf5-tools            | role::program\r\n libhdf5-7             | role::shared-lib\r\n libhdf5-cpp-7         | role::shared-lib\r\n libhdf5-lam-1.8.4     | role::shared-lib\r\n libhdf5-mpich-1.8.4   | role::shared-lib\r\n libhdf5-mpich2-7      | role::shared-lib\r\n libhdf5-mpich-7       | role::shared-lib\r\n libhdf5-openmpi-1.8.4 | role::shared-lib\r\n libhdf5-openmpi-7     | role::shared-lib\r\n libhdf5-serial-1.8.4  | role::shared-lib\r\n libjhdf5-jni          | role::shared-lib\r\n hdf5-tools            | scope::utility\r\n r-cran-hdf5           | suite::gnu\r\n hdf5-tools            | use::converting\r\n libhdf5-doc           | use::storing\r\n libhdf5-lam-dev       | use::storing\r\n libhdf5-mpich-dev     | use::storing\r\n libhdf5-serial-dev    | use::storing\r\n(67 rows)\r\n\r\n<\/pre>\n<\/blockquote>\n
more on netCDF from Sebastic:<\/p>\n
If you’re looking for the interdependencies I would parse the Packages files from the PPA and analyse the Depends fields of the packages in question. ed. the method above achieves the same results<\/em><\/p>\n
Because I have coordinated the recent netcdf transitions, I have a
\npretty good idea of the dependency chain.<\/p>\n
netcdf-c (netcdf source package) is at the bottom, everything else
\ndepends on that. netcdf-cxx-legacy, netcdf-cxx, netcdf-fortran &
\nnetcdf4-python all require the netcdf package to build. netcdf in turn
\nrequires hdf5 to build.<\/p>\n
To help prepare transitions, I run a transition tracker [2] using the
\nben package [3] also used for Debian [4] & Ubuntu [5]. ben visualizes
\nthe reverse dependencies for packages and marks them as good or bad
\nbased on the regular expressions applied to the fields in the Packages
\nfiles (usually just Depends).<\/p>\n
[2] http:\/\/linuxminded.nl\/tmp\/pkg-grass-transitions\/html\/netcdf-c.html<\/a>
\n[3] https:\/\/tracker.debian.org\/pkg\/ben<\/a>
\n[4] https:\/\/release.debian.org\/transitions\/<\/a>
\n[5] https:\/\/people.canonical.com\/~ubuntu-archive\/transitions\/<\/a><\/p>\n
> Where is a convenient place to file an update ticket :
\n> “netCDF4 project home page has moved from code.google.com to github.com\/Unidata; update source description”<\/p>\n
Convenient != Appropriate<\/p>\n
You should file bugreports in the tracker for the repository in
\nquestion, in this case UbuntuGIS\/OSGeo-Live.<\/p>\n
If you verify that the issue is also present in the packaging maintained
\nby the Debian GIS team, you can contact the Debian GIS team via the
\nmailinglist or file a bugreport for the package in question.<\/p>\n
> dsc content:
\n> stable_dsc | python-netcdf4_1.1.0-0~trusty1 | Homepage | http:\/\/code.google.com\/p\/netcdf4-python\/
\n>
\n> make sense ? thanks<\/p>\n
That looks like the python-netcdf4 source package from OSGeo-Live 9.5,
\nit is maintained by The Mer -rememberthemer @gmail.com- according to its
\ncontrol file.<\/p>\n
It is not maintained by the Debian GIS team, the netcdf4-python package
\nis maintained by the Debian GIS team and included in Debian & Ubuntu. It
\ndoes not have these issues.<\/p>\n
Regarding NetCDF & Python, only the python{,3}-netcdf4 packages built
\nfrom the netcdf4-python source package are actively maintained. The
\npython-netcdf package built from the python-scientific package as used
\nby bin\/install_jupyter.sh is very problematic. It does not support newer
\nNumPy versions and has been broken in Debian for quite a while and has
\nrecently been removed from Debian because it was keeping the old NetCDF
\n4.1.3 packages in Debian unstable (due to being unable to build with the
\nnewer versions). [6]<\/p>\n
These issues with python-scientific also caused it to be removed from
\nUbuntu xenial, so bin\/install_jupyter.sh needs to be updated to not
\nrequire python-netcdf any more.<\/p>\n
[6] https:\/\/lists.debian.org\/debian-gis\/2016\/05\/msg00009.html<\/p><\/blockquote>\n
Misc<\/h4>\n
Other listings using PPA-Pool-Parse<\/b>:
\n—<\/p>\n
Search all source control files in the testing PPA for source package names:<\/p>\n
dbb=# select * from dsc_all \r\n  where dsc_key = 'Source' and ppa_name = 'testing_dsc' \r\n    order by dsc_val;\r\n\r\n  ppa_name   |                   dsc_name                   | dsc_key |     dsc_val      \r\n-------------+----------------------------------------------+---------+------------------\r\n testing_dsc | apache2_2.4.6-4~precise2                     | Source  | apache2\r\n testing_dsc | fiona_1.6.3-3~xenial0                        | Source  | fiona\r\n testing_dsc | gdal_2.1.0+dfsg-1~trusty0                    | Source  | gdal\r\n testing_dsc | gdal_2.1.0+dfsg-1~trusty1                    | Source  | gdal\r\n testing_dsc | gdal_2.1.0+dfsg-1~xenial0                    | Source  | gdal\r\n testing_dsc | gdal_2.0.2+dfsg-5~trusty0                    | Source  | gdal\r\n testing_dsc | gdal_1.10.0-1~precise1                       | Source  | gdal\r\n testing_dsc | geos_3.5.0-1~trusty1                         | Source  | geos\r\n testing_dsc | geos_3.3.8-2~precise1                        | Source  | geos\r\n testing_dsc | gmt_5.2.1+dfsg-3build2~xenial0               | Source  | gmt\r\n testing_dsc | gmt_5.2.1+dfsg-4ubuntu2~xenial0              | Source  | gmt\r\n testing_dsc | grass_7.0.4-1~xenial2                        | Source  | grass\r\n testing_dsc | liblas_1.8.0-7build2~xenial0                 | Source  | liblas\r\n testing_dsc | mapcache_0~git052512+a8a8fe848c+1-2~precise4 | Source  | mapcache\r\n testing_dsc | mapcache_1.4.0-5~xenial0                     | Source  | mapcache\r\n testing_dsc | mapnik_3.0.9+ds-2~xenial0                    | Source  | mapnik\r\n testing_dsc | mapserver_7.0.1-4~xenial0                    | Source  | mapserver\r\n testing_dsc | mapserver_6.2.0~beta1-2~precise8             | Source  | mapserver\r\n testing_dsc | mapserver_6.2.0~rc1-2~precise1               | Source  | mapserver\r\n testing_dsc | merkaartor_0.18.2-6~xenial0                  | Source  | merkaartor\r\n testing_dsc | openjpeg2_2.1.0-2.1otb1~trusty1              | Source  | openjpeg2\r\n testing_dsc | openscenegraph_3.2.3+dfsg1-1~trusty0         | Source  | openscenegraph\r\n testing_dsc | openscenegraph_3.2.3+dfsg1-1~trusty1         | Source  | openscenegraph\r\n testing_dsc | openscenegraph_3.2.3+dfsg1-1~trusty2         | Source  | openscenegraph\r\n testing_dsc | openscenegraph_3.2.3+dfsg1-1~xenial0         | Source  | openscenegraph\r\n testing_dsc | osgearth_2.7.0+dfsg-2~xenial0                | Source  | osgearth\r\n testing_dsc | ossim_1.81-1svn22135+precise1                | Source  | ossim\r\n testing_dsc | ossim_1.8.20.3+ds-4~xenial0                  | Source  | ossim\r\n testing_dsc | ossimplanet_1.81-1~svn22135~ubuntu9          | Source  | ossimplanet\r\n testing_dsc | ossimplanetqt_1.81-1~svn22135~ubuntu5        | Source  | ossimplanetqt\r\n testing_dsc | ossimplanetqt_1.81-1~svn22135~ubuntu6        | Source  | ossimplanetqt\r\n testing_dsc | ossimpredator_1.81-1svn21539~precise11       | Source  | ossimpredator\r\n testing_dsc | ossim-wms_1.81-1~1svn22135~ubuntu3           | Source  | ossim-wms\r\n testing_dsc | pgrouting_2.1.0-2~xenial0                    | Source  | pgrouting\r\n testing_dsc | postgis_2.2.1+dfsg-2~xenial1                 | Source  | postgis\r\n testing_dsc | postgis_2.2.1+dfsg-3~xenial0                 | Source  | postgis\r\n testing_dsc | pycsw_1.10.4+dfsg-2~xenial0                  | Source  | pycsw\r\n testing_dsc | qgis_2.14.1+dfsg-3~xenial0                   | Source  | qgis\r\n testing_dsc | rasterio_0.31.0-2build2~xenial0              | Source  | rasterio\r\n testing_dsc | saga_2.2.7+dfsg-0~ubuntugis~xenial1          | Source  | saga\r\n testing_dsc | spatialite_4.1.1-5ubuntu2                    | Source  | spatialite\r\n testing_dsc | spatialite-tools_4.1.1-3~trusty0             | Source  | spatialite-tools\r\n testing_dsc | tinyows_1.1.1-3~xenial0                      | Source  | tinyows\r\n(43 rows)\r\n\r\n<\/pre>\n
—<\/p>\n
All maintainers listed in PPA stable, by number of packages maintained:<\/p>\n
dbb=# select count(*),dsc_val from dsc_all \r\n    where ppa_name = 'stable_dsc' and dsc_key = 'Maintainer' \r\n    group by dsc_val   order by count(*) desc;\r\n-------+----------------------------------------------------------------------\r\n    47 | Debian GIS Project \r\n    11 | Angelos Tzotsos \r\n     7 | OTB Team \r\n     6 | Rashad M \r\n     4 | Ubuntu Developers \r\n     2 | QGIS developers \r\n     2 | Loic Dachary (OuoU) \r\n     2 | Jerome Villeneuve Larouche \r\n     1 | Kubuntu Developers \r\n     1 | Quantum GIS developers \r\n     1 | wxWidgets Maintainers \r\n     1 | Ubuntu GIS Project \r\n     1 | Debian Med Packaging Team \r\n     1 | Tom Payne \r\n     1 | David Paleino \r\n     1 | Alan Boudreault \r\n     1 | Mapnik Developers \r\n     1 | Debian Games Team \r\n     1 | The Mer  \r\n     1 | UbuntuGIS \r\n     1 | Python Applications Packaging Team \r\n     1 | Frederik Ramm \r\n     1 | Debian OpenStreetMap Team \r\n     1 | Alexandre Viau \r\n     1 | Rashad M \r\n     1 | Pirmin Kalberer \r\n     1 | Stephan Holl \r\n     1 | Ingo Berg \r\n     1 | Debian Java Maintainers \r\n     1 | Bart Martens \r\n     1 | Debian PhotoTools Maintainers \r\n     1 | Johan Van de Wauw \r\n\r\n<\/pre>\n
—<\/p>\n
The contents of all .dsc key-value pairs, for all PPAs, where the source control name matches ‘cdf’<\/p>\n
dbb=# select * from dsc_all where dsc_name ~ 'cdf' order by ppa_name, dsc_name, dsc_key;\r\n  ppa_name     dsc_name                         dsc_key             dsc_val\r\n+-----------+--------------------------------+-------------------+---------------------------\r\n stable_dsc | python-netcdf4_1.1.0-0~trusty1 | Architecture      | any\r\n stable_dsc | python-netcdf4_1.1.0-0~trusty1 | Binary            | python-netcdf4\r\n stable_dsc | python-netcdf4_1.1.0-0~trusty1 | Build-Depends     | debhelper (>= 9), dpkg-dev (>= 1.16.1~), python-all-dev, libnetcdf-dev (>= 4.1.1~), python-numpy (>= 1:1.6.1~), zlib1g-dev, libhdf5-serial-dev (>= 1.8.4~) | libhdf5-dev (>= 1.8.4~), netcdf-bin\r\n stable_dsc | python-netcdf4_1.1.0-0~trusty1 | Checksums-Sha1    | \r\n stable_dsc | python-netcdf4_1.1.0-0~trusty1 | Checksums-Sha256  | \r\n stable_dsc | python-netcdf4_1.1.0-0~trusty1 | Files             | \r\n stable_dsc | python-netcdf4_1.1.0-0~trusty1 | Format            | 3.0 (quilt)\r\n stable_dsc | python-netcdf4_1.1.0-0~trusty1 | Hash              | SHA1\r\n stable_dsc | python-netcdf4_1.1.0-0~trusty1 | Homepage          | http:\/\/code.google.com\/p\/netcdf4-python\/\r\n stable_dsc | python-netcdf4_1.1.0-0~trusty1 | Maintainer        | The Mer -rememberthemer @gmail.com-\r\n stable_dsc | python-netcdf4_1.1.0-0~trusty1 | Package-List      | \r\n stable_dsc | python-netcdf4_1.1.0-0~trusty1 | Source            | python-netcdf4\r\n stable_dsc | python-netcdf4_1.1.0-0~trusty1 | Standards-Version | 3.9.3\r\n stable_dsc | python-netcdf4_1.1.0-0~trusty1 | Version           | 1.1.0-0~trusty1\r\n stable_dsc | python-netcdf4_1.1.0-0~trusty1 | Version           | GnuPG v1\r\n\r\n<\/pre>\n
—<\/p>\n
A count of how many source packages in PPA stable<\/code> depend on what component:<\/p>\n
dbb=# select bdepends, count(*) from dsc_bdepends where ppa_name = 'stable_dsc' \r\n        group by bdepends   order by count(*) desc;\r\n\r\n                   bdepends                   | count \r\n----------------------------------------------+-------\r\n debhelper                                    |   105\r\n cmake                                        |    36\r\n libproj-dev                                  |    32\r\n zlib1g-dev                                   |    29\r\n libgdal-dev                                  |    28\r\n python-all-dev                               |    26\r\n libgeos-dev                                  |    26\r\n python-all                                   |    24\r\n autotools-dev                                |    24\r\n dpkg-dev                                     |    24\r\n python-setuptools                            |    23\r\n libexpat1-dev                                |    22\r\n libjpeg-dev                                  |    19\r\n libcurl4-gnutls-dev                          |    19\r\n libsqlite3-dev                               |    18\r\n libpng-dev                                   |    17\r\n libpq-dev                                    |    16\r\n dh-python                                    |    15\r\n libfcgi-dev                                  |    14\r\n libxml2-dev                                  |    14\r\n...\r\n python-numpy                                 |    12\r\n doxygen                                      |    12\r\n...\r\n python-scipy                                 |     2\r\n libqt4-opengl                                |     2\r\n libqhull-dev                                 |     2\r\n...\r\n python3-all-dbg                              |     1\r\n spawn-fcgi                                   |     1\r\n libossim-wms                                 |     1\r\n(396 rows)\r\n\r\n<\/pre>\n
Java-related projects:<\/em><\/p>\n
\"base10_java.dot\"<\/a><\/p>\n
Apache2, python, postgis and others:<\/em><\/p>\n
\"base10t.dot\"<\/a><\/p>\n
checkversion.py<\/code><\/p>\n
import netCDF4, sys, numpy\r\nsys.stdout.write('netcdf4-python version: %s\\n'%netCDF4.__version__)\r\nsys.stdout.write('HDF5 lib version:       %s\\n'%netCDF4.__hdf5libversion__)\r\nsys.stdout.write('netcdf lib version:     %s\\n'%netCDF4.__netcdf4libversion__)\r\nsys.stdout.write('numpy version           %s\\n' % numpy.__version__)\r\n<\/pre>\n
https:\/\/tracker.debian.org\/pkg\/netcdf4-python
\nPKG-INFO<\/code><\/p>\n
Metadata-Version: 1.0\r\nName: netCDF4\r\nVersion: 0.5\r\nSummary: netCDF version 4 has many features not found in earlier versions of the library, such as hierarchical groups, zlib compression, multiple unlimited dimensions, and new data types.  It is implemented on top of HDF5.  This module implements many of the new features, and can read netCDF files created with older versions of the library.  The API is modelled after Scientific.IO.NetCDF, and should be familiar to users of that module\r\nHome-page: http:\/\/www.cdc.noaa.gov\/people\/jeffrey.s.whitaker\/python\/netCDF4.html\r\nAuthor: Jeff Whitaker\r\nAuthor-email: jeffrey.s.whitaker@noaa.gov\r\nLicense: ['OSI Approved']\r\nDownload-URL: http:\/\/www.cdc.noaa.gov\/people\/jeffrey.s.whitaker\/python\/netCDF4-0.4.4.tar.gz\r\nDescription: UNKNOWN\r\nPlatform: any\r\nClassifier: Development Status :: 3 - Alpha\r\nClassifier: Intended Audience :: Science\/Research\r\nClassifier: License :: OSI Approved\r\nClassifier: Topic :: Software Development :: Libraries :: Python Modules\r\nClassifier: Topic :: System :: Archiving :: Compression\r\nClassifier: Operating System :: OS Independent\r\n<\/pre>\n
https:\/\/tracker.debian.org\/pkg\/hdf5<\/p>\n","protected":false},"excerpt":{"rendered":"
by Brian M Hamlin, OSGeo California Chapter https:\/\/firms.modaps.eosdis.nasa.gov\/usfs\/ https:\/\/earthdata.nasa.gov\/learn\/articles\/usfs-firms-us-canada https:\/\/earthdata.nasa.gov\/earth-observation-data\/near-real-time\/firms https:\/\/gwis.jrc.ec.europa.eu\/about-gwis\/technical-background\/active-fire-detection https:\/\/wiki.earthdata.nasa.gov\/pages\/viewrecentblogposts.action?key=FIRMS https:\/\/firms.modaps.eosdis.nasa.gov\/usfs\/map\/#d:24hrs;@-122.2,38.5,10z https:\/\/earthdata.nasa.gov\/collaborate\/open-data-services-and-software\/data-information-policy\/data-levels   LANCE Citation, Acknowledgements and Disclaimer\u00a0 NASA promotes the full and open sharing of all data with the research and applications communities, private industry, academia, and the general public. Read NASA’s\u00a0Data and Information Policy. If you provide NASA’s Land, Atmosphere Near […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"_links":{"self":[{"href":"http:\/\/blog.light42.com\/wordpress\/index.php?rest_route=\/wp\/v2\/pages\/8"}],"collection":[{"href":"http:\/\/blog.light42.com\/wordpress\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/blog.light42.com\/wordpress\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/blog.light42.com\/wordpress\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/blog.light42.com\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=8"}],"version-history":[{"count":139,"href":"http:\/\/blog.light42.com\/wordpress\/index.php?rest_route=\/wp\/v2\/pages\/8\/revisions"}],"predecessor-version":[{"id":3763,"href":"http:\/\/blog.light42.com\/wordpress\/index.php?rest_route=\/wp\/v2\/pages\/8\/revisions\/3763"}],"wp:attachment":[{"href":"http:\/\/blog.light42.com\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=8"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}