Search results
From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
Page title matches
- <div style="font-size: 24pt;line-height: 100%">'''Volume 1: Data Model and Serialized Representation'''</div> <table border=1 width="85%">145 KB (22,480 words) - 22:53, 5 November 2021
- 29 bytes (4 words) - 22:21, 10 April 2019
- ; b[1<nowiki>:</nowiki>4] : Slice b so that only elements 1 through 4 are returned. Since b does not use a shared dim the special prope ...ut because a local slicing operation was performed, c is returned with dim 1 as an anonymous dim, not the sdim 'd'24 KB (4,077 words) - 22:09, 2 December 2013
- '''Initial Draft''': 1/1/16 '''Revised''': 1/16/1611 KB (1,881 words) - 22:34, 19 January 2016
Page text matches
- ...owiki>http://.../thredds/dodsC/hfrnet/agg/6km_expr_{}{let deq1ubar=u[d=1,l=1:24@ave]}</nowiki> : <nowiki>?avg(u[1,1:24])</nowiki>4 KB (578 words) - 19:48, 13 April 2012
- # [[DAP4: Specification Volume 1 | Volume 1: Data Model, Persistent Representation, and Constraints]] #* [[DAP4: Specification Volume 1 Deltas]]581 bytes (67 words) - 18:16, 15 August 2014
- for the boundary. Using, for example, the Boyer-Moore [1] (1) --<boundary>2 KB (344 words) - 18:11, 24 August 2012
- ...e some simple guidelines for prioritizing bugs on a scale of 1 to 5, where 1 is the lowest priority and 5 is the highest: ;1 Lowest:682 bytes (117 words) - 20:49, 15 March 2016
- └─xvda1 202:1 0 8G 0 part / [bash]# '''growpart /dev/xdva 1'''2 KB (227 words) - 21:44, 10 April 2017
- method 1: ...s buffer will destroy and create a new one to store new content. So method 1 is better than method 2? Is my understanding correct?1 KB (204 words) - 18:45, 16 August 2023
- <pre>ST[1:7]</pre> array dimensions such as A[1:10][31:2:40] ].2 KB (251 words) - 20:09, 1 May 2012
- These JSON dialects create 1:1 onto mappings to the native "binary" representation / source encoding.998 bytes (165 words) - 22:03, 19 July 2018
- ...ith requests for data in the DAP4 binary data encoding described in Volume 1 of the DAP4 specification <sup><nowiki>[</nowiki>[[#DAP4_Vol1|DAP4 Vol1]]<n <nowiki>[DAP4 Vol1]</nowiki> [[DAP4:_Specification_Volume_1|DAP4 Volume 1: Data Model, Persistent Representations, and Constraints]].3 KB (444 words) - 16:23, 22 April 2014
- <?xml version="1.0" encoding="UTF-8"?> ...ue>-7</value> <value>-5</value> <value>-3</value> <value>-1</value> <value>1</value> <value>3</value> <value>5</value> <value>7</value> <value>9</value>17 KB (1,519 words) - 00:59, 24 July 2013
- ;1 Jan :Final release of 1.5438 bytes (65 words) - 17:45, 29 April 2013
- 1 2 3 This lambda function use uses a 'capture.' The square braces at #1 name the captured variable. Its value is taken from the current environment2 KB (305 words) - 16:50, 16 October 2023
- :: version: m4 (GNU M4) 1.4.13 from source :: version: automake (GNU automake) 1.11 from source3 KB (495 words) - 23:28, 7 June 2012
- <center>Figure 1. Notional Domain Model over DAP4 Architecture</center> Figure 1 shows a notional architecture for using DAP4 as the basis for domain specif3 KB (455 words) - 20:55, 5 May 2012
- Namespace: http://xml.opendap.org/ns/bes/admin/1.0# <?xml version="1.0" encoding="UTF-8"?>8 KB (1,044 words) - 22:53, 6 October 2011
- <font color="red" size="+1">This is out of date: See [http://www.opendap.org/apac_workshop_vm The APAC :1. [http://www.opendap.org/support/bom_sdw/SDW_1r0_HyraxArchitecture.ppt Arch3 KB (436 words) - 23:32, 4 May 2012
- ...>1</sub> and M<sub>2</sub> for G<sub>1</sub> and a different set of M<sub>1</sub> and M<sub>2</sub> for G<sub>2</sub>. This only gets more complex whe We can go back to the old data model where each Grid (G<sub>1</sub> and G<sub>2</sub>, e.g.) is wrapped in its own scope. Problems with t8 KB (1,349 words) - 17:31, 13 April 2012
- === Basic Flow Stage 1=== === Basic Flow Stage 1===5 KB (868 words) - 16:05, 12 April 2012
- Content-Length: <<-1 or the size in bytes of the binary data>> <<XDR encoded binary data, part 1>>4 KB (668 words) - 20:36, 20 August 2012
- ...to the following: ''valgrind --quiet --trace-children=yes --error-exitcode=1 --dsymutil=yes --leak-check=yes"''. Here's what the options do: ...leak, etc., but instead returns the program's exit code. Setting this to ''1'' means that leaks will show up as errors when the tests are run by ''make'3 KB (484 words) - 23:20, 29 April 2013
- The Data response is a multipart MIME document that contains a N+1 parts for a response with N variables.708 bytes (101 words) - 20:54, 29 March 2012
- ...may have to use the loopback address to be able to do so: https://127.0.0.1/Shibboleth.sso/Status ShibRequestSetting requireSession 18 KB (1,102 words) - 23:51, 5 November 2014
- minmax_title 1 24 char 0 latitude 1 10 double 615 KB (2,042 words) - 23:30, 8 August 2012
- /* (1) */ As move operations are usually faster than copies, (1) is better than (0) if you pass a lot of temporaries. (2) is optimal in ter3 KB (423 words) - 23:26, 22 February 2024
- ::version: ltmain.sh (GNU libtool) 1.5.26 (1.1220.2.492 2008/01/30 06:40:56) :: version: automake (GNU automake) 1.10.14 KB (644 words) - 17:32, 29 April 2013
- '''Initial Draft''': 1/1/16 '''Revised''': 1/16/1611 KB (1,881 words) - 22:34, 19 January 2016
- Content-Length: -12 KB (243 words) - 18:19, 20 March 2013
- * SUSE-12.1 (64 bit) On SUSE 12.1 zipper does not have szip. I tried building szip from source and ran into t13 KB (1,779 words) - 03:50, 9 May 2012
- ...tware/netcdf/ncml/v2.2/Aggregation.html#joinExisting. Note that version 1.1.0 of the module does not support all features of joinExisting! Future vers ...n of joinExisting for version 1.2.x of the NcML Module, bundled with Hyrax 1.8. It is a limited feature set described below. Please see the Limitation11 KB (1,628 words) - 22:14, 18 November 2015
- # [[DAP4: Specification Volume 1 | Volume 1: Data Model, Persistent Representation, and Constraints]] #* [[DAP4: Specification Volume 1 Deltas]]13 KB (1,672 words) - 17:53, 4 January 2016
- ** [[File:1 Add the prefix var to project.png]] ** [[File:1 configure new make target.png]]6 KB (1,005 words) - 18:37, 24 March 2018
- [[Image:DAP4 DataDDX Design 2.png|400px|right|frame|'''Figure 1'''. Building the DataDDX with the OLFS making the initial and final headers [[Image:DAP4 DataDDX Design 1.png|right|thumb|'''Figure 2'''. This design would be good from the standpoi12 KB (1,799 words) - 18:18, 21 August 2011
- ?P1.P2[0:2:10].F[1:3][4:4] http://.../thredds/dodsC/hfrnet/agg/6km_expr_{}{let deq1ubar=u[d=1,l=1:24@ave]}6 KB (942 words) - 21:08, 26 February 2012
- ==== Example 1 - Choosing Variables and subsetting arrays ==== version, "<?xml version=\"1.0\" encoding=\"UTF-8\"?>6 KB (906 words) - 22:17, 11 February 2013
- ...toreFile="${user.home}/.keystore" keystorePass="changeit"'') to SSL HTTP/1.1 Connector entry. [[File:hai-Slide13.jpg|Log Viewer Controls 1]]10 KB (1,767 words) - 20:47, 25 September 2015
- ; ASPECT BALTO URL Reader Presentation - Part 1 Of the BALTO/ASPECT presentation. An overview of design and a brief discuss2 KB (283 words) - 00:51, 5 December 2020
- === Alternate Idea 1 ===7 KB (1,044 words) - 16:38, 12 June 2012
- This proposal suggests that DAP4 use a simple variation on the HTTP/1.1 chunked transmission scheme to serialize the data Part of the response docu #[http://www.w3.org/Protocols/rfc2616/rfc2616.html HTTP/1.1]5 KB (823 words) - 22:37, 4 September 2012
- ...n order to accommodate streaming, the length is allowed to have the value -1, which indicates that the length was unknown at the time the part was sent ...cording the length in bytes of the data part of the mime part. If this is -1, then the length is unknown and must be computed by the client. The {parthe13 KB (2,100 words) - 22:55, 8 May 2012
- In Hyrax 1.7: In Hyrax 1.6:1 KB (213 words) - 18:53, 18 March 2016
- <?xml version="1.0" encoding="UTF-8"?> ...<cf:Conventions rdf:datatype="http://www.w3.org/2001/XMLSchema#string">CF-1.0</cf:Conventions>22 KB (3,225 words) - 19:00, 6 February 2012
- <font size="+1" color="red">This is an old document that captures the starting point of th ...ort for various versions of the protocol (e.g., 2.0, 3.1, 3.2, ..., 4.0, 4.1, ...). A number of schemes to support this range of behaviors was discussed15 KB (2,578 words) - 19:11, 31 August 2012
- chunk-extension = chunk-size "x" 1*(chunk-ext-name [ "=" chunk-ext-val ] ";") [[Image:BES chunking 7 1.jpg]]15 KB (2,202 words) - 20:47, 19 December 2013
- ...paragraph). If the handler, as of version 3.10.x, is linked with netCDF 4.1.x or later, you will be able to read any netCDF file that fits the 'classic ...s of length one. Arrays of ''N'' characters in netCDF map to arrays of ''N-1'' Strings in DAP10 KB (1,640 words) - 19:13, 11 January 2012
- ...y version of the HDF5 API. The handler should be built/linked with version 1.8.x of the API. ...hexadecimal value of their ASCII code is used. For example, "Raster Image #1" becomes "Raster%20Image%20%231". These translations should be transparent6 KB (1,023 words) - 13:40, 4 October 2013
- http://<machine/<path>[_expr{#1}{#2}{#3}].<response_object>[?DAP2_constraint] The feature provided by #1 opens servers to working with non-local data. This is a known vulnerability18 KB (2,983 words) - 23:52, 17 September 2013
- <?xml version="1.0" encoding="UTF-8"?> <netcdf title="Sample Slice 1">15 KB (2,237 words) - 23:27, 8 July 2015
- : <tt> ?dap4.ce=n;a[3:1:100];k|x<=y|z=y</tt> : <font size="3"><code>?dap4.ce=u[25:1:1000][75:1:1000]|u>4.0|u<12.7&dap4.arraySelection=mask(0x00)</code></font>11 KB (1,841 words) - 21:03, 8 February 2014
- At the OPULS meeting in Boulder CO on 1-3 Oct 2012 we discussed how the concepts of the DAP2 constraint expressions ...u[:4:][:4:]'': every fourth element in both dimentsions; this would return 1/16^th of the array's data.22 KB (3,445 words) - 17:28, 22 May 2014
- ; [[Wiki_Testing/dintro | Chapter 1]] : contains an overview of the OPeNDAP FreeForm ND Data Handler software, 1 2 3 4 5 66 KB (994 words) - 01:21, 11 December 2014
