Hi,
I've been having some issues getting the WCS driver to behave correctly.
However, I am new to GIS so it's very likely I'm doing something wrong.
When performing a request on a coverage whose CRS is EPSG:4326, if the
projWin contains a negative longitude, the driver requests instead the
covera
Hi! Is it possible to cache server responds using WCS driver in GDAL? Like in
WMS driver ...
Thanks.
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/ma
Ari Jolma kirjoitti 14.11.2017 klo 17:41:
I've got very close to being able to get valid data (visual comparison
in QGIS) from various server types and WCS versions.
I've documented the results here:
https://trac.osgeo.org/gdal/wiki/WCS%2Binteroperability
It seems that I need eight option fl
I've got very close to being able to get valid data (visual comparison
in QGIS) from various server types and WCS versions.
I've documented the results here:
https://trac.osgeo.org/gdal/wiki/WCS%2Binteroperability
It seems that I need eight option flags to cover all cases. Mostly the
problem
Even Rouault kirjoitti 30.10.2017 klo 22:41:
On lundi 30 octobre 2017 10:54:56 CET Ari Jolma wrote:
>
> XML namespaces can be declared in any element and then they are in
> effect in that element and in all of its children unless they override
> the namespace declarations.
>
Yes, XML can
On lundi 30 octobre 2017 10:54:56 CET Ari Jolma wrote:
> Ari Jolma kirjoitti 24.10.2017 klo 17:07:
> > Whoa! How hard can XML be? I have a real Capabilities document (from
> > well known company) which defines *both* default and ows namespace to
> > http://www.opengis.net/ows/2.0.
>
> Seems that X
Ari Jolma kirjoitti 24.10.2017 klo 17:07:
Whoa! How hard can XML be? I have a real Capabilities document (from
well known company) which defines *both* default and ows namespace to
http://www.opengis.net/ows/2.0.
Seems that XML is actually much harder than that :)
XML namespaces can be de
Even Rouault kirjoitti 29.10.2017 klo 12:49:
> So, treat lat,lon and north,east always as exceptions. And in this case
> add an option to make that exception when appropriate and when writing
> the BoundingBox into the request. (But not when reading GridOrigin.
> However, I still have to see
> So, treat lat,lon and north,east always as exceptions. And in this case
> add an option to make that exception when appropriate and when writing
> the BoundingBox into the request. (But not when reading GridOrigin.
> However, I still have to see what other servers say.)
I'm not sure what you exa
Even Rouault kirjoitti 29.10.2017 klo 11:52:
The "tradition" in GDAL drivers such as GML, WFS is to strip AXIS from
the CRS WKT exposed when they are in the "annoying" lat,long and
northing,easting,
From the GML driver:
{{{
if (poSRS != NULL && m_bInvertAxisOrderIfLatLong &&
GML_IsSRSLatL
Hi Ari,
>
> I'd like to have your comment on this.
>
> Ari Jolma kirjoitti 28.10.2017 klo 17:39:
> > Reading MapServer code, it seems to be based on the idea that x,y is
> > always east,north and when it writes BoundingBox, it swaps x and y if
> > the projection is inverted (like 4326). It does
jratike80 kirjoitti 28.10.2017 klo 13:10:
Ari Jolma-2 wrote
The case of GeoServer is also strange
https://msp.smartsea.fmi.fi/geoserver/wcs?SERVICE=WCS&VERSION=1.1.1&REQUEST=GetCoverage&IDENTIFIER=smartsea%3Aeusm2016&FORMAT=image%2Ftiff&BOUNDINGBOX=61610,7303970,61630,7303990,urn:ogc:def:crs:EPS
FYI, this is one of the shortcomings of WCS 1.x. Remedied in WCS 2.
-Peter
On 10/28/2017 04:39 PM, Ari Jolma wrote:
> jratike80 kirjoitti 28.10.2017 klo 13:10:
>
>> Ari Jolma-2 wrote
>>>
>>> For example this request to a MapServer WCS (I'm not responsible for
>>> that server so don't know much a
jratike80 kirjoitti 28.10.2017 klo 13:10:
Ari Jolma-2 wrote
For example this request to a MapServer WCS (I'm not responsible for
that server so don't know much about it), which is generated in the
driver during a DescribeCoverage for the coverage,
http://194.66.252.155/cgi-bin/BGS_EMODnet_bat
Ari Jolma-2 wrote
> Ari Jolma kirjoitti 27.10.2017 klo 19:38:
>>
>>
>> * I'm testing against existing ArcGIS, GeoServer and MapServer servers
>> on the net
>
> Version 1.0.0 seems to be usually understandable/ok but strangeness
> begins with 1.1
>
> For example this request to a MapServer WCS (
Ari Jolma kirjoitti 27.10.2017 klo 19:38:
* I'm testing against existing ArcGIS, GeoServer and MapServer servers
on the net
Version 1.0.0 seems to be usually understandable/ok but strangeness
begins with 1.1
For example this request to a MapServer WCS (I'm not responsible for
that server
cool work! Once released, you may want to list yourself here:
https://en.wikipedia.org/wiki/Web_Coverage_Service .
FYI, GDAL is already listed here:
http://external.opengeospatial.org/twiki_public/CoveragesDWG/WebHome#Known_Implementations
-Peter
On 10/27/2017 06:38 PM, Ari Jolma wrote:
> I hav
I have my initial work here:
https://github.com/ajolma/gdal/commit/2335bc6222e8d8df7e4b5fcfe21a825c727ad549
what I've done so far:
* Recognize WCS:URL format
* Parse GetCapabilities XML (versions 1.0.0 to 2.0.1)
* Simple cache for various XML-files (PAM, WCS_GDAL, Capabilities,
DescribeCover
Even Rouault kirjoitti 24.10.2017 klo 20:23:
On mardi 24 octobre 2017 17:07:51 CEST Ari Jolma wrote:
> Whoa! How hard can XML be? I have a real Capabilities document (from
> well known company) which defines *both* default and ows namespace to
> http://www.opengis.net/ows/2.0.
>
> Thus, to
On mardi 24 octobre 2017 17:07:51 CEST Ari Jolma wrote:
> Whoa! How hard can XML be? I have a real Capabilities document (from
> well known company) which defines *both* default and ows namespace to
> http://www.opengis.net/ows/2.0.
>
> Thus, to be sure, I need to look for *both* ows:ServiceIdenti
FWIW, OWS Common 2.0 is known to be flawed in several aspects (we spec writers
suffered dearly - from the resources it needed to discover, to finding
workarounds in the spec, to explaining to people...). Trust me, the namespace
issue is just a minor one in comparison... OGC is looking to get someth
Whoa! How hard can XML be? I have a real Capabilities document (from
well known company) which defines *both* default and ows namespace to
http://www.opengis.net/ows/2.0.
Thus, to be sure, I need to look for *both* ows:ServiceIdentification
and ServiceIdentification. Or maybe loop through all
Even Rouault kirjoitti 24.10.2017 klo 13:28:
> The netcdf files I looked at through the GDAL driver had time and/or
> depth offered as different gdal layers, and offered different variables
> (i.e. different coverages) as subdatasets.
Yes, although in the WCS case, a coverage can have several
> The netcdf files I looked at through the GDAL driver had time and/or
> depth offered as different gdal layers, and offered different variables
> (i.e. different coverages) as subdatasets.
Yes, although in the WCS case, a coverage can have several bands, and thus
using the band
mechanism to ref
On 10/23/2017 08:47 PM, Even Rouault wrote:
> On lundi 23 octobre 2017 18:31:58 CEST Ari Jolma wrote:
>> Peter Baumann kirjoitti 23.10.2017 klo 18:01:
>>> Hi all,
>>>
>>> splendid idea! Anybody who feels like working on WCS 2 support, feel free
>>> to contact me or my group for any sort of explan
> Is there any reason not to switch to libxml2 from minixml?
>
> I see only GMLAS driver uses libxml2 currently
Ah, yes indirectly when it validates the data/gmlasconf.xml file against
data/gmlasconf.xsd,
since CPLValidateXML() uses libxml2 underneath to do that (it could actually
have an
alt
Even Rouault kirjoitti 23.10.2017 klo 13:19:
Hi Ari,
It seems to me that the WCS driver could benefit from some love.
That would be a good initiative!
In the wished feature list, I could add:
* improve test coverage, which is really low currently:
https://rawgit.com/rouault/gdalautotest-cove
On 10/23/2017 05:31 PM, Ari Jolma wrote:
>
>
> Peter Baumann kirjoitti 23.10.2017 klo 18:01:
>> Hi all,
>>
>> splendid idea! Anybody who feels like working on WCS 2 support, feel free to
>> contact me or my group for any sort of explanations sought (I am the spec
>> writer
>> of the coverages, a
On lundi 23 octobre 2017 18:31:58 CEST Ari Jolma wrote:
> Peter Baumann kirjoitti 23.10.2017 klo 18:01:
> > Hi all,
> >
> > splendid idea! Anybody who feels like working on WCS 2 support, feel free
> > to contact me or my group for any sort of explanations sought (I am the
> > spec writer of the c
On 10/23/2017 05:20 PM, Ari Jolma wrote:
> jratike80 kirjoitti 23.10.2017 klo 17:23:
>> Ari Jolma-2 wrote
>>> I could begin with the gdalinfo WCS:... to list the subdatasets. I guess
>>> that's enough for some time.
>> My personal opinion is that developing anything for WCS 1.x versions is
>> was
On 10/23/2017 04:23 PM, jratike80 wrote:
> Ari Jolma-2 wrote
>> I could begin with the gdalinfo WCS:... to list the subdatasets. I guess
>> that's enough for some time.
> My personal opinion is that developing anything for WCS 1.x versions is
> waste of time. WCS 2.x is much better standard and
Peter Baumann kirjoitti 23.10.2017 klo 18:01:
Hi all,
splendid idea! Anybody who feels like working on WCS 2 support, feel free to
contact me or my group for any sort of explanations sought (I am the spec writer
of the coverages, admittedly). Note that the Coverage Implementation Schema
(CIS)
jratike80 kirjoitti 23.10.2017 klo 17:23:
Ari Jolma-2 wrote
I could begin with the gdalinfo WCS:... to list the subdatasets. I guess
that's enough for some time.
My personal opinion is that developing anything for WCS 1.x versions is
waste of time. WCS 2.x is much better standard and it is quit
Hi all,
splendid idea! Anybody who feels like working on WCS 2 support, feel free to
contact me or my group for any sort of explanations sought (I am the spec writer
of the coverages, admittedly). Note that the Coverage Implementation Schema
(CIS) 1.1 is out. Maybe this is a good starter:
http://
Ari Jolma-2 wrote
> I could begin with the gdalinfo WCS:... to list the subdatasets. I guess
> that's enough for some time.
My personal opinion is that developing anything for WCS 1.x versions is
waste of time. WCS 2.x is much better standard and it is quite a lot
different than 1.x.
-Jukka Rahk
Even Rouault kirjoitti 23.10.2017 klo 13:19:
Hi Ari,
It seems to me that the WCS driver could benefit from some love.
That would be a good initiative!
I could begin with the gdalinfo WCS:... to list the subdatasets. I guess
that's enough for some time.
In the wished feature list, I coul
Hi Ari,
> It seems to me that the WCS driver could benefit from some love.
That would be a good initiative!
In the wished feature list, I could add:
* improve test coverage, which is really low currently:
https://rawgit.com/rouault/gdalautotest-coverage-results/master/coverage_html/frmts/wcs/wc
It seems to me that the WCS driver could benefit from some love.
Is anybody working on it / planning to work on it?
I think simply a support for
gdalinfo WCS:...
to get a list of offered coverages would be useful to start with.
Ari
___
gdal-dev ma
Le vendredi 19 août 2011 23:46:16, Jachym Cepicky a écrit :
Looks like you are running into http://trac.osgeo.org/gdal/ticket/4118
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
Hi,
using gdal 1.9 (trunk)
I try to read data from this service (with following configuration):
http://motherlode.ucar.edu:8080/thredds/wcs/fmrc/NCEP/DGEX/Alaska_12km/NCEP-DGEX-Alaska_12km_best.ncd?
Geopotential_height
gdalinfo says:
ERROR 1: HTTP error code : 400
ERROR 1: BBOX
[-2382
Hi list,
on that occasion it may be noteworthy that OGC is about to publish a Request for
Comments (RFC) on the
10-140 OGC Web Coverage Service - Earth Observation Application Profile
nicknamed EO-WCS. This specification, which has been tasked by ESA, specializes
WCS for use in remote sens
Evan, thanks for answer
it works!!
Thanks
Jachym
2011/6/26 Even Rouault :
> Le dimanche 26 juin 2011 00:03:55, Jachym Cepicky a écrit :
>> Hi,
>>
>> using Python, gdal 1.8.0, Ubuntu
>>
>> I need to access some Temporal information about available WCS layer
>
> Jachym,
>
> Frank has added supp
Le dimanche 26 juin 2011 00:03:55, Jachym Cepicky a écrit :
> Hi,
>
> using Python, gdal 1.8.0, Ubuntu
>
> I need to access some Temporal information about available WCS layer
Jachym,
Frank has added support for WCS temporal information in GDAL trunk just a few
days ago. So it is not available
Hi,
using Python, gdal 1.8.0, Ubuntu
I need to access some Temporal information about available WCS layer
http://www.gdal.org/frmt_wcs.html says at the end, that
"Each time position available for the coverage will be treated as a subdataset."
I have following service description file (with ser
44 matches
Mail list logo
