I’m an S57 expert. Send me the data - I’ll take a look, there’s a lot of leeway
with S57 and sometimes it trips up GDAL. I had issues with AML data before
which is similar…
Jonathan.
Sent from my iPhone
> On 27 Jan 2022, at 10:44, Momtchil Momtchev wrote:
>
>
>
>
> Your code looks O
DSNM is dataset name. I'ts defined in the DSID which only occurs in the
first field/subfield group in the dataset - not sure what the driver does
in respect of it. In terms of identifiers s-57 has "FOID"s, so each feature
has a unique id made up of a combination of the agency code and two
integers
http://s100.iho.int/S100/productspecs
this will become IHO S-401 in time when revised but the features/attributes
will probably stay the same in name...
JP
On Thu, 19 Dec 2019 at 14:23, Andreas Oxenstierna wrote:
> Hi list
>
> see
>
> http://www.unece.org/fileadmin/DAM/trans/doc/finaldocs/sc3/
These are features and attributes from the Inland ENC catalogue which is an
S-57 product specification similar to ENC - basically ENCs for inland
waterways. unlocd is UN Location Code, the unique identifier of a port and
wtwdis is "waterway distance" - both from the IENC product specification.
The
hi Even, thanks for the quick reply - seems to make sense and chimes with
what we've found - certainly in the short term I think we can use
gml:PointProperty to get us where we want to go The Marine S-100 model
adds an association to an information type into the geometry primitive by
extension
Hi everyone,
I'm using the GMLAS driver in connection with the OGCs pilot project on
maritime limits and boundaries. The first part of the project is the
creation of an application schema and we're using the IHO S-100 profile of
GML. What I've noticed is that the GMLAS driver won't recognise geome
sue date) is incorrect, it
> just has the same value as DSID_UADT (update application date).
>
> On Thu, Aug 30, 2018, 4:27 AM kusala nine wrote:
>
>> The biggest work item for S-100 compatibility would be an update to the
>> GDAL/OGR drivers for iso8211 in order to parse th
The biggest work item for S-100 compatibility would be an update to the
GDAL/OGR drivers for iso8211 in order to parse the S-101 iso8211 encoding.
S-101 is the candidate replacement for S-57 ENC data - so, at some point
all of NOAA's S-57 marine data will be available as S-101 datasets too.
There's
Hi - I don’t post a lot to this group but I work extensively with the IHO and
the group developing S-100. It’s a fairly broad framework standard with
multiple product specifications emerging from it and its own GML profile
included in the encodings. Iso8211 is another encoding included in the ma
hi, I work for a hydrographic office and S-57 is one of our core formats.
There's a LOT of information in S-57 and I'm really interested in data
which has been produced through an open SDK like this. Do you also produce
updates and deal with the topology aspects of the geometry? I'd be really
inter
gdal/.libs/libgdal.so: undefined reference to
`mongo::BulkOperationBuilder::insert(mongo::BSONObj const&)'
/home/ubuntu/gdal/gdal/gdal/.libs/libgdal.so: undefined reference to
`mongo::OID::init(std::basic_string,
std::allocator > const&)'
/home/ubuntu/gdal/gdal/gdal/.libs/libgdal.so: undefine
great thanks - I'll have a go. many thanks for the pointer.
J
On Wed, Jun 24, 2015 at 4:23 PM, Even Rouault
wrote:
> Jon,
>
> It is in the development version (2.1.0dev), not 2.0.0. The website
> displays
> the doc of the dev version.
>
> On Unix, you must use the following configure options:
>
Hi - has anyone got any pointers on compiling the mongodb drivers into the
latest 2.0.0 version of gdal. I've been watching for a while and the new
2.0.0 page has a table saying that mongo is included but not compiled in by
default. I've downloaded the libraries and compiled them from the link on
t
13 matches
Mail list logo
