Great! Thanks for letting us know.
Kind regards,
Ben.
On 16/06/18 02:24, Todd Jacobus wrote:
Hi Ben,
UPDATE: it works! I added a data security rule that allows write
permissions for the postgis layer. Thank you so much for your assistance
in this. You're making the world a better place!
B
Hi Ben,
UPDATE: it works! I added a data security rule that allows write
permissions for the postgis layer. Thank you so much for your assistance
in this. You're making the world a better place!
Best,
Todd
On Fri, Jun 15, 2018 at 8:03 AM, Todd Jacobus wrote:
> Ben,
>
> Interesting! I chan
Ben,
Interesting! I changed the namespace as per your suggestion and I think
we're making progress. At least, I'm seeing a different error (see below),
stating that the layer/table (aoi_features) is read-only. I assume this
means GeoServer was able to connect to the right workspace/datastore/la
Todd,
I do not think the namespace matches. You have: xmlns:aoi="aoi" and
targetNamespace="aoi" which I think should be something like (for
example)): xmlns:aoi="http://www.tcartadata.com/aoi"; and
targetNamespace="http://www.tcartadata.com/aoi";.
Please check your workspace settings for the
Thanks again Ben,
Here's the DescribeFeatureType response:
http://www.opengis.net/gml";
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; elementFormDefault="qualified"
targetNamespace="aoi">
http://www.opengis.net/gml"; schemaLocation="
http://www.tcartadata.com:80/geoserver/schemas/gml/3.1.1/base/g
Todd,
what is the namespace of the aoi workspace? Does it match the xmlns below?
Are you able to get a WFS 1.1 GetFeature response?
Kind regards,
Ben.
On 15/06/18 10:29, Todd Jacobus wrote:
Hi Ben,
Thanks very much for the help. I have since migrated to OpenLayers since
they have a functi
Hi Ben,
Thanks very much for the help. I have since migrated to OpenLayers since
they have a function that writes the transaction GML for you, which has
made things much simpler. However, I would love to ask another question.
I'm seeing a " Feature type 'aoi_features' is not available" error (I
Todd,
secondary namespaces are only required for the app-schema data store,
which does not support WFS-T.
For non-app-schema data stores, namespace prefixes should be defined in
the WFS-T request document. The error you see is consistent with an
undefined namespace prefix. Try adding an xmln
