<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
span.Shkpostityyli23
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 2.0cm 70.85pt 2.0cm;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="FI" link="#0563C1" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Hi,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Even Rouault wrote:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">> One option to avoid both issues would be for the service to publish
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">> DescribedBy links at the collection level that would point to a XML
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">> schema (using a GML Simple Feature schema profile, such as the one
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">> understood by the GML driver) or a JSON schema (not "too" complicated too).
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">> Both are handled by the driver.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">We added JSON schema and ogrinfo seems to read it, but it still wants to read one page of data:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">ogrinfo OAPIF:http://some.internal.service/features/collections/PalstanSijaintitiedot/ -al -so -oo PAGE_SIZE=10000 -nocount -noextent -nogeomtype --debug on<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">HTTP: Fetch(http://</span><span lang="EN-US">
</span><span lang="EN-US">some.internal.service /features/collections/PalstanSijaintitiedot/schema)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">HTTP: These HTTP headers were set: Accept: application/schema+json<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">OAPIF: Using JSON schema<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">HTTP: Fetch(http://</span><span lang="EN-US">
</span><span lang="EN-US">some.internal.service /features/collections/PalstanSijaintitiedot/items?f=json&limit=10000)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I wonder if there is still something in ogrinfo that I cannot turn off and what triggers the need to read some features, perhaps the coordinate system.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">-Jukka Rahkonen-<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</body>
</html>