version=1.1.1=1;
tells me details about this coverage which seems to be huge. Now that is the
src_dataset string to be used in gdal_translate.
Ari
Odd Ragnar Lydersen kirjoitti 10.10.2018 klo 14:11:
> I have investigated some more now, and I've found that the problem is perhaps
> the way I
nal Message-
From: Peter Baumann
Sent: tirsdag 9. oktober 2018 15:10
To: jratike80 ; gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev] WCS: Bug in WCSDataset110::GetCoverageRequest()
On 09.10.2018 15:06, jratike80 wrote:
> Odd Ragnar Lydersen wrote
>> I think there is a bug in WCS
1) DescribeCoverage for version 1.0.0 (It's working fine if I use version=1.1.x)
static std::string wcsDescribeCoverage =
"WCS:https://wms.geonorge.no/skwms1/wcs.hoyde-dtm1_32?SERVICE=WCS=DescribeCoverage=dtm1_32=1.0.0;;
static const char* pOptionOpenOptions[] =
I think there is a bug in WCSDataset110::GetCoverageRequest()
At line 178: "=%s=GetCoverage=%s"
Should be : "=%s=GetCoverage=%s"
At least that fixes my problem, and I can get one step further in my effort to
use the wcs driver, using C++ API, on Windows.
>Odd-Ragnar<
Hi, I'm struggling to understand the new setup for WCS.
In the documentation it says:
- If the URL does not contain a coverage name, the driver attempts to fetch the
capabilities document from the server, parse it, and show the resulting
metadata to the user.
How is this done using the C++
. The same applies for the DescribeFeatureType request issued to
discover the field definition of each layer."
Am I missing something here, or is this a bug?
Is there another way to select a subset of feature attributes, and the feature
geometry?
Odd-Ragnar Ly
n.roua...@spatialys.com]
Sendt: onsdag 19. oktober 2016 15.55
Til: Odd Ragnar Lydersen <odd-ragnar.lyder...@powel.no>
Kopi: gdal-dev@lists.osgeo.org
Emne: Re: SV: [gdal-dev] WFS driver bug2 - MAXFEATURES not working
Le mercredi 19 octobre 2016 15:17:52, Odd Ragnar Lydersen a écrit :
> Now I h
..@spatialys.com]
Sendt: torsdag 29. september 2016 11.20
Til: gdal-dev@lists.osgeo.org
Kopi: Odd Ragnar Lydersen <odd-ragnar.lyder...@powel.no>
Emne: Re: [gdal-dev] WFS driver bug2 - MAXFEATURES not working
Le jeudi 29 septembre 2016 10:06:12, Odd Ragnar Lydersen a écrit :
> So I hav
ys.com]
Sendt: torsdag 29. september 2016 11.20
Til: gdal-dev@lists.osgeo.org
Kopi: Odd Ragnar Lydersen <odd-ragnar.lyder...@powel.no>
Emne: Re: [gdal-dev] WFS driver bug2 - MAXFEATURES not working
Le jeudi 29 septembre 2016 10:06:12, Odd Ragnar Lydersen a écrit :
> So I have tried to
d just use, SetSpatialFilterRect(),
to restrain the number of features returned from a layer.
>Odd-Ragnar<
Fra: Odd Ragnar Lydersen [mailto:odd-ragnar.lyder...@powel.no]
Sendt: onsdag 28. september 2016 14.10
Til: gdal-dev@lists.osgeo.org
Emne: [gdal-dev] WFS driver bug2 - MAXFEATURES not working
service, could it be related to my "WFS driver
bug1"?
Med vennlig hilsen
Odd-Ragnar Lydersen
System Developer
Powel AS Storgata 27B, Pb 369, N-4349 Bryne, NORWAY
Email: odd-ragnar.lyder...@powel.no<mailto:odd-ragnar.lyder...@powel.no>
www.powel.no<http://www.powel.com/
to read features from the
service.
But why are the calls in the GML driver, (on behalf of the WFS driver), made
without UserPwd in papszOptions parameter?
I have attached some output from the calls tack, so you can see which calls are
causing this behaviour.
Best regards
Odd-Ragnar Lydersen
a call to CPLHTTPResult *CPLHTTPFetch( const char
*pszURL, char **papszOptions ) , without any content in **papszOptions.
In other calls I can see that the UserPwd is sendt in the **papszOptions
variable.
Odd-Ragnar Lydersen
System Developer
Email: odd-ragnar.lyder...@powel.no<mailto
This is probably a stupid question, but I'm wondering if the WCS driver is
missing something.
1) I have used the WFS driver, and the description xml file, which caches the
GetCapabilitis result, so that I can get info from that file later.
2) The corresponding description xml file for the WCS
Thanks for the response.
I think I will conclude the same as you, and report back to the server
developers that this is a bad idea.
Odd-Ragnar
-Original Message-
From: Rahkonen Jukka [mailto:jukka.rahko...@mmmtike.fi]
Sent: 8. oktober 2012 22:22
To: gdal-dev@lists.osgeo.org
Subject:
The problem is OGRSQL (ogr_gensql.cpp) which adds the string FIELD_%d when it
doesn't know how to handle column names with dot character in them. Because the
dot character is a special/reserved character it needs to be enclosed in '',
, ``, [], ..., all depending on which dialect is used (MS
I see you have been busy discussing how to handle column names which contain
dot .
My problem is that I can't get any reasonable values from the query I make,
whether I use str1.str2 or 'str1.str2' in my expression.
In my C++ code this is:
a) const char *sSqlQuery = SELECT \str1.str2\ FROM
Is it possible to make OGRDataSource:: ExecuteSQL() to work with a column name
containing .?
Here is an example:
select column.name.one, column.name.two from 'wfs:layerName'
I have tried to enclose the column name in [] brackets, but that was invalid as
well.
Any ideas on how to get around
According to the definition WFS_TurnSQLFilterToOGCFilter() should have 6
arguments, but this one place it has 7.
I guess the definition is correct, and I have deleted one of the arguments on
my computer.
In addition I had to make one more adjustment to make gdal compile, I had to
comment out
Yes, the server is accessible to the outside world.
But first I must say, that we have modified our server to send the correct gml
document.
The problem was that the server only got the text/xml part specified by the
OutputFormat parameter, and not the subtype=gml/3.1.1 part, so our server
When I call myLayer-GetNextFeature(), I get an exception that tells me the
format in request is not supported.
Then I tried to ad outputformat=text/xml; subtype=gml/3.1.1 to
myWfsDriver-Open() string, and still I get the exception.
I guess my question is this:
How do I specify the
21 matches
Mail list logo
