<div dir="ltr"><div>Hmm strange indeed!</div><div><br></div><div>Not sure what/where but still feels like there is a bug somewhere to me. Feel free to file your findings as an issue at <a href="https://github.com/MapServer/MapServer">https://github.com/MapServer/MapServer</a> and I (or someone else) will hopefully find some time to look into it.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Den tis 30 aug. 2022 kl 19:22 skrev Scott <<a href="mailto:public@postholer.com">public@postholer.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Thanks for the response Bjorn!<br>
<br>
Using this without DATA, still returns the same error:<br>
<br>
CONNECTIONTYPE OGR<br>
CONNECTION "/vsis3/bucket/path/traceseg.fgb"<br>
<br>
Ogrinfo works fine, COG works fine, all aws keys/pw set.<br>
<br>
.fgb with it's range requests is ideally suited for cloud <br>
storage/retrieval, like COG for raster. COG/.fgb are the perfect pair <br>
for cloud raster/vector data sources. Yet, I can't get .fgb to work <br>
within a .map file. Ugh!<br>
<br>
v8 rc1 ms_error message:<br>
[Tue Aug 30 09:53:20 2022].395601 msOGRFileOpen(): OGR error. Open <br>
failed for OGR connection in layer `traceseg'. File not found or <br>
unsupported format. Check server logs.<br>
[Tue Aug 30 09:53:20 2022].395617 Open failed for OGR connection in <br>
layer `traceseg'.<br>
<br>
[Tue Aug 30 09:53:20 2022].395625 msDrawMap(): Image handling error. <br>
Failed to draw layer named 'traceseg'.<br>
<br>
Thanks again!<br>
<br>
<br>
On 8/30/22 09:42, Björn Harrtell wrote:<br>
> Hi Scott,<br>
> <br>
> The OGR method should work but it might be confusing about naming of <br>
> file vs specified in DATA. Does it work if you omit the DATA parameter <br>
> or set it to the same name as the file name (possibly without extension)?<br>
> <br>
> The new native FlatGeobuf driver ("CONNECTIONTYPE flatgeobuf") only <br>
> supports local file access. While it could possibly be extended to <br>
> support access via HTTP/HTTPS that would be non-trivial work and I'm not <br>
> sure it's worth it because the overhead of going through OGR is likely <br>
> insignificant when you have network I/O involved.<br>
> <br>
> PS. I don't quite agree that it's the whole point of the format. :)<br>
> <br>
> Den tis 30 aug. 2022 kl 16:49 skrev Scott <<a href="mailto:public@postholer.com" target="_blank">public@postholer.com</a> <br>
> <mailto:<a href="mailto:public@postholer.com" target="_blank">public@postholer.com</a>>>:<br>
> <br>
> Using mapserver 7.6 or 8rc1 I've been unable to serve .fgb from an S3<br>
> bucket. Local disk works fine as does ogrinfo on S3 .fgb. COG raster<br>
> data works fine off S3.<br>
> <br>
> Accessing .fgb from cloud storage seems to be the whole point of the<br>
> .fgb format. So, I'm very curious if I'm doing something wrong or is it<br>
> by design.<br>
> <br>
> <br>
> Map file configs:<br>
> <br>
> v8rc1:<br>
> CONNECTIONTYPE flatgeobuf<br>
> DATA "/vsis3/bucket/path/data.fgb"<br>
> <br>
> v7.6.4<br>
> CONNECTIONTYPE OGR<br>
> CONNECTION "/vsis3/bucket/path/data.fgb"<br>
> DATA "rm_trace"<br>
> <br>
> v8rc ms_error log:<br>
> [Fri Aug 26 10:24:13 2022].854479 msDrawMap(): Image handling error.<br>
> Failed to draw layer named 'rm_trace'.<br>
> <br>
> v7.6.4 ms_error log<br>
> [Fri Aug 26 10:06:59 2022].388096 msOGRFileOpen(): OGR error. Open<br>
> failed for OGR connection in layer `rm_trace'. File not found or<br>
> unsupported format. Check server logs.<br>
> [Fri Aug 26 10:06:59 2022].388132 Open failed for OGR connection in<br>
> layer `rm_trace'.<br>
> <br>
> -- <br>
> <a href="http://www.postholer.com" rel="noreferrer" target="_blank">www.postholer.com</a> <<a href="http://www.postholer.com" rel="noreferrer" target="_blank">http://www.postholer.com</a>><br>
> _______________________________________________<br>
> MapServer-dev mailing list<br>
> <a href="mailto:MapServer-dev@lists.osgeo.org" target="_blank">MapServer-dev@lists.osgeo.org</a> <mailto:<a href="mailto:MapServer-dev@lists.osgeo.org" target="_blank">MapServer-dev@lists.osgeo.org</a>><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/mapserver-dev" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/mapserver-dev</a><br>
> <<a href="https://lists.osgeo.org/mailman/listinfo/mapserver-dev" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/mapserver-dev</a>><br>
> <br>
_______________________________________________<br>
MapServer-dev mailing list<br>
<a href="mailto:MapServer-dev@lists.osgeo.org" target="_blank">MapServer-dev@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/mapserver-dev" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/mapserver-dev</a><br>
</blockquote></div></div>