Re: [Geoserver-users] undefined

[Gavin Medley]

Hi Ben,

I understand your workaround I think. However, can you clarify what you
mean by “neither approach is schema-valid”? Are you saying this would be a
violation of GML or violation of the schema as I presented it?

Also, I tried including the attribute on the enclosing property (
geo:gnssReceiver) and since it is a multiple property, it just copied one
date for all instances of the property.

The schema is flexible as it’s under development and I’m working to find
the best place for some of these data. I’m experimenting with using
attributes of properties, attributes of objects, and properties themselves.

-Gavin
​

On Tue, Nov 21, 2017 at 8:37 PM, Ben Caradoc-Davies 
wrote:

> Gavin,
>
> a little experimentation confirms your findings. While ClientProperty is
> very permissive and does not require an attribute to be schema-valid, it
> does not seem to work with feature types and geometry property types,
> likely because these have special handling in the encoder that does not
> test for ClientProperty settings. I was able to use ClientProperty to set
> arbitrary attributes on a range of properties and types.
>
> A fix would be to add support for ClientProperty in the encoder binding
> for features, but I am not aware of any schema-valid use-cases.
>
> As a workaround (and neither approach is schema-valid), you can put this
> attribute on any convenient property. Some might not work because they have
> special handling in the encoder. For example, in the app-schema tutorial
> configuration for gsml:MappedFeature, I added a mapping for
> gml:description, which is inherited by all features from their abstract
> base type. You might have a better mapping target. Note the use of
> encodeIfEmpty, and substitute your source column name for the CQL date
> literal.
>
> 
> 
> gml:description
> 
> 
> dateInserted
> '2017-11-10'
> 
> true
> 
>
> I then get the following when I request gsml:GeologicUnit (to show it
> works when chained):
>
> 
> 
> [...]
> 
> 
> 
> Some basalt
> [...]
>
> Kind regards,
> Ben.
>
>
> On 22/11/17 06:18, Gavin Medley wrote:
>
>> Hello,
>>
>> I have a simple feature chaining setup
>>
>> 
>>  geo:gnssReceiver
>>  
>>  fourid
>>  geo:GnssReceiver
>>  FEATURE_LINK[1]
>>  
>>  true
>>  false
>> 
>>
>> which produces a GML property geo:gnssReceiver with a value of a
>> geo:GnssReceiver object. There may be multiple occurrences of this
>> property.
>>
>> I need to include some attributes on the object level that are not the
>> same
>> for every instance of geo:GnssReceiver. Specifically I have a metadata
>> attribute called dateInserted to keep track of changes. Is this possible
>> at
>> the object level? I want it to look like this when encoded:
>>
>> 
>>  > dateInserted="2017-11-10">
>>...
>>  
>> 
>>
>> I have tried, without success, to add a  to the the nested
>> mapping file like so:
>>
>> 
>>  geo:GnssReceiver
>>  
>>  dateInserted
>>  database-dateinserted-field
>>  
>> 
>>
>> Any guidance on how to proceed is much appreciated.
>>
>> -Gavin
>> ​
>>
>>
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>>
>> ___
>> Geoserver-users mailing list
>>
>> Please make sure you read the following two resources before posting to
>> this list:
>> - Earning your support instead of buying it, but Ian Turton:
>> http://www.ianturton.com/talks/foss4g.html#/
>> - The GeoServer user list posting guidelines:
>> http://geoserver.org/comm/userlist-guidelines.html
>>
>> Geoserver-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>>
> --
> Ben Caradoc-Davies 
> Director
> Transient Software Limited <http://transient.nz/>
> New Zealand
>



-- 
Gavin Medley
Software Engineer, UNAVCO
6350 Nautilus Drive
Boulder, CO 80301-5394
Mobile: 505-819-1270
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Mapping PostGis geometry to app schema

[Gavin Medley]

Hi Tomas,

I can't see your view, schema, mapping, or result. Try pasting in plain
text maybe? In general though, I can tell you this is definitely possible.

-Gavin

On Tue, Nov 21, 2017 at 2:45 PM, geseus  wrote:

> Hi,
> is it possible to use geometry type from PostGis in app schema?
>
> I have view in postgre db:
>
>
> Then i have schema:
>
>
>
> App schema mapping is defined as:
>
>
>
> But when a call WFS service, there is empty  Geom element in the result:
>
>
> So, how can i map postGis geometry type to element in app schema?
>
> Thanks a lot,
> Tomas
>
>
>
>
>
> --
> Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-
> f3786390.html
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines: http://geoserver.org/comm/
> userlist-guidelines.html
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>



-- 
Gavin Medley
Software Engineer, UNAVCO
6350 Nautilus Drive
Boulder, CO 80301-5394
Mobile: 505-819-1270
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] undefined

[Gavin Medley]

Hello,

I have a simple feature chaining setup


geo:gnssReceiver

fourid
geo:GnssReceiver
FEATURE_LINK[1]

true
false


which produces a GML property geo:gnssReceiver with a value of a
geo:GnssReceiver object. There may be multiple occurrences of this property.

I need to include some attributes on the object level that are not the same
for every instance of geo:GnssReceiver. Specifically I have a metadata
attribute called dateInserted to keep track of changes. Is this possible at
the object level? I want it to look like this when encoded:



  ...



I have tried, without success, to add a  to the the nested
mapping file like so:


geo:GnssReceiver

dateInserted
database-dateinserted-field



Any guidance on how to proceed is much appreciated.

-Gavin
​
-- 
Gavin Medley
Software Engineer, UNAVCO
6350 Nautilus Drive
Boulder, CO 80301-5394
Mobile: 505-819-1270 <(505)%20819-1270>
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] WFS nesting

[Gavin Medley]

r completeness of sent messages and accepts no responsibility for
> changes made
> > after they were sent or for other risks which arise as a result of e-mail
> > transmission, viruses, etc.
> >
> >
> > 
> --
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > ___
> > Geoserver-users mailing list
> >
> > Please make sure you read the following two resources before posting to
> this list:
> > - Earning your support instead of buying it, but Ian Turton:
> > http://www.ianturton.com/talks/foss4g.html#/
> > - The GeoServer user list posting guidelines:
> > http://geoserver.org/comm/userlist-guidelines.html
> >
> > Geoserver-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/geoserver-users
> >
> >
> >
> > 
> --
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> >
> >
> >
> > ___
> > Geoserver-users mailing list
> >
> > Please make sure you read the following two resources before posting to
> this list:
> > - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> > - The GeoServer user list posting guidelines: http://geoserver.org/comm/
> userlist-guidelines.html
> >
> > Geoserver-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/geoserver-users
> >
>
> --
> Ben Caradoc-Davies 
> Director
> Transient Software Limited <http://transient.nz/>
> New Zealand
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines: http://geoserver.org/comm/
> userlist-guidelines.html
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>


-- 
Gavin Medley
Software Engineer, UNAVCO
6350 Nautilus Drive
Boulder, CO 80301-5394
Mobile: 505-819-1270
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] App Schema Reuse of targetElement in Feature Chaining

[Gavin Medley]

Hi,

Suppose that I have two properties, `geo:siteContact` and
`geo:siteMetadataCustodian` that both contain the same type of object,
`gmd:CI_ResponsibleParty` so that properly encoded, they look like
```

   
   


   
   

```
I want to use Application Schema feature chaining to map into these
properties but I can't figure out how to create two different mapping files
for the same `gmd:CI_ResponsibleParty` because I always get the error
```
Duplicate mappingName or targetElement across FeatureTypeMapping instances
detected. They have to be unique, or app-schema doesn't know which one to
get. Please check your mapping file(s) with mappingName or targetElement
of: urn:xml-gov-au:icsm:egeodesy:0.4:GnssReceiver
```
The key is that despite having the same targetElement (and therefore
linkElement in the root mapping file), different information (from a
different table in the database) is being mapped into these objects. How do
I solve this?


Best,

Gavin

-- 
Gavin Medley
Software Engineer, UNAVCO
6350 Nautilus Drive
Boulder, CO 80301-5394
Mobile: 505-819-1270 <(505)%20819-1270>
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] App Schema Encodes xs:nil="true"

[Gavin Medley]

Hi,

What causes App Schema to encode xs:nil="true"? I have many elements which
I've marked with `true` but only some
elements get tagged with `xs:nil="true"`. Most of them show up as
`` and I'm not using `` with any of the
mappings. What causes this? Is there something in my xsd file that causes
the `xs:nil` attribute to be encoded?

Best,

Gavin

-- 
Gavin Medley
Software Engineer, UNAVCO
6350 Nautilus Drive
Boulder, CO 80301-5394
Mobile: 505-819-1270
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] encodeIfEmpty with string values length zero

[Gavin Medley]

Bug report filed: https://osgeo-org.atlassian.net/browse/GEOS-8362

On Fri, Oct 20, 2017 at 3:24 PM, Ben Caradoc-Davies 
wrote:

> Gavin,
>
> that is interesting. I suspect that this situation was not anticipated
> (only nulls). Please file a bug report.
>
> Workarounds are to convert empty strings to nulls in a database view or a
> CQL if_then_else expression in the mapping file.
>
> Kind regards,
> Ben.
>
> On 21/10/17 05:08, Gavin Medley wrote:
>
>> Hi,
>>
>> I am using App Schema to map to GeodesyML, a rather demanding schema in
>> terms of validation. One of the problems I’m running into is missing child
>> elements that are not generated by App Schema when the database field is
>> blank. Specifically, the problem arises when the field I’m mapping
>> contains
>> an empty string (''). i.e. it’s not a null value but it *is* empty so it
>> doesn’t appear, even when I use true. Am I
>> getting this right? Is there a workaround, other than changing the data in
>> my database?
>>
>> Thanks,
>>
>> Gavin
>> ​
>>
>>
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>>
>> ___
>> Geoserver-users mailing list
>>
>> Please make sure you read the following two resources before posting to
>> this list:
>> - Earning your support instead of buying it, but Ian Turton:
>> http://www.ianturton.com/talks/foss4g.html#/
>> - The GeoServer user list posting guidelines:
>> http://geoserver.org/comm/userlist-guidelines.html
>>
>> Geoserver-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>>
> --
> Ben Caradoc-Davies 
> Director
> Transient Software Limited <http://transient.nz/>
> New Zealand
>



-- 
Gavin Medley
Software Engineer, UNAVCO
6350 Nautilus Drive
Boulder, CO 80301-5394
Mobile: 505-819-1270
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] GML Striping and App Schema

[Gavin Medley]

Hi Andrea,

I'm running a recent install of 2.12.0

-Gavin

On Mon, Oct 23, 2017 at 11:45 AM, Andrea Aime 
wrote:

> Gavin,
> one question, which version of GeoServer are you using?
> Looked through the posts and could not see it.
>
> Cheers
> Andrea
>
> On Fri, Oct 20, 2017 at 7:38 PM, Gavin Medley  wrote:
>
>> Hi,
>>
>> I understand that App Schema enforces GML striping, i.e. “complex types
>> are never the direct property of another complex type; they are always
>> contained in a property type to ensure that their type is encoded in a
>> surrounding element.” However, in GeodesyML, there are complex types (
>> geo:GnssReceiver) and simple types (geo:dateInserted) *both* nested
>> inside a geo:gnssReceiver property element like so.
>>
>> 
>>  > gml:id="GnssReceiver.87bff11d-a3bc-4e84-b7bc-5175f824f0f5">
>> Receiver 1
>> 3213
>> > codeList="http://xml.gov.au/icsm/geodesyml/codelists/antenna-receiver-codelists.xml#GeodesyML_GNSSReceiverTypeCode";
>>  codeListValue="ASHTECH Z-XII3" 
>> codeSpace="https://igscb.jpl.nasa.gov/igscb/station/general/rcvr_ant.tab";>ASHTECH
>>  Z-XII3
>> > codeSpace="eGeodesy/satelliteSystem">GPS
>> 1Y05-1D04
>> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:nil="true"/>
>> 1996-01-01T00:00:00.000Z
>> 1998-09-17T00:00:00.000Z
>> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:nil="true"/>
>>  
>>  1996-01-01T00:00:00.000Z
>> 
>>
>> I have a feature chained element such that I map geo:GnssReceiver type
>> into the geo:gnssReceiver property but I cannot figure out how to get
>> geo:dateInserted to appear in each (of *many*) geo:gnssReceiver
>> elements. I tried referencing the XPath and simply adding the
>> AttributeMapping after my GnssReceiver feature chain element (as below)
>> but dateInserted only appears on *one* instance of gnssReceiver.
>>
>> ...
>> 
>> geo:gnssReceiver
>> 
>> fourid
>>         geo:GnssReceiver
>> FEATURE_LINK[1]
>> 
>> true
>> false
>> 
>>
>> 
>> geo:gnssReceiver/geo:dateInserted
>> 
>> 
>> 
>> true
>> true
>> 
>> ...
>>
>> Does anyone have a suggestion on how to achieve this or am I missing
>> something obvious?
>>
>> Regards,
>>
>> Gavin
>> ​
>> --
>> Gavin Medley
>> Software Engineer, UNAVCO
>> 6350 Nautilus Drive
>> <https://maps.google.com/?q=6350+Nautilus+Drive+Boulder,+CO+80301&entry=gmail&source=g>
>> Boulder, CO 80301
>> <https://maps.google.com/?q=6350+Nautilus+Drive+Boulder,+CO+80301&entry=gmail&source=g>
>> -5394
>> Mobile: 505-819-1270 <(505)%20819-1270>
>> med...@unavco.org
>>
>>
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> Geoserver-users mailing list
>>
>> Please make sure you read the following two resources before posting to
>> this list:
>> - Earning your support instead of buying it, but Ian Turton:
>> http://www.ianturton.com/talks/foss4g.html#/
>> - The GeoServer user list posting guidelines:
>> http://geoserver.org/comm/userlist-guidelines.html
>>
>> Geoserver-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>>
>
>
> --
>
> Regards,
>
> Andrea Aime
>
> ==
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> <https://maps.google.com/?q=Via+di+Montramito+3/A+55054+%C2%A0Massarosa&entry=gmail&source=g>
> 55054  Massarosa
> <https://maps.google.com/?q=Via+di+Montramito+3/A+55054+%C2%A0Massarosa&entry=gmail&source=g>
> (LU)
> phone: +39 0584 962313 <+39%200584%20962313>
> fax: +39 0584 1660272 <+39%200584%20166%200272>
> mob: +39  339 8844549 <+39%20339%20884%204549>
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> AVVERTEN

Re: [Geoserver-users] Mapping Database Fields to XML Attributes

[Gavin Medley]

Great! Thank you Ben.

-Gavin

On Fri, Oct 20, 2017 at 2:30 PM, Ben Caradoc-Davies 
wrote:

> Gavin,
>
> the content of the  tag is a bare CQL expression without any other
> XML expressions. Please try this:
>
> 
> codeListValue
> country
> 
>
> If you need to manipulate the string, you can use CQL. Literal strings
> need to be in CQL form, that is, surrounded by single quotes (').
>
> Kind regards,
> Ben.
>
> On 21/10/17 04:17, Gavin Medley wrote:
>
>> Hi all,
>>
>> I’m sure this is possible but I can’t figure out the syntax to put in my
>> mapping file. I need to map a field in my database, country to be an
>> attribute value codeListValue I think my  should be
>> something like the following but the attribute just doesn’t appear at all
>> in my WFS requests.
>>
>> 
>>  codeListValue
>>  
>>  country
>>  
>> 
>>
>> Thanks for the help!
>>
>> -Gavin
>> ​
>>
>>
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>>
>> ___
>> Geoserver-users mailing list
>>
>> Please make sure you read the following two resources before posting to
>> this list:
>> - Earning your support instead of buying it, but Ian Turton:
>> http://www.ianturton.com/talks/foss4g.html#/
>> - The GeoServer user list posting guidelines:
>> http://geoserver.org/comm/userlist-guidelines.html
>>
>> Geoserver-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>>
> --
> Ben Caradoc-Davies 
> Director
> Transient Software Limited <http://transient.nz/>
> New Zealand
>



-- 
Gavin Medley
Software Engineer, UNAVCO
6350 Nautilus Drive
Boulder, CO 80301-5394
Mobile: 505-819-1270
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] GML Striping and App Schema

[Gavin Medley]

Hi,

I understand that App Schema enforces GML striping, i.e. “complex types are
never the direct property of another complex type; they are always
contained in a property type to ensure that their type is encoded in a
surrounding element.” However, in GeodesyML, there are complex types (
geo:GnssReceiver) and simple types (geo:dateInserted) *both* nested inside
a geo:gnssReceiver property element like so.


 
Receiver 1
3213
http://xml.gov.au/icsm/geodesyml/codelists/antenna-receiver-codelists.xml#GeodesyML_GNSSReceiverTypeCode";
codeListValue="ASHTECH Z-XII3"
codeSpace="https://igscb.jpl.nasa.gov/igscb/station/general/rcvr_ant.tab";>ASHTECH
Z-XII3
GPS
1Y05-1D04
http://www.w3.org/2001/XMLSchema-instance"; xsi:nil="true"/>
1996-01-01T00:00:00.000Z
1998-09-17T00:00:00.000Z
http://www.w3.org/2001/XMLSchema-instance"; xsi:nil="true"/>
 
 1996-01-01T00:00:00.000Z


I have a feature chained element such that I map geo:GnssReceiver type into
the geo:gnssReceiver property but I cannot figure out how to get
geo:dateInserted to appear in each (of *many*) geo:gnssReceiver elements. I
tried referencing the XPath and simply adding the AttributeMapping after my
GnssReceiver feature chain element (as below) but dateInserted only appears
on *one* instance of gnssReceiver.

...

geo:gnssReceiver

fourid
geo:GnssReceiver
FEATURE_LINK[1]

true
false



geo:gnssReceiver/geo:dateInserted



true
true

...

Does anyone have a suggestion on how to achieve this or am I missing
something obvious?

Regards,

Gavin
​
-- 
Gavin Medley
Software Engineer, UNAVCO
6350 Nautilus Drive
Boulder, CO 80301-5394
Mobile: 505-819-1270
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] encodeIfEmpty with string values length zero

[Gavin Medley]

Hi,

I am using App Schema to map to GeodesyML, a rather demanding schema in
terms of validation. One of the problems I’m running into is missing child
elements that are not generated by App Schema when the database field is
blank. Specifically, the problem arises when the field I’m mapping contains
an empty string (''). i.e. it’s not a null value but it *is* empty so it
doesn’t appear, even when I use true. Am I
getting this right? Is there a workaround, other than changing the data in
my database?

Thanks,

Gavin
​
-- 
Gavin Medley
Software Engineer, UNAVCO
6350 Nautilus Drive
Boulder, CO 80301-5394
Mobile: 505-819-1270
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] Mapping Database Fields to XML Attributes

[Gavin Medley]

Hi all,

I’m sure this is possible but I can’t figure out the syntax to put in my
mapping file. I need to map a field in my database, country to be an
attribute value codeListValue I think my  should be
something like the following but the attribute just doesn’t appear at all
in my WFS requests.


codeListValue

country



Thanks for the help!

-Gavin
​
-- 
Gavin Medley
Software Engineer, UNAVCO
6350 Nautilus Drive
Boulder, CO 80301-5394
Mobile: 505-819-1270
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] PostGIS Query with tstzrange

[Gavin Medley]

Hi all,

I am using Geoserver to make a view (Layer) from my PostGIS database using
the query below. Unfortunately, I can’t get the tstzrange field to appear.
Is there a limitation here that I’m not seeing? I don’t get an error but
the field just doesn’t appear in the “Attributes” table after clicking
“Refresh.” The query works fine in PGAdmin and in the CLI. What am I
missing?

WITH
metric_types AS
(SELECT station, station_type, tstzrange(min(lower(duration)),
max(upper(duration))) AS active_dates
FROM (
select metric_station.name as station,
metric_type.name as station_type,
duration,
ROW_NUMBER() OVER (PARTITION BY metric_station_id, metric_type_id
ORDER BY lower(duration) DESC) AS first_row,
ROW_NUMBER() OVER (PARTITION BY metric_station_id, metric_type_id
ORDER BY lower(duration)  ASC) as last_row
FROM metrics.active_station_status
JOIN metric_type ON metric_type_id = metric_type.id
JOIN metric_station ON metric_station_id = metric_station.id)
 AS station_sub
WHERE first_row = 1 or last_row = 1
GROUP BY station, station_type)
SELECT
t3sstations.idstn,
metric_types.station,
t3sstations.stnname,
t3sstations.stnnickname,
ST_SETSRID(ST_MAKEPOINT(t3sstations.stnlong, t3sstations.stnlat),
4326) AS lonlat_geom,
t3sstations.stnlong,
t3sstations.stnlat,
t3sstations.stnelev,
stationtype.label,
t3sstations.stninsdate,
metric_types.station_type AS sensor_type,
metric_types.active_dates
FROM
t3sstations
INNER JOIN metric_types ON t3sstations.fourcharid=metric_types.station
LEFT JOIN stationtype ON stationtype.id = t3sstations.idstationtype

​
-- 
Gavin Medley
Software Engineer, UNAVCO
6350 Nautilus Drive
Boulder, CO 80301-5394
Mobile: 505-819-1270
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] PostGIS Query with tstzrange

[Gavin Medley]

*UPDATE:* I went to the logs and found this. Looks like Geoserver doesn’t
support the tstzrange datatype.

2017-10-10 20:38:03,371 WARN [geotools.jdbc] - Could not find mapping
for 'date_range', ignoring the column and setting the feature type
read only
2017-10-10 20:38:57,543 WARN [geotools.jdbc] - Could not find mapping
for 'active_dates', ignoring the column and setting the feature type
read only

​

On Tue, Oct 10, 2017 at 2:50 PM, Gavin Medley  wrote:

> Hi all,
>
> I am using Geoserver to make a view (Layer) from my PostGIS database using
> the query below. Unfortunately, I can’t get the tstzrange field to
> appear. Is there a limitation here that I’m not seeing? I don’t get an
> error but the field just doesn’t appear in the “Attributes” table after
> clicking “Refresh.” The query works fine in PGAdmin and in the CLI. What am
> I missing?
>
> WITH
> metric_types AS
> (SELECT station, station_type, tstzrange(min(lower(duration)), 
> max(upper(duration))) AS active_dates
> FROM (
> select metric_station.name as station,
> metric_type.name as station_type,
> duration,
> ROW_NUMBER() OVER (PARTITION BY metric_station_id, metric_type_id ORDER 
> BY lower(duration) DESC) AS first_row,
> ROW_NUMBER() OVER (PARTITION BY metric_station_id, metric_type_id ORDER 
> BY lower(duration)  ASC) as last_row
> FROM metrics.active_station_status
> JOIN metric_type ON metric_type_id = metric_type.id
> JOIN metric_station ON metric_station_id = metric_station.id)
>  AS station_sub
> WHERE first_row = 1 or last_row = 1
> GROUP BY station, station_type)
> SELECT
> t3sstations.idstn,
> metric_types.station,
> t3sstations.stnname,
> t3sstations.stnnickname,
> ST_SETSRID(ST_MAKEPOINT(t3sstations.stnlong, t3sstations.stnlat), 4326) 
> AS lonlat_geom,
> t3sstations.stnlong,
> t3sstations.stnlat,
> t3sstations.stnelev,
> stationtype.label,
> t3sstations.stninsdate,
> metric_types.station_type AS sensor_type,
> metric_types.active_dates
> FROM
> t3sstations
> INNER JOIN metric_types ON t3sstations.fourcharid=metric_types.station
> LEFT JOIN stationtype ON stationtype.id = t3sstations.idstationtype
>
> ​
> --
> Gavin Medley
> Software Engineer, UNAVCO
> 6350 Nautilus Drive
> Boulder, CO 80301-5394
> Mobile: 505-819-1270 <(505)%20819-1270>
> med...@unavco.org
>
>
>


-- 
Gavin Medley
Software Engineer, UNAVCO
6350 Nautilus Drive
Boulder, CO 80301-5394
Mobile: 505-819-1270
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] EPSG:4326 Incorrect WKT - Coordinates Reversed!

[Gavin Medley]

Hi Ben,

Hmm, that is certainly the behavior. So the st_makepoint function doesn't
enforce it upon point creation but other postgis functions do expect (lon,
lat). In the context of Geoserver, it is also not enforced is that correct?
My observation is that Geoserver will happily take my (lat, lon) geometry
and project it, mirrored (I've since fixed my database though). Not sure
what it does with the values that are out of bounds.

On Wed, Aug 16, 2017 at 3:33 PM, Ben Caradoc-Davies 
wrote:

> Gavin,
>
> you might think that you have tables with geometries with lat/lon axis
> order, but I suspect that, as soon as you try to reproject, you will
> discover that postgis does not agree.
>
> Try transforming your office location in WGS 84 to NAD83(2011) / Colorado
> Central (eastings/northings in metres):
>
> lat/lon axis order:
>
> test=> select st_asewkt(st_transform(st_setsrid(st_makepoint(40.061165,
> -105.205885), 4326), 6427));
> ERROR:  transform: couldn't project point (40.0612 -105.206 0): latitude
> or longitude exceeded limits (-14)
>
> lon/lat axis order:
>
> test=> select st_asewkt(st_transform(st_setsrid(st_makepoint(-105.205885,
> 40.061165), 4326), 6427));
>  st_asewkt
> ---
>  SRID=6427;POINT(939496.893326505 552163.38163549)
> (1 row)
>
> Kind regards,
> Ben.
>
>
> On 17/08/17 06:57, Gavin Medley wrote:
>
>> Hi Jukka,
>>
>> You are right about the note obviously. That is definitely not enforced by
>> the function in any way though so I think it's a convention but not a
>> requirement. I know because I have tables with geometries in the format
>> (lat, lon) and the data is preserved.
>>
>> This is a long standing debate and I don't think it will be resolved any
>> time soon. I think we can probably close this thread.
>>
>> On Wed, Aug 16, 2017 at 12:47 PM, Rahkonen Jukka (MML) <
>> jukka.rahko...@maanmittauslaitos.fi> wrote:
>>
>> Hi,
>>>
>>>
>>> The link you provided actually shows this information:
>>>
>>> geometry *ST_MakePoint*(double precision x, double precision y);
>>>
>>> and
>>>
>>> Note x is longitude and y is latitude
>>>
>>>
>>> I would rather say that the function is agnostic to the EPSG
>>> specification
>>> for the given SRID because it requires always longitude-latitude /
>>> easting-northing order.
>>>
>>>
>>> -Jukka Rahkonen-
>>>
>>>
>>> --
>>> *Lähettäjä:* Gavin Medley 
>>> *Lähetetty:* 16. elokuuta 2017 21:21
>>> *Vastaanottaja:* Andrea Aime
>>> *Kopio:* GeoServer Mailing List List; Rahkonen Jukka (MML)
>>> *Aihe:* Re: [Geoserver-users] EPSG:4326 Incorrect WKT - Coordinates
>>>
>>> Reversed!
>>>
>>> Hi Andrea,
>>>
>>> Maybe we are thinking of different ways of storing the data. To make the
>>> Point geometries I'm using ST_SetSRID(ST_MakePoint(lat, lon), 4326) as
>>> documented here:
>>> https://postgis.net/docs/ST_MakePoint.html
>>> I think the function is agnostic as to the actual values entered so it's
>>> up to the user to ensure that the order and values match the EPSG
>>> specification for the given SRID.
>>>
>>> On Wed, Aug 16, 2017 at 11:49 AM, Andrea Aime <
>>> andrea.a...@geo-solutions.it> wrote:
>>>
>>> Ah!
>>>> As far as I know postgis, Oracle spatial, SQL server all require data to
>>>> be stored as east/north no matter what the CRS is
>>>>
>>>> Cheers
>>>> Andrea
>>>>
>>>> Il 16 ago 2017 11:08 AM, "Gavin Medley"  ha scritto:
>>>>
>>>> Hi Jukka,
>>>>
>>>> The problem wasn't with the WMS in the end. I had the coordinates in our
>>>> database (forming a layer on top of the cascaded WMS) in the EPSG
>>>> dictated
>>>> order: (lat, lon) so the points on my map were rotated 180 degrees and
>>>> mirrored across (0,0). I just had to redefine all of the Point
>>>> geometries
>>>> in the database to be (lon, lat).
>>>>
>>>>
>>>> On Wed, Aug 2, 2017 at 6:51 AM, Rahkonen Jukka (MML) <
>>>> jukka.rahko...@maanmittauslaitos.fi> wrote:
>>>>
>>>> Hi,
>>>>>
>>>>>
>>>>> You wrote:
>>>>>
>>>>> "I'm using a

Re: [Geoserver-users] EPSG:4326 Incorrect WKT - Coordinates Reversed!

[Gavin Medley]

Hi Jukka,

You are right about the note obviously. That is definitely not enforced by
the function in any way though so I think it's a convention but not a
requirement. I know because I have tables with geometries in the format
(lat, lon) and the data is preserved.

This is a long standing debate and I don't think it will be resolved any
time soon. I think we can probably close this thread.

On Wed, Aug 16, 2017 at 12:47 PM, Rahkonen Jukka (MML) <
jukka.rahko...@maanmittauslaitos.fi> wrote:

> Hi,
>
>
> The link you provided actually shows this information:
>
> geometry *ST_MakePoint*(double precision x, double precision y);
>
> and
>
> Note x is longitude and y is latitude
>
>
> I would rather say that the function is agnostic to the EPSG specification
> for the given SRID because it requires always longitude-latitude /
> easting-northing order.
>
>
> -Jukka Rahkonen-
>
>
> --
> *Lähettäjä:* Gavin Medley 
> *Lähetetty:* 16. elokuuta 2017 21:21
> *Vastaanottaja:* Andrea Aime
> *Kopio:* GeoServer Mailing List List; Rahkonen Jukka (MML)
> *Aihe:* Re: [Geoserver-users] EPSG:4326 Incorrect WKT - Coordinates
> Reversed!
>
> Hi Andrea,
>
> Maybe we are thinking of different ways of storing the data. To make the
> Point geometries I'm using ST_SetSRID(ST_MakePoint(lat, lon), 4326) as
> documented here:
> https://postgis.net/docs/ST_MakePoint.html
> I think the function is agnostic as to the actual values entered so it's
> up to the user to ensure that the order and values match the EPSG
> specification for the given SRID.
>
> On Wed, Aug 16, 2017 at 11:49 AM, Andrea Aime <
> andrea.a...@geo-solutions.it> wrote:
>
>> Ah!
>> As far as I know postgis, Oracle spatial, SQL server all require data to
>> be stored as east/north no matter what the CRS is
>>
>> Cheers
>> Andrea
>>
>> Il 16 ago 2017 11:08 AM, "Gavin Medley"  ha scritto:
>>
>> Hi Jukka,
>>
>> The problem wasn't with the WMS in the end. I had the coordinates in our
>> database (forming a layer on top of the cascaded WMS) in the EPSG dictated
>> order: (lat, lon) so the points on my map were rotated 180 degrees and
>> mirrored across (0,0). I just had to redefine all of the Point geometries
>> in the database to be (lon, lat).
>>
>>
>> On Wed, Aug 2, 2017 at 6:51 AM, Rahkonen Jukka (MML) <
>> jukka.rahko...@maanmittauslaitos.fi> wrote:
>>
>>> Hi,
>>>
>>>
>>> You wrote:
>>>
>>> "I'm using a cascading WMS (from another Geoserver) to put a map behind
>>> our GPS station locations and I had to switch all the coordinates to make
>>> the projections overlay correctly."
>>>
>>>
>>> Could you explain why do you think that WKT definition is the reason for
>>> your trouble with cascading WMS and what coordinates you need to switch?
>>> Cascading WMS is usually painless if user remembers that for WMS versions
>>> prior 1.3 the BBOX is expressed always in longitude-latitude /
>>> easting-northing order for all the projections.  In WMS 1.3 the official
>>> axis order is to be honoured. Could it be that you are cascading WMS 1.1.x
>>> and you make a wrong assumption that BBOX should be in lat-lon order? If
>>> that is the case, simply start cascading WMS 1.3.0.
>>>
>>>
>>> -Jukka Rahkonen-
>>>
>>>
>>>
>>>
>>> --
>>> *Lähettäjä:* Gavin Medley 
>>> *Lähetetty:* 1. elokuuta 2017 20:15
>>> *Vastaanottaja:* geoserver-users@lists.sourceforge.net
>>> *Aihe:* [Geoserver-users] EPSG:4326 Incorrect WKT - Coordinates
>>> Reversed!
>>>
>>> Hi all,
>>>
>>> I believe that the WKT for EPGS:4326 in Geoserver is incorrect. Can
>>> someone verify?
>>>
>>> Note the lat lon coordinate order in the following strings. Geoserver
>>> displays:
>>>
>>> GEOGCS["WGS 84",
>>> DATUM["World Geodetic System 1984",
>>> SPHEROID["WGS 84", 6378137.0, 298.257223563, AUTHORITY["EPSG","7030"]],
>>> AUTHORITY["EPSG","6326"]],
>>> PRIMEM["Greenwich", 0.0, AUTHORITY["EPSG","8901"]],
>>> UNIT["degree", 0.017453292519943295],
>>> AXIS["Geodetic longitude", EAST],
>>> AXIS["Geodetic latitude", NORTH],
>>> AUTHORITY["EPSG","4326"]]
>>>
>

Re: [Geoserver-users] EPSG:4326 Incorrect WKT - Coordinates Reversed!

[Gavin Medley]

Hi Andrea,

Maybe we are thinking of different ways of storing the data. To make the
Point geometries I'm using ST_SetSRID(ST_MakePoint(lat, lon), 4326) as
documented here:
https://postgis.net/docs/ST_MakePoint.html
I think the function is agnostic as to the actual values entered so it's up
to the user to ensure that the order and values match the EPSG
specification for the given SRID.

On Wed, Aug 16, 2017 at 11:49 AM, Andrea Aime 
wrote:

> Ah!
> As far as I know postgis, Oracle spatial, SQL server all require data to
> be stored as east/north no matter what the CRS is
>
> Cheers
> Andrea
>
> Il 16 ago 2017 11:08 AM, "Gavin Medley"  ha scritto:
>
> Hi Jukka,
>
> The problem wasn't with the WMS in the end. I had the coordinates in our
> database (forming a layer on top of the cascaded WMS) in the EPSG dictated
> order: (lat, lon) so the points on my map were rotated 180 degrees and
> mirrored across (0,0). I just had to redefine all of the Point geometries
> in the database to be (lon, lat).
>
>
> On Wed, Aug 2, 2017 at 6:51 AM, Rahkonen Jukka (MML) <
> jukka.rahko...@maanmittauslaitos.fi> wrote:
>
>> Hi,
>>
>>
>> You wrote:
>>
>> "I'm using a cascading WMS (from another Geoserver) to put a map behind
>> our GPS station locations and I had to switch all the coordinates to make
>> the projections overlay correctly."
>>
>>
>> Could you explain why do you think that WKT definition is the reason for
>> your trouble with cascading WMS and what coordinates you need to switch?
>> Cascading WMS is usually painless if user remembers that for WMS versions
>> prior 1.3 the BBOX is expressed always in longitude-latitude /
>> easting-northing order for all the projections.  In WMS 1.3 the official
>> axis order is to be honoured. Could it be that you are cascading WMS 1.1.x
>> and you make a wrong assumption that BBOX should be in lat-lon order? If
>> that is the case, simply start cascading WMS 1.3.0.
>>
>>
>> -Jukka Rahkonen-
>>
>>
>>
>>
>> --
>> *Lähettäjä:* Gavin Medley 
>> *Lähetetty:* 1. elokuuta 2017 20:15
>> *Vastaanottaja:* geoserver-users@lists.sourceforge.net
>> *Aihe:* [Geoserver-users] EPSG:4326 Incorrect WKT - Coordinates Reversed!
>>
>> Hi all,
>>
>> I believe that the WKT for EPGS:4326 in Geoserver is incorrect. Can
>> someone verify?
>>
>> Note the lat lon coordinate order in the following strings. Geoserver
>> displays:
>>
>> GEOGCS["WGS 84",
>> DATUM["World Geodetic System 1984",
>> SPHEROID["WGS 84", 6378137.0, 298.257223563, AUTHORITY["EPSG","7030"]],
>> AUTHORITY["EPSG","6326"]],
>> PRIMEM["Greenwich", 0.0, AUTHORITY["EPSG","8901"]],
>> UNIT["degree", 0.017453292519943295],
>> AXIS["Geodetic longitude", EAST],
>> AXIS["Geodetic latitude", NORTH],
>> AUTHORITY["EPSG","4326"]]
>>
>> However, epsg-registry.org lists the official WKT as:
>>
>> GEODCRS["WGS 84",
>>   DATUM["World Geodetic System 1984",
>> ELLIPSOID["WGS 84",6378137,298.257223563,LENGTHUNIT["metre",1.0]]],
>>   CS[ellipsoidal,2],
>> AXIS["latitude",north,ORDER[1]],
>> AXIS["longitude",east,ORDER[2]],
>> ANGLEUNIT["degree",0.01745329252],
>>   ID["EPSG",4326]]
>>
>> According to EPSG, latitude is FIRST. I'm using a cascading WMS (from
>> another Geoserver) to put a map behind our GPS station locations and I had
>> to switch all the coordinates to make the projections overlay correctly.
>>
>> -Gavin
>>
>> --
>> Gavin Medley
>> Software Engineer I
>> *UNAVCO*
>> 6350 Nautilus Drive
>> Boulder, CO 80301-5394
>> med...@unavco.org
>>
>>
>>
>> -- Forwarded message --
>> From: Andrea Aime 
>> To: Gavin Medley 
>> Cc: Ian Turton , geoserver-users <
>> geoserver-users@lists.sourceforge.net>
>> Bcc:
>> Date: Tue, 1 Aug 2017 22:49:11 +0200
>> Subject: Re: [Geoserver-users] EPSG:4326 Incorrect WKT - Coordinates
>> Reversed!
>> On Tue, Aug 1, 2017 at 8:09 PM, Gavin Medley  wrote:
>>
>>> Hi,
>>>
>>> I'm using 1.1.0. Shouldn't the axis order be defined by the EPSG
>>> official WKT string? Am I correct in thinking that order[1] and order[2]
>>> specify the coordinate order?
>>

Re: [Geoserver-users] EPSG:4326 Incorrect WKT - Coordinates Reversed!

[Gavin Medley]

Hi Jukka,

The problem wasn't with the WMS in the end. I had the coordinates in our
database (forming a layer on top of the cascaded WMS) in the EPSG dictated
order: (lat, lon) so the points on my map were rotated 180 degrees and
mirrored across (0,0). I just had to redefine all of the Point geometries
in the database to be (lon, lat).


On Wed, Aug 2, 2017 at 6:51 AM, Rahkonen Jukka (MML) <
jukka.rahko...@maanmittauslaitos.fi> wrote:

> Hi,
>
>
> You wrote:
>
> "I'm using a cascading WMS (from another Geoserver) to put a map behind
> our GPS station locations and I had to switch all the coordinates to make
> the projections overlay correctly."
>
>
> Could you explain why do you think that WKT definition is the reason for
> your trouble with cascading WMS and what coordinates you need to switch?
> Cascading WMS is usually painless if user remembers that for WMS versions
> prior 1.3 the BBOX is expressed always in longitude-latitude /
> easting-northing order for all the projections.  In WMS 1.3 the official
> axis order is to be honoured. Could it be that you are cascading WMS 1.1.x
> and you make a wrong assumption that BBOX should be in lat-lon order? If
> that is the case, simply start cascading WMS 1.3.0.
>
>
> -Jukka Rahkonen-
>
>
>
>
> --
> *Lähettäjä:* Gavin Medley 
> *Lähetetty:* 1. elokuuta 2017 20:15
> *Vastaanottaja:* geoserver-users@lists.sourceforge.net
> *Aihe:* [Geoserver-users] EPSG:4326 Incorrect WKT - Coordinates Reversed!
>
> Hi all,
>
> I believe that the WKT for EPGS:4326 in Geoserver is incorrect. Can
> someone verify?
>
> Note the lat lon coordinate order in the following strings. Geoserver
> displays:
>
> GEOGCS["WGS 84",
> DATUM["World Geodetic System 1984",
> SPHEROID["WGS 84", 6378137.0, 298.257223563, AUTHORITY["EPSG","7030"]],
> AUTHORITY["EPSG","6326"]],
> PRIMEM["Greenwich", 0.0, AUTHORITY["EPSG","8901"]],
> UNIT["degree", 0.017453292519943295],
> AXIS["Geodetic longitude", EAST],
> AXIS["Geodetic latitude", NORTH],
> AUTHORITY["EPSG","4326"]]
>
> However, epsg-registry.org lists the official WKT as:
>
> GEODCRS["WGS 84",
>   DATUM["World Geodetic System 1984",
> ELLIPSOID["WGS 84",6378137,298.257223563,LENGTHUNIT["metre",1.0]]],
>   CS[ellipsoidal,2],
> AXIS["latitude",north,ORDER[1]],
> AXIS["longitude",east,ORDER[2]],
> ANGLEUNIT["degree",0.01745329252],
>   ID["EPSG",4326]]
>
> According to EPSG, latitude is FIRST. I'm using a cascading WMS (from
> another Geoserver) to put a map behind our GPS station locations and I had
> to switch all the coordinates to make the projections overlay correctly.
>
> -Gavin
>
> --
> Gavin Medley
> Software Engineer I
> *UNAVCO*
> 6350 Nautilus Drive
> Boulder, CO 80301-5394
> med...@unavco.org
>
>
>
> -- Forwarded message --
> From: Andrea Aime 
> To: Gavin Medley 
> Cc: Ian Turton , geoserver-users <
> geoserver-users@lists.sourceforge.net>
> Bcc:
> Date: Tue, 1 Aug 2017 22:49:11 +0200
> Subject: Re: [Geoserver-users] EPSG:4326 Incorrect WKT - Coordinates
> Reversed!
> On Tue, Aug 1, 2017 at 8:09 PM, Gavin Medley  wrote:
>
>> Hi,
>>
>> I'm using 1.1.0. Shouldn't the axis order be defined by the EPSG official
>> WKT string? Am I correct in thinking that order[1] and order[2] specify the
>> coordinate order?
>>
>
> OGC took its dear time to make things clear on this, WFS 1.1 happened
> midway when the axis order storm blew up (and I'm
> partially to blame cause I raised exactly your question, shouldn't WGS84
> be in lat/lon order?).
>
> When that happened everybody on the user side quietly assumed a "sane"
> "east/north" order for everything, in GeoServer we tried to
> keep both parties happy by adopting the following policy
>
> http://docs.geoserver.org/latest/en/user/services/wfs/
> basics.html#axis-ordering
>
> Basically, legacy naming, east/north, new naming, EPSG database suggested
> order instead.
> Deegree seems to have followed suit, https://github.com/
> deegree/deegree3/wiki/Axis-order-handling
>
> There is currently no way to get EPSG suggested axis order with the old
> EPSG:XYWZ syntax, nor any plan to add one
> (but with funding or contribution, that might still happen, as a
> configuration flag for those that want to impose strict behavior).
>
> Mind, the axis order issue is far from being solved, 

Re: [Geoserver-users] Limit to Number of Feature Chained Elements?

[Gavin Medley]

PS. Here is the geoserver.log tail from when I submitted the WFS request to
when I shut Geoserver down.

On Tue, Aug 15, 2017 at 11:46 AM, Gavin Medley  wrote:

> Hi again,
>
> I've been trying to nail down exactly when the "Duplicate mappingName or
> targetElement..." error occurs. I have two very specific cases, neither of
> which make sense to me (I don't see any reason to think that they should be
> invalid). I have attached three files here that I will reference; they are
> part of a larger app schema mapping structure. SLMSiteLog_Mapping.xml is
> the primary mapping file and includes many others under the 
> block including SLMSurveyedLocalTies_Mapping.xml and
> SLMRadioInterferences_Mapping.xml. The attached versions of these files
> are functional and don't raise errors but the following modifications both
> cause the above error. Case 1 and Case 2 occur independently.
>
> *Case 1:*
> Uncomment the following block in SLMSurveyedLocalTies_Mapping.xml. These
> AttributeMappings are all valid XPaths in the GeodesyML schema according to
> their documentation here
> <https://geoscienceaustralia.github.io/GeodesyML-Github-Pages/> and
> regardless, the error doesn't indicated any problem with the XPaths being
> valid. Moreover this block does not even contain a targetElement tag nor a
> mappingName tag at all. Any one of these three AttributeMapping blocks will
> independently cause the error if they are not commented out.
>
> 
> geo:localSiteTiesAccuracy
> 
> accuracym
> 
> 
> 
> geo:surveyMethod
> 
> surveymethod
> 
> 
> 
> geo:dateMeasured/gml:timePosition
> 
> datemeasured
> 
> 
>
> *Case 2:*
> Include the SLMRadioInterferences_Mapping.xml file in the feature chain.
> Doing this also produces the error, regardless of which AttributeMapping
> elements are used in the SLMRadioInterferences_Mapping.xml. This means
> uncommenting the following two pieces in SLMSiteLog_Mapping.xml:
>
> SLMRadioInterferences_Mapping.xml
>
> AND
>
> 
> geo:radioInterference
> 
> fourid
> geo:RadioInterference
> FEATURE_LINK[10]
> 
> true
> 
>
>
> Can you explain this behavior?
>
>
> On Mon, Aug 14, 2017 at 4:37 PM, Gavin Medley  wrote:
>
>> Hi Ben,
>>
>> Thanks! Geoserver starts without a hitch now. Unfortunately it seems this
>> was not the root cause of my problem. I am getting two errors, seemingly
>> without cause:
>>
>> Error creating app-schema data store for 'geo:RadioInterference', caused
>> by: No top level element found in schemas: {urn:xml-gov-au:icsm:egeodesy:
>> 0.4}RadioInterference
>>
>> Duplicate mappingName or targetElement across FeatureTypeMapping
>> instances detected.
>> I have been getting these errors since I first starting working with App
>> Schema and early on I presumed I had an error that I didn't understand and
>> fixed upon rewriting my mapping files. Now I'm not as sure. I say that they
>> happen "without cause" because without changing my mapping files in any
>> way, these errors usually go away after some combination of reloading the
>> feature types, restarting Geoserver, and recreating the app schema data
>> store (I emphasize that I recreate the data store with the *same*
>> mapping files!). I believe that if the error were simply suppressed,
>> everything would work because I know my mapping files are fine. They have
>> worked before!
>>
>> I found a possibly relevant bug here:
>> https://osgeo-org.atlassian.net/browse/GEOT-4196
>>
>> I'm happy to provide my mapping files but they are quite complex and
>> require the ability to connect to my local development database.
>>
>> Let me know what you think.
>>
>> On Mon, Aug 14, 2017 at 3:10 PM, Ben Caradoc-Davies 
>> wrote:
>>
>>> Gavin,
>>>
>>> you should not have to download anything, just move the postgresql jar
>>> included with GeoServer (in your case for 2.11.2 it is
>>> WEB-INF/lib/postgresql-9.4.1211.jar) to your Tomcat lib directory.
>>> GeoServer does not use the postgis jar from postgis.org. Leave
>>> everything else. The goal is to ensure that there is only one postgresql
>>> jar on your classpath. Tomcat does not need anything else because it only
>>> manages the connection and does not need to understand the content.
>>> Everything else stays in the GeoServer WEB-INF/lib.
>>> http://docs.geoserver.org/stable/en/user/tutorials/tomcat-jn
>>> di/tomcat-jndi.html#configuring-a-postgresql-connection-pool
>>>
>>> The latest version of the 

Re: [Geoserver-users] Limit to Number of Feature Chained Elements?

[Gavin Medley]

Hi again,

I've been trying to nail down exactly when the "Duplicate mappingName or
targetElement..." error occurs. I have two very specific cases, neither of
which make sense to me (I don't see any reason to think that they should be
invalid). I have attached three files here that I will reference; they are
part of a larger app schema mapping structure. SLMSiteLog_Mapping.xml is
the primary mapping file and includes many others under the 
block including SLMSurveyedLocalTies_Mapping.xml and
SLMRadioInterferences_Mapping.xml. The attached versions of these files are
functional and don't raise errors but the following modifications both
cause the above error. Case 1 and Case 2 occur independently.

*Case 1:*
Uncomment the following block in SLMSurveyedLocalTies_Mapping.xml. These
AttributeMappings are all valid XPaths in the GeodesyML schema according to
their documentation here
<https://geoscienceaustralia.github.io/GeodesyML-Github-Pages/> and
regardless, the error doesn't indicated any problem with the XPaths being
valid. Moreover this block does not even contain a targetElement tag nor a
mappingName tag at all. Any one of these three AttributeMapping blocks will
independently cause the error if they are not commented out.


geo:localSiteTiesAccuracy

accuracym



geo:surveyMethod

surveymethod



geo:dateMeasured/gml:timePosition

datemeasured



*Case 2:*
Include the SLMRadioInterferences_Mapping.xml file in the feature chain.
Doing this also produces the error, regardless of which AttributeMapping
elements are used in the SLMRadioInterferences_Mapping.xml. This means
uncommenting the following two pieces in SLMSiteLog_Mapping.xml:

SLMRadioInterferences_Mapping.xml

AND


geo:radioInterference

fourid
geo:RadioInterference
FEATURE_LINK[10]

true



Can you explain this behavior?


On Mon, Aug 14, 2017 at 4:37 PM, Gavin Medley  wrote:

> Hi Ben,
>
> Thanks! Geoserver starts without a hitch now. Unfortunately it seems this
> was not the root cause of my problem. I am getting two errors, seemingly
> without cause:
>
> Error creating app-schema data store for 'geo:RadioInterference', caused
> by: No top level element found in schemas: {urn:xml-gov-au:icsm:egeodesy:
> 0.4}RadioInterference
>
> Duplicate mappingName or targetElement across FeatureTypeMapping instances
> detected.
> I have been getting these errors since I first starting working with App
> Schema and early on I presumed I had an error that I didn't understand and
> fixed upon rewriting my mapping files. Now I'm not as sure. I say that they
> happen "without cause" because without changing my mapping files in any
> way, these errors usually go away after some combination of reloading the
> feature types, restarting Geoserver, and recreating the app schema data
> store (I emphasize that I recreate the data store with the *same* mapping
> files!). I believe that if the error were simply suppressed, everything
> would work because I know my mapping files are fine. They have worked
> before!
>
> I found a possibly relevant bug here:
> https://osgeo-org.atlassian.net/browse/GEOT-4196
>
> I'm happy to provide my mapping files but they are quite complex and
> require the ability to connect to my local development database.
>
> Let me know what you think.
>
> On Mon, Aug 14, 2017 at 3:10 PM, Ben Caradoc-Davies 
> wrote:
>
>> Gavin,
>>
>> you should not have to download anything, just move the postgresql jar
>> included with GeoServer (in your case for 2.11.2 it is
>> WEB-INF/lib/postgresql-9.4.1211.jar) to your Tomcat lib directory.
>> GeoServer does not use the postgis jar from postgis.org. Leave
>> everything else. The goal is to ensure that there is only one postgresql
>> jar on your classpath. Tomcat does not need anything else because it only
>> manages the connection and does not need to understand the content.
>> Everything else stays in the GeoServer WEB-INF/lib.
>> http://docs.geoserver.org/stable/en/user/tutorials/tomcat-jn
>> di/tomcat-jndi.html#configuring-a-postgresql-connection-pool
>>
>> The latest version of the postgresql driver should also work; if you want
>> to use it in your Tomcat lib, just remove WEB-INF/lib/postgresql-9.4.121
>> 1.jar.
>>
>> Kind regards,
>> Ben.
>>
>>
>>
>> On 15/08/17 04:45, Gavin Medley wrote:
>>
>>> Hi Ben,
>>>
>>> I'm finally getting to this but I think there must be missing information
>>> in the Geoserver documentation on this topic, especially in the context
>>> of
>>> App Schemas. I'm following the Postgres example here:
>>> http://docs.geoserver.org/stable/en/user/tutorials/tomcat-jn
>>> di/tomcat-jndi.html

Re: [Geoserver-users] CQL_Filter on App Schema Mapped Feature

[Gavin Medley]

Hi Ben,

Ah, that makes sense. I'm posting the working curl command and XML
GetFeature request for others who might be searching through the archives.

The following goes in a file called GetFeature.xml (for example):





geo:siteIdentification/geo:fourCharacterID






Use the following shell command to run the query using POST and store the
result in GetFeature_Result.xml:

curl -X POST -H "Content-type: application/gml+xml;version=3.2" -d
@GetFeature.xml http://localhost:8080/geoserver/wfs > GetFeature_Result.xml




On Mon, Aug 14, 2017 at 4:13 PM, Ben Caradoc-Davies 
wrote:

> Gavin,
>
> filter complex features by referencing xpath properties in the output. The
> client never needs to know about the source tables. app-schema converts the
> client filter into filters against the source tables, or efficient SQL join
> queries if joining is used.
>
> The cql_filter vendor parameter works fine for top-level properties like
> gml:name but I can find no way of encoding xpaths because "/" and "@" are
> invalid and not recognised as part of the property selector. In these cases
> you should be able to use filter (OGC Filter XML) rather than cql_filter.
>
> Kind regards,
> Ben.
>
> On 15/08/17 07:42, Gavin Medley wrote:
>
>> Hi all,
>>
>> How would one use a CQL_Filter parameter in a WFS request to filter the
>> results given by an app schema mapped complex feature using feature
>> chaining. The way I understand it, CQL_Filter operates using a WHERE
>> statement in a CQL query but how does that work when each (linked) mapping
>> file may be accessing a different table? Does the filter get applied to
>> the
>> top level mapping file? I haven't been able to make it work at all.
>> Perhaps
>> I'm totally misunderstanding it though.
>>
>>
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>>
>> ___
>> Geoserver-users mailing list
>>
>> Please make sure you read the following two resources before posting to
>> this list:
>> - Earning your support instead of buying it, but Ian Turton:
>> http://www.ianturton.com/talks/foss4g.html#/
>> - The GeoServer user list posting guidelines:
>> http://geoserver.org/comm/userlist-guidelines.html
>>
>> Geoserver-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>>
> --
> Ben Caradoc-Davies 
> Director
> Transient Software Limited <http://transient.nz/>
> New Zealand
>



-- 
Gavin Medley
Software Engineer I
*UNAVCO*
6350 Nautilus Drive
Boulder, CO 80301-5394
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Limit to Number of Feature Chained Elements?

[Gavin Medley]

Hi Ben,

Thanks! Geoserver starts without a hitch now. Unfortunately it seems this
was not the root cause of my problem. I am getting two errors, seemingly
without cause:

Error creating app-schema data store for 'geo:RadioInterference', caused
by: No top level element found in schemas:
{urn:xml-gov-au:icsm:egeodesy:0.4}RadioInterference

Duplicate mappingName or targetElement across FeatureTypeMapping instances
detected.
I have been getting these errors since I first starting working with App
Schema and early on I presumed I had an error that I didn't understand and
fixed upon rewriting my mapping files. Now I'm not as sure. I say that they
happen "without cause" because without changing my mapping files in any
way, these errors usually go away after some combination of reloading the
feature types, restarting Geoserver, and recreating the app schema data
store (I emphasize that I recreate the data store with the *same* mapping
files!). I believe that if the error were simply suppressed, everything
would work because I know my mapping files are fine. They have worked
before!

I found a possibly relevant bug here:
https://osgeo-org.atlassian.net/browse/GEOT-4196

I'm happy to provide my mapping files but they are quite complex and
require the ability to connect to my local development database.

Let me know what you think.

On Mon, Aug 14, 2017 at 3:10 PM, Ben Caradoc-Davies 
wrote:

> Gavin,
>
> you should not have to download anything, just move the postgresql jar
> included with GeoServer (in your case for 2.11.2 it is
> WEB-INF/lib/postgresql-9.4.1211.jar) to your Tomcat lib directory.
> GeoServer does not use the postgis jar from postgis.org. Leave everything
> else. The goal is to ensure that there is only one postgresql jar on your
> classpath. Tomcat does not need anything else because it only manages the
> connection and does not need to understand the content. Everything else
> stays in the GeoServer WEB-INF/lib.
> http://docs.geoserver.org/stable/en/user/tutorials/tomcat-
> jndi/tomcat-jndi.html#configuring-a-postgresql-connection-pool
>
> The latest version of the postgresql driver should also work; if you want
> to use it in your Tomcat lib, just remove WEB-INF/lib/postgresql-9.4.121
> 1.jar.
>
> Kind regards,
> Ben.
>
>
>
> On 15/08/17 04:45, Gavin Medley wrote:
>
>> Hi Ben,
>>
>> I'm finally getting to this but I think there must be missing information
>> in the Geoserver documentation on this topic, especially in the context of
>> App Schemas. I'm following the Postgres example here:
>> http://docs.geoserver.org/stable/en/user/tutorials/tomcat-
>> jndi/tomcat-jndi.html
>> but
>> have no luck. Geoserver won't start afterwards. I can revert to my
>> previous
>> configuration and everything is fine.
>>
>> Specifically, I'm not sure which .jar files to move to where. I am using a
>> PostGIS backend so I downloaded both the postgres and the postgis JDBC
>> drivers:
>>
>> postgis-jdbc-2.1.7.2.jar
>> postgresql-42.1.4.jar
>>
>> I understand that these (or possibly just one?) should go into
>> /Library/Tomcat/lib and that I should remove the duplicates (?) from
>> /Library/Tomcat/webapps/geoserver/WEB-INF/lib but I don't see any
>> duplicates in that directory. I have the following from ls *jdbc* :
>>
>> gs-sec-jdbc-2.11.2.jar
>> gt-jdbc-mysql-17.2.jar
>> spring-jdbc-4.2.5.RELEASE.jar
>> gs-web-sec-jdbc-2.11.2.jar
>> gt-jdbc-postgis-17.2.jar
>> gt-jdbc-17.2.jar
>> gwc-diskquota-jdbc-1.11.1.jar
>>
>> After these are in the right place with the correct duplicates are
>> removed,
>> I think my context.xml file should look like the following. Have I missed
>> replacing any placeholder values in any of these fields?
>>
>> 
>> 
>>  >auth="Container"
>>type="javax.sql.DataSource"
>>driverClassName="org.postgresql.Driver"
>>url="jdbc:postgresql://localhost:5432/slm"
>>username="ecelt-07" password=""
>>maxActive="100"
>>initialSize="0"
>>minIdle="0"
>>maxIdle="8"
>>maxWait="1"
>>timeBetweenEvictionRunsMillis="3"
>>minEvictableIdleTimeMillis="6"
>>testWhileIdle="true"
>>validationQuery="SELECT 1"
>>    maxAge="60"
>>rollbackOnReturn="true"
>>  />
>>  
>>  
>>  WEB-INF/web.xml
>>  ${catalina.

[Geoserver-users] CQL_Filter on App Schema Mapped Feature

[Gavin Medley]

Hi all,

How would one use a CQL_Filter parameter in a WFS request to filter the
results given by an app schema mapped complex feature using feature
chaining. The way I understand it, CQL_Filter operates using a WHERE
statement in a CQL query but how does that work when each (linked) mapping
file may be accessing a different table? Does the filter get applied to the
top level mapping file? I haven't been able to make it work at all. Perhaps
I'm totally misunderstanding it though.

-- 
Gavin Medley
Software Engineer I
*UNAVCO*
6350 Nautilus Drive
Boulder, CO 80301-5394
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Limit to Number of Feature Chained Elements?

[Gavin Medley]

Hi Ben,

I'm finally getting to this but I think there must be missing information
in the Geoserver documentation on this topic, especially in the context of
App Schemas. I'm following the Postgres example here:
http://docs.geoserver.org/stable/en/user/tutorials/tomcat-jndi/tomcat-jndi.html
but
have no luck. Geoserver won't start afterwards. I can revert to my previous
configuration and everything is fine.

Specifically, I'm not sure which .jar files to move to where. I am using a
PostGIS backend so I downloaded both the postgres and the postgis JDBC
drivers:

postgis-jdbc-2.1.7.2.jar
postgresql-42.1.4.jar

I understand that these (or possibly just one?) should go into
/Library/Tomcat/lib and that I should remove the duplicates (?) from
/Library/Tomcat/webapps/geoserver/WEB-INF/lib but I don't see any
duplicates in that directory. I have the following from ls *jdbc* :

gs-sec-jdbc-2.11.2.jar
gt-jdbc-mysql-17.2.jar
spring-jdbc-4.2.5.RELEASE.jar
gs-web-sec-jdbc-2.11.2.jar
gt-jdbc-postgis-17.2.jar
gt-jdbc-17.2.jar
gwc-diskquota-jdbc-1.11.1.jar

After these are in the right place with the correct duplicates are removed,
I think my context.xml file should look like the following. Have I missed
replacing any placeholder values in any of these fields?






WEB-INF/web.xml
${catalina.base}/conf/web.xml




Thanks for all your help!


On Fri, Aug 11, 2017 at 3:40 PM, Ben Caradoc-Davies 
wrote:

> Gavin,
>
> every source feature has its own connection pool. Use the same JNDI source
> for all source features to have them use a single pool that you can make as
> large as you like.
>
> The new functionality is in 2.11.2 and master so you should have it.
>
> Kind regards,
> Ben.
>
>
> On 12/08/17 06:37, Gavin Medley wrote:
>
>> Hi Ben,
>>
>> How does App Schema use the connections pool? Does it create a new
>> connection for each mapping file?
>>
>> I am running 2.11.2. Is the new development in the nightly build?
>>
>> On Thu, Aug 10, 2017 at 5:29 PM, Ben Caradoc-Davies 
>> wrote:
>>
>> Gavin,
>>>
>>> there is no limit in app-schema, but you might be hitting a limit in the
>>> size of the JDBC connection pool. You can increase this by using JNDI and
>>> configuring a larger number of connections.
>>>
>>> Very recent changes should improve app-schema connection usage:
>>>
>>> [GEOT-5748] Improve App-Schema connection usage
>>> https://osgeo-org.atlassian.net/browse/GEOT-5748
>>>
>>> What GeoServer version are you using?
>>>
>>> Kind regards,
>>> Ben.
>>>
>>> On 11/08/17 10:58, Gavin Medley wrote:
>>>
>>> Hi,
>>>>
>>>> Is there a limit to the number of feature chained elements possible in a
>>>> single feature? I have 10 mapping files, performing feature chaining and
>>>> each file maps between 4 and 10 elements. I've noticed that I don't seem
>>>> to
>>>> be able to go further. If I comment out a single  it
>>>> works but if I add one I get
>>>>
>>>> Duplicate mappingName or targetElement across FeatureTypeMapping
>>>> instances
>>>> detected.
>>>>
>>>> It doesn't seem to matter which  I change. It only
>>>> seems
>>>> to matter that there are too many. Is this possible?
>>>>
>>>> Cheers,
>>>>
>>>>
>>>>
>>>> 
>>>> --
>>>> Check out the vibrant tech community on one of the world's most
>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>
>>>>
>>>>
>>>> ___
>>>> Geoserver-users mailing list
>>>>
>>>> Please make sure you read the following two resources before posting to
>>>> this list:
>>>> - Earning your support instead of buying it, but Ian Turton:
>>>> http://www.ianturton.com/talks/foss4g.html#/
>>>> - The GeoServer user list posting guidelines:
>>>> http://geoserver.org/comm/userlist-guidelines.html
>>>>
>>>> Geoserver-users@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>>>
>>>>
>>>> --
>>> Ben Caradoc-Davies 
>>> Director
>>> Transient Software Limited <http://transient.nz/>
>>> New Zealand
>>>
>>>
>>
>>
>>
> --
> Ben Caradoc-Davies 
> Director
> Transient Software Limited <http://transient.nz/>
> New Zealand
>



-- 
Gavin Medley
Software Engineer I
*UNAVCO*
6350 Nautilus Drive
Boulder, CO 80301-5394
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Limit to Number of Feature Chained Elements?

[Gavin Medley]

Hi Ben,

How does App Schema use the connections pool? Does it create a new
connection for each mapping file?

I am running 2.11.2. Is the new development in the nightly build?

On Thu, Aug 10, 2017 at 5:29 PM, Ben Caradoc-Davies 
wrote:

> Gavin,
>
> there is no limit in app-schema, but you might be hitting a limit in the
> size of the JDBC connection pool. You can increase this by using JNDI and
> configuring a larger number of connections.
>
> Very recent changes should improve app-schema connection usage:
>
> [GEOT-5748] Improve App-Schema connection usage
> https://osgeo-org.atlassian.net/browse/GEOT-5748
>
> What GeoServer version are you using?
>
> Kind regards,
> Ben.
>
> On 11/08/17 10:58, Gavin Medley wrote:
>
>> Hi,
>>
>> Is there a limit to the number of feature chained elements possible in a
>> single feature? I have 10 mapping files, performing feature chaining and
>> each file maps between 4 and 10 elements. I've noticed that I don't seem
>> to
>> be able to go further. If I comment out a single  it
>> works but if I add one I get
>>
>> Duplicate mappingName or targetElement across FeatureTypeMapping instances
>> detected.
>>
>> It doesn't seem to matter which  I change. It only
>> seems
>> to matter that there are too many. Is this possible?
>>
>> Cheers,
>>
>>
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>>
>> ___
>> Geoserver-users mailing list
>>
>> Please make sure you read the following two resources before posting to
>> this list:
>> - Earning your support instead of buying it, but Ian Turton:
>> http://www.ianturton.com/talks/foss4g.html#/
>> - The GeoServer user list posting guidelines:
>> http://geoserver.org/comm/userlist-guidelines.html
>>
>> Geoserver-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>>
> --
> Ben Caradoc-Davies 
> Director
> Transient Software Limited <http://transient.nz/>
> New Zealand
>



-- 
Gavin Medley
Software Engineer I
*UNAVCO*
6350 Nautilus Drive
Boulder, CO 80301-5394
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] Limit to Number of Feature Chained Elements?

[Gavin Medley]

Hi,

Is there a limit to the number of feature chained elements possible in a
single feature? I have 10 mapping files, performing feature chaining and
each file maps between 4 and 10 elements. I've noticed that I don't seem to
be able to go further. If I comment out a single  it
works but if I add one I get

Duplicate mappingName or targetElement across FeatureTypeMapping instances
detected.

It doesn't seem to matter which  I change. It only seems
to matter that there are too many. Is this possible?

Cheers,

-- 
Gavin Medley
Software Engineer I
*UNAVCO*
6350 Nautilus Drive
Boulder, CO 80301-5394
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] AppSchema plugin, mapping simpleFeature with element having 0...N cardinality

[Gavin Medley]

Hi again,

I would like to add that I think this could be a bug in Geoserver's App
Schema. I frequently encounter this error when I'm working on my mapping
files (adding  tags for example) and the fix is almost
always restarting Geoserver, reloading the file used in the App Schema Data
Access, and reloading features in the layer you are working on. Magically
everything is fine and the mapping works again.


On Thu, Aug 10, 2017 at 11:09 AM, Gavin Medley  wrote:

> Hi,
>
> I experienced this error and it was the result of having an incorrect
> XPath to the element (therefore making Geoserver believe the element didn't
> exist). For example, if you are trying to map to an element
> gsml:myTarget
> which is contained in
> gsml:containingElement
> you have to specify the XPath like
> gsml:containingElement/gsml:myTarget
>
> If you are still having problems, it would be helpful to see your code.
>
>
> On Thu, Aug 10, 2017 at 2:42 AM, aquentin  wrote:
>
>> Hello,
>>
>> I'm trying to use app schema to expose a simple feature that have
>> attributes
>> with cardinality 0...N as :
>>
>> > maxOccurs="unbounded">
>> 
>>
>> In database, I create another table with foreign key in the main table.
>>
>> I tried to use feature link but an error raised "No top level element
>> found
>> in schemas". It shouldn't be the good manner to do mapping.
>>
>> Do you know how to do the mapping on this kind of element ?
>>
>> thank you
>> Regards.
>>
>>
>>
>> --
>> View this message in context: http://osgeo-org.1560.x6.nabbl
>> e.com/AppSchema-plugin-mapping-simpleFeature-with-element-
>> having-0-N-cardinality-tp5331073.html
>> Sent from the GeoServer - User mailing list archive at Nabble.com.
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> Geoserver-users mailing list
>>
>> Please make sure you read the following two resources before posting to
>> this list:
>> - Earning your support instead of buying it, but Ian Turton:
>> http://www.ianturton.com/talks/foss4g.html#/
>> - The GeoServer user list posting guidelines:
>> http://geoserver.org/comm/userlist-guidelines.html
>>
>> Geoserver-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>
>
>
> --
> Gavin Medley
> Software Engineer I
> *UNAVCO*
> 6350 Nautilus Drive
> Boulder, CO 80301-5394
> med...@unavco.org
>
>


-- 
Gavin Medley
Software Engineer I
*UNAVCO*
6350 Nautilus Drive
Boulder, CO 80301-5394
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Mapping Multiple Tables in One Mapping File

[Gavin Medley]

Thank you! That answers my question. We need to work on the database.

On Tue, Aug 8, 2017 at 3:32 PM, Ben Caradoc-Davies  wrote:

> On 09/08/17 04:52, Gavin Medley wrote:
>
>> I have the data for siteName and iersDOMESNumber in Table1 and the data
>> for
>> monumentDescription and heightOfTheMonument in Table2. Can I use a single
>> XML mapping file to map those two tables to the elements of
>> siteIdentification?
>>
>
> No, there is a one-to-one relationship between a feature type and the
> database relation that provides its identity.
>
> The two workarounds that I have considered are 1) Making a new
>> feature-chained mapping file for each element that needs to be mapped
>> (ugh!) or 2) making a new view or table to bring in any data that needs to
>> be mapped to the same level of the XML schema.
>> What would you suggest?
>>
>
> If the attributes are single-valued, then a database view or table is an
> excellent solution: fast and simple. This is also an opportunity to use
> fast database-side string concatenation to construct identifiers such as
> gml:id or HTTP URIs. You can even index them for performance.
>
> Kind regards,
>
> --
> Ben Caradoc-Davies 
> Director
> Transient Software Limited <http://transient.nz/>
> New Zealand
>



-- 
Gavin Medley
Software Engineer I
*UNAVCO*
6350 Nautilus Drive
Boulder, CO 80301-5394
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] AppSchema plugin, mapping simpleFeature with element having 0...N cardinality

[Gavin Medley]

Hi,

I experienced this error and it was the result of having an incorrect XPath
to the element (therefore making Geoserver believe the element didn't
exist). For example, if you are trying to map to an element
gsml:myTarget
which is contained in
gsml:containingElement
you have to specify the XPath like
gsml:containingElement/gsml:myTarget

If you are still having problems, it would be helpful to see your code.


On Thu, Aug 10, 2017 at 2:42 AM, aquentin  wrote:

> Hello,
>
> I'm trying to use app schema to expose a simple feature that have
> attributes
> with cardinality 0...N as :
>
>  maxOccurs="unbounded">
> 
>
> In database, I create another table with foreign key in the main table.
>
> I tried to use feature link but an error raised "No top level element found
> in schemas". It shouldn't be the good manner to do mapping.
>
> Do you know how to do the mapping on this kind of element ?
>
> thank you
> Regards.
>
>
>
> --
> View this message in context: http://osgeo-org.1560.x6.
> nabble.com/AppSchema-plugin-mapping-simpleFeature-with-element-having-0-N-
> cardinality-tp5331073.html
> Sent from the GeoServer - User mailing list archive at Nabble.com.
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines: http://geoserver.org/comm/
> userlist-guidelines.html
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>



-- 
Gavin Medley
Software Engineer I
*UNAVCO*
6350 Nautilus Drive
Boulder, CO 80301-5394
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] feature frenzy - any requests?

[Gavin Medley]

Hi Jody,

First, a "wow" moment. At UNAVCO, we are experimenting with a new way to
compose GNSS site logs. We have a Geoserver connected to our database and
we have successfully mapped most of our site log data into the foriegn
GeodesyML schema using the App Schema extension for Geoserver. There are
still issues (mostly with datatypes) but it works! We are on our way to
being able to distribute entire sitelogs via WFS requests in GeodesyML
format!

Second, a request: it would be great to have support for 3D CRSs. PostGIS
Point can take up to a 3D (actually it can do 4D too) coordinate and
Geoserver could do the same. In particular we use EPSG:4978 (cartesian
Earth centered Earth fixed XYZ) along with 4326. I'm not sure how this
would work with OpenLayers (Cesium can do 3D maps?) but just recognizing 3D
Postgis geometries in features would be a great start!

Cheers,


On Sun, Aug 6, 2017 at 6:03 PM, Jody Garnett  wrote:

> We have a "geoserver feature frenzy" presentation coming up at foss4g.
> Last time we asked the user list what features they found the most valuable
> (and had some surprises like the number of people who found the oracle
> database support vital).
>
> This year I would like to cast a wider net - please help out by sharing
> any "wow I did not know geoserver could do that" experiences!
> --
> Jody Garnett
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines: http://geoserver.org/comm/
> userlist-guidelines.html
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>


-- 
Gavin Medley
Software Engineer I
*UNAVCO*
6350 Nautilus Drive
Boulder, CO 80301-5394
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] Mapping Multiple Tables in One Mapping File

[Gavin Medley]

Hi all,

I am faced with a problem. I am mapping a database of site logs to
GeodesyML through Geoserver App Schema. I am trying to minimize the number
of new views and tables I need to make in the database so I was wondering
if it is possible to use a single mapping file to map multiple views or
tables to fields contained in a single XML element.

e.g. the XML schema is of the form

The Site
42
This is a monument...
1m


I have the data for siteName and iersDOMESNumber in Table1 and the data for
monumentDescription and heightOfTheMonument in Table2. Can I use a single
XML mapping file to map those two tables to the elements of
siteIdentification?

The two workarounds that I have considered are 1) Making a new
feature-chained mapping file for each element that needs to be mapped
(ugh!) or 2) making a new view or table to bring in any data that needs to
be mapped to the same level of the XML schema.

What would you suggest?

Many thanks!

-- 
Gavin Medley
Software Engineer I
*UNAVCO*
6350 Nautilus Drive
Boulder, CO 80301-5394
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] EPSG:4326 Incorrect WKT - Coordinates Reversed!

[Gavin Medley]

Hi,

I'm using 1.1.0. Shouldn't the axis order be defined by the EPSG official
WKT string? Am I correct in thinking that order[1] and order[2] specify the
coordinate order?

-Gavin

On Tue, Aug 1, 2017 at 11:57 AM, Ian Turton  wrote:

> Epsg:4326 axis order is a complex topic. Are you using WMS 1.0 or 1.1.0
> for your cascading? The axis order changes between the two versions.
>
> Ian
>
> On 1 Aug 2017 18:18, "Gavin Medley"  wrote:
>
> Hi all,
>
> I believe that the WKT for EPGS:4326 in Geoserver is incorrect. Can
> someone verify?
>
> Note the lat lon coordinate order in the following strings. Geoserver
> displays:
>
> GEOGCS["WGS 84",
> DATUM["World Geodetic System 1984",
> SPHEROID["WGS 84", 6378137.0, 298.257223563, AUTHORITY["EPSG","7030"]],
> AUTHORITY["EPSG","6326"]],
> PRIMEM["Greenwich", 0.0, AUTHORITY["EPSG","8901"]],
> UNIT["degree", 0.017453292519943295],
> AXIS["Geodetic longitude", EAST],
> AXIS["Geodetic latitude", NORTH],
> AUTHORITY["EPSG","4326"]]
>
> However, epsg-registry.org lists the official WKT as:
>
> GEODCRS["WGS 84",
>   DATUM["World Geodetic System 1984",
> ELLIPSOID["WGS 84",6378137,298.257223563,LENGTHUNIT["metre",1.0]]],
>   CS[ellipsoidal,2],
> AXIS["latitude",north,ORDER[1]],
> AXIS["longitude",east,ORDER[2]],
> ANGLEUNIT["degree",0.01745329252],
>   ID["EPSG",4326]]
>
> According to EPSG, latitude is FIRST. I'm using a cascading WMS (from
> another Geoserver) to put a map behind our GPS station locations and I had
> to switch all the coordinates to make the projections overlay correctly.
>
> -Gavin
>
> --
> Gavin Medley
> Software Engineer I
> *UNAVCO*
> 6350 Nautilus Drive
> Boulder, CO 80301-5394
> med...@unavco.org
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
>


-- 
Gavin Medley
Software Engineer I
*UNAVCO*
6350 Nautilus Drive
Boulder, CO 80301-5394
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] EPSG:4326 Incorrect WKT - Coordinates Reversed!

[Gavin Medley]

Hi all,

I believe that the WKT for EPGS:4326 in Geoserver is incorrect. Can someone
verify?

Note the lat lon coordinate order in the following strings. Geoserver
displays:

GEOGCS["WGS 84",
DATUM["World Geodetic System 1984",
SPHEROID["WGS 84", 6378137.0, 298.257223563, AUTHORITY["EPSG","7030"]],
AUTHORITY["EPSG","6326"]],
PRIMEM["Greenwich", 0.0, AUTHORITY["EPSG","8901"]],
UNIT["degree", 0.017453292519943295],
AXIS["Geodetic longitude", EAST],
AXIS["Geodetic latitude", NORTH],
AUTHORITY["EPSG","4326"]]

However, epsg-registry.org lists the official WKT as:

GEODCRS["WGS 84",
  DATUM["World Geodetic System 1984",
ELLIPSOID["WGS 84",6378137,298.257223563,LENGTHUNIT["metre",1.0]]],
  CS[ellipsoidal,2],
AXIS["latitude",north,ORDER[1]],
AXIS["longitude",east,ORDER[2]],
ANGLEUNIT["degree",0.01745329252],
  ID["EPSG",4326]]

According to EPSG, latitude is FIRST. I'm using a cascading WMS (from
another Geoserver) to put a map behind our GPS station locations and I had
to switch all the coordinates to make the projections overlay correctly.

-Gavin

-- 
Gavin Medley
Software Engineer I
*UNAVCO*
6350 Nautilus Drive
Boulder, CO 80301-5394
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] WFS Request Namespace Inconsistency?

[Gavin Medley]

Hi Ben,

We added the secondary namespace and all is well. Very interesting that it
affected GetFeature but not GetPropertyValue.

Thanks!

-Gavin

On Fri, Jul 28, 2017 at 6:14 PM, Ben Caradoc-Davies 
wrote:

> Gavin,
>
> both of these problems are likely caused by the lack of a secondary
> namespace.
>
> I saw the difference in encoding (the xmlns on the non-root element),
> which is odd. Incremental improvements might have changed the manifestation
> of the problem (no longer an exception), and implementation differences
> might explain the difference between the two requests. Time for a
> documentation update.
>
> Please add a secondary namespace gml for GML 3.2.1 and report back. Any
> further app-schema misbehaviour is likely a bug.
>
> Kind regards,
> Ben.
>
>
> On 29/07/17 11:24, Gavin Medley wrote:
>
>> Hi Ben,
>>
>> That's probably what it is. I don't have a secondary namespace for gml.
>> Weird that it's not throwing an error when encoding the response.
>>
>> With respect to your second question, we do see wfs:FeatureCollection and
>> wfs:ValueCollection when using App Schema. However, in the
>> wfs:FeatureCollection, we are missing the namespace definition for gml. In
>> wfs:ValueCollection we see
>> xmlns:gml="http://www.opengis.net/gml/3.2";
>> Do you think this is likely due to the lack of secondary namespace?
>>
>>
>> -Gavin
>>
>> On Fri, Jul 28, 2017 at 4:57 PM, Ben Caradoc-Davies 
>> wrote:
>>
>> Gavin,
>>>
>>> that is very interesting. My guess is that the different response root
>>> elements end up with different namespace configurations being provided to
>>> the GeoTools encoder.
>>>
>>> Have you defined a secondary namespace for the gml prefix?
>>> http://docs.geoserver.org/latest/en/user/data/app-schema/
>>> supported-gml-versions.html#secondary-namespace-for-gml-3-2-1-required
>>>
>>> A secondary namespace was not required for GML 3.1.1 application schemas
>>> because WFS 1.1.0 was defined in terms of GML 3.1.1. WFS 2.0.0 is
>>> GML-version-agnostic, so the encoder no longer has a namespace prefix
>>> binding to use.
>>>
>>> GetFeature responses have a root element of wfs:FeatureCollection.
>>> GetPropertyValue responses have a root element of wfs:ValueCollection. Do
>>> you see these with app-schema?
>>>
>>> Kind regards,
>>> Ben.
>>>
>>> On 29/07/17 10:05, Gavin Medley wrote:
>>>
>>> Hi,
>>>>
>>>> I think this is a bug, probably in App Schema, but I want to ensure I'm
>>>> not
>>>> doing something wrong before filing a report. I am using App Schema to
>>>> output GeodesyML for WFS requests. I noticed recently that Geoserver
>>>> fails
>>>> to resolve one of my namespaces in GetFeature requests. This confused me
>>>> because in the past it wasn't a problem. Now I am further confused
>>>> because
>>>> in GetPropertyValue requests it resolves again! How can one WFS request
>>>> fail to resolve a namespace but another succeeds? To be clear these are
>>>> back to back requests with zero change to mapping files or any other
>>>> configuration.
>>>>
>>>> *Specifics:*
>>>>
>>>> http://host:port/geoserver/ows?
>>>> service=WFS&
>>>> version=2.0.0&
>>>> request=*GetFeature*&
>>>> typeNames=geo:siteLog&
>>>> outputFormat=gml32&
>>>> count=10
>>>>
>>>> *results in*
>>>>
>>>> 
>>>> Nepal
>>>> Eurasia
>>>> 
>>>> 
>>>> <*null:Point* xmlns:null="http://www.opengis.net/gml/3.2"; id="
>>>> cartesian.geoml_monuments.fid--1f0f9389_15d8afee8b4_-4128"/>
>>>> 
>>>> 
>>>> <*null:Point* xmlns:null="http://www.opengis.net/gml/3.2"; id="
>>>> latlon.geoml_monuments.fid--1f0f9389_15d8afee8b4_-4128"/>
>>>> 
>>>> 
>>>> 
>>>>
>>>> *BUT*
>>>>
>>>> http://ws-beta.int.unavco.org:9090/geoserver/wfs?
>>>> service=wfs&
>>>> version=2.0.0&
>>>> request=*GetPropertyValue*&
>>>> typeNames=geo:siteLog&
>>>> valueReference=geo:siteLocation&
>>>> count=10
>>>>
>>>> *results in*
>>>>
>

Re: [Geoserver-users] WFS Request Namespace Inconsistency?

[Gavin Medley]

Hi Ben,

That's probably what it is. I don't have a secondary namespace for gml.
Weird that it's not throwing an error when encoding the response.

With respect to your second question, we do see wfs:FeatureCollection and
wfs:ValueCollection when using App Schema. However, in the
wfs:FeatureCollection, we are missing the namespace definition for gml. In
wfs:ValueCollection we see
xmlns:gml="http://www.opengis.net/gml/3.2";
Do you think this is likely due to the lack of secondary namespace?


-Gavin

On Fri, Jul 28, 2017 at 4:57 PM, Ben Caradoc-Davies 
wrote:

> Gavin,
>
> that is very interesting. My guess is that the different response root
> elements end up with different namespace configurations being provided to
> the GeoTools encoder.
>
> Have you defined a secondary namespace for the gml prefix?
> http://docs.geoserver.org/latest/en/user/data/app-schema/
> supported-gml-versions.html#secondary-namespace-for-gml-3-2-1-required
>
> A secondary namespace was not required for GML 3.1.1 application schemas
> because WFS 1.1.0 was defined in terms of GML 3.1.1. WFS 2.0.0 is
> GML-version-agnostic, so the encoder no longer has a namespace prefix
> binding to use.
>
> GetFeature responses have a root element of wfs:FeatureCollection.
> GetPropertyValue responses have a root element of wfs:ValueCollection. Do
> you see these with app-schema?
>
> Kind regards,
> Ben.
>
> On 29/07/17 10:05, Gavin Medley wrote:
>
>> Hi,
>>
>> I think this is a bug, probably in App Schema, but I want to ensure I'm
>> not
>> doing something wrong before filing a report. I am using App Schema to
>> output GeodesyML for WFS requests. I noticed recently that Geoserver fails
>> to resolve one of my namespaces in GetFeature requests. This confused me
>> because in the past it wasn't a problem. Now I am further confused because
>> in GetPropertyValue requests it resolves again! How can one WFS request
>> fail to resolve a namespace but another succeeds? To be clear these are
>> back to back requests with zero change to mapping files or any other
>> configuration.
>>
>> *Specifics:*
>>
>> http://host:port/geoserver/ows?
>> service=WFS&
>> version=2.0.0&
>> request=*GetFeature*&
>> typeNames=geo:siteLog&
>> outputFormat=gml32&
>> count=10
>>
>> *results in*
>>
>> 
>> Nepal
>> Eurasia
>> 
>> 
>> <*null:Point* xmlns:null="http://www.opengis.net/gml/3.2"; id="
>> cartesian.geoml_monuments.fid--1f0f9389_15d8afee8b4_-4128"/>
>> 
>> 
>> <*null:Point* xmlns:null="http://www.opengis.net/gml/3.2"; id="
>> latlon.geoml_monuments.fid--1f0f9389_15d8afee8b4_-4128"/>
>> 
>> 
>> 
>>
>> *BUT*
>>
>> http://ws-beta.int.unavco.org:9090/geoserver/wfs?
>> service=wfs&
>> version=2.0.0&
>> request=*GetPropertyValue*&
>> typeNames=geo:siteLog&
>> valueReference=geo:siteLocation&
>> count=10
>>
>> *results in*
>>
>> 
>> Nepal
>> Eurasia
>> 
>> 
>> <*gml:Point* gml:id="
>> cartesian.geoml_monuments.fid--1f0f9389_15d8afee8b4_-40bc"/>
>> 
>> 
>> <*gml:Point* gml:id="latlon.geoml_monuments.fid--1f0f9389_15d8afee8b4_-
>> 40bc"
>> />
>> 
>> 
>> 
>>
>>
>> Many thanks,
>>
>>
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>>
>> ___
>> Geoserver-users mailing list
>>
>> Please make sure you read the following two resources before posting to
>> this list:
>> - Earning your support instead of buying it, but Ian Turton:
>> http://www.ianturton.com/talks/foss4g.html#/
>> - The GeoServer user list posting guidelines:
>> http://geoserver.org/comm/userlist-guidelines.html
>>
>> Geoserver-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>>
> --
> Ben Caradoc-Davies 
> Director
> Transient Software Limited <http://transient.nz/>
> New Zealand
>



-- 
Gavin Medley
Software Engineer I
*UNAVCO*
6350 Nautilus Drive
Boulder, CO 80301-5394
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] WFS Request Namespace Inconsistency?

[Gavin Medley]

Hi,

I think this is a bug, probably in App Schema, but I want to ensure I'm not
doing something wrong before filing a report. I am using App Schema to
output GeodesyML for WFS requests. I noticed recently that Geoserver fails
to resolve one of my namespaces in GetFeature requests. This confused me
because in the past it wasn't a problem. Now I am further confused because
in GetPropertyValue requests it resolves again! How can one WFS request
fail to resolve a namespace but another succeeds? To be clear these are
back to back requests with zero change to mapping files or any other
configuration.

*Specifics:*

http://host:port/geoserver/ows?
service=WFS&
version=2.0.0&
request=*GetFeature*&
typeNames=geo:siteLog&
outputFormat=gml32&
count=10

*results in*


Nepal
Eurasia


<*null:Point* xmlns:null="http://www.opengis.net/gml/3.2"; id="
cartesian.geoml_monuments.fid--1f0f9389_15d8afee8b4_-4128"/>


<*null:Point* xmlns:null="http://www.opengis.net/gml/3.2"; id="
latlon.geoml_monuments.fid--1f0f9389_15d8afee8b4_-4128"/>




*BUT*

http://ws-beta.int.unavco.org:9090/geoserver/wfs?
service=wfs&
version=2.0.0&
request=*GetPropertyValue*&
typeNames=geo:siteLog&
valueReference=geo:siteLocation&
count=10

*results in*


Nepal
Eurasia


<*gml:Point* gml:id="
cartesian.geoml_monuments.fid--1f0f9389_15d8afee8b4_-40bc"/>


<*gml:Point* gml:id="latlon.geoml_monuments.fid--1f0f9389_15d8afee8b4_-40bc"
/>





Many thanks,

-- 
Gavin Medley
Software Engineer I
*UNAVCO*
6350 Nautilus Drive
Boulder, CO 80301-5394
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] App-Schema Mapping File to GeodesyML

[Gavin Medley]

t in the GeodesyML
>>>> schema, outlined  here
>>>> <https://geoscienceaustralia.github.io/GeodesyML-Github-Pages/>  . In
>>>> particular, I am working with GPS monument meta data. For now I'm trying
>>>>
>>> to
>>>
>>>> just output the siteName in GeodesyML schema when I click GML in the
>>>>
>>> Layers
>>>
>>>> Preview in Geoserver. The relevant XML schema definition file for
>>>>
>>> GeodesyML
>>>
>>>> is called monumentInfo.xsd. Unfortunately, I can't seem to get the
>>>>
>>> mapping
>>>
>>>> correct from my database schema to GeodesyML. In particular I think the
>>>> problem is in the  or  fields within
>>>> . I concluded that I should use geo:GeodesyML as the
>>>> argument to schemaUri because it is the only xsd file with a top level
>>>> element (type GeodesyMLType).
>>>>
>>>> How can I use the schema outlined in the monumentInfo.xsd schema
>>>>
>>> definition?
>>>
>>>> Specifically here, how can I map site_name in my database schema to
>>>>
>>> siteName
>>>
>>>> in the GeodesyML schema?
>>>>
>>>> Any help is sincerely appreciated and I apologize if my lack of
>>>>
>>> familiarity
>>>
>>>> with XML is causing me to ask a silly question. I have done a fair bit
>>>>
>>> of
>>>
>>>> Google research. The tutorial I followed to get this far is  here
>>>> <http://docs.geoserver.org/latest/en/user/data/app-schema/tutorial.html
>>>> >
>>>>
>>>   ,
>>>
>>>> with supporting documentation  here
>>>> <http://docs.geoserver.org/stable/en/user/data/app-
>>>>
>>> schema/mapping-file.html>
>>>
>>>> but they are using GeoscienceML, not GeodesyML.
>>>>
>>>> -Gavin Medley
>>>>
>>>>
>>>> *The view I am querying, called geoml_monuments contains:*
>>>> id | station_code | site_name | geolocation | iers_domex | country_name
>>>> I am pretty sure this is fine.
>>>>
>>>>
>>>>
>>>> *The monumentsInfo.xsd file:*
>>>> https://github.com/GeoscienceAustralia/GeodesyML/blob/master/schemas/
>>>>
>>> monumentInfo.xsd
>>>
>>>> <https://github.com/GeoscienceAustralia/GeodesyML/blob/master/schemas/
>>>>
>>> monumentInfo.xsd>
>>>
>>>>
>>>>
>>>>
>>>> *The GeodesyML.xsd file:*
>>>> https://github.com/GeoscienceAustralia/GeodesyML/
>>>>
>>> blob/master/schemas/geodesyML.xsd
>>>
>>>> <https://github.com/GeoscienceAustralia/GeodesyML/
>>>>
>>> blob/master/schemas/geodesyML.xsd>
>>>
>>>>
>>>>
>>>>
>>>>
>>>> *My mapping file:*
>>>>
>>>>
>>>>
>>>> 
>>>> >>> xmlns:as="http://www.geotools.org/app-schema";
>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>>>> xsi:schemaLocation="http://www.geotools.org/app-schema
>>>> AppSchemaDataAccess.xsd">
>>>> 
>>>> 
>>>> geo
>>>> urn:xml-gov-au:icsm:egeodesy:0.4
>>>> 
>>>> 
>>>> gml
>>>> http://www.opengis.net/gml/3.2
>>>> 
>>>> 
>>>> gmd
>>>> http://www.isotc211.org/2005/gmd
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> thedb
>>>> 
>>>> 
>>>> dbtype
>>>> postgisng
>>>> 
>>>> 
>>>> host
>>>> thedatabaselocation.unavco.org
>>>> 
>>>> 
>>>> port
>>>> 5432
>>>> 
>>>> 
>>>> database
>>>> tst3
>>>> 
>>>> 
>>>> user
>>>> theuser
>>>> 
>>>> 
>>>> passwd
>>>> thepassword
>>>> 
>>>> 
>>>

[Geoserver-users] Updating an App Schema Data Store via REST

[Gavin Medley]

Hi,

Has anyone implemented an App Schema Data Store (such as a Postgres
database) to be updated via REST? I would love a working example of how you
import data.

More ambitiously, we actually map our Postgres schema to the GeodesyML
schema for WFS requests (using several feature-chained app schema mapping
files). Is it possible to upload data in GeodesyML via REST and have
Geoserver "reverse map" the data back into Postgres during the REST import
so that we can allow database updates through Geoserver?

Documentation, working code, examples, or just discussion is much
appreciated.

Cheers,

Gavin



-- 
Gavin Medley
USIP Intern
med...@unavco.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users