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