Re: [Geoserver-users] xlink:ref not well encoded in WFS response (app schema)

Hi Christy, I raised a JIRA issue here: https://jira.codehaus.org/browse/GEOT-4894 I will try my best to have a look this month, and see if the issue is related with xlink. Cheers Rini -- View this message in context:

Re: [Geoserver-users] app-schema and a mapping to generate xlink:href or xsi:nil on the same element

This is a bug in ReferenceTypeBinding (the type for eventProcess). I have submitted a fix in https://jira.codehaus.org/browse/GEOT-4757. Cheers Rini -- View this message in context:

Re: [Geoserver-users] Complex features and WMS

OK this looks like a bug.. Please create a JIRA issue with your configuration attached (SLD style, mapping file) - it would make it a lot faster to unit test and fix. -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Complex-features-and-WMS-tp5129235p5130043.html Sent

Re: [Geoserver-users] Complex features and WMS

Interesting, NamedPlace extends gml:AbstractFeatureType, so it should be treated as a feature type. Do you have layer.xml set up? -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Complex-features-and-WMS-tp5129235p5129592.html Sent from the GeoServer - User mailing list

Re: [Geoserver-users] Complex features and WMS

Can you attach the stack trace as well? -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Complex-features-and-WMS-tp5129235p5129593.html Sent from the GeoServer - User mailing list archive at Nabble.com.

Re: [Geoserver-users] Complex features and WMS

NonFeatureTypeProxy is used when the complex type used is not a GML Feature type, e.g. a data type. Which type in the schema are you trying to use exactly? Having said that, we should be flexible enough to let users publish anything.. so it's a bug specific to non GML Feature types. -- View

Re: [Geoserver-users] App-Schema encodeIfEmpty

It's probably just the ordering that's wrong. It should be just before ClientProperty, or the last one if you do'nt have ClientProperty. https://github.com/geotools/geotools/blob/master/modules/extension/app-schema/app-schema/src/test/resources/test-data/AppSchemaDataAccess.xsd -- View this

Re: [Geoserver-users] App-Schema and Join Tables

Hi Marcus and Ryan, It is now possible to feature-chain simple properties, as seen in the unit test here: https://github.com/geoserver/geoserver/blob/master/src/extension/app-schema/app-schema-test/src/test/resources/test-data/SimpleAttributeFeatureChainTest.xml. This eliminates the need for

Re: [Geoserver-users] App-Schema plugin (2.4.1), mapping the AdministrativUnit model of INSPIRE

Sounds related to a bug I recently introduced and fixed only in trunk because it was too late for the 2.4.1 release. I'll commit it for 2.4.2 soon. The workaround I believe is to specify idExpression for your mapping type. -- View this message in context:

Re: [Geoserver-users] App-schema feature linkage issue

Try adding an element of property type in your schema: xs:element name=gmd:MD_Metadata type=gmd:MD_Metadata_PropertyType/ And update your EmployeeType accordingly: complexType name=EmployeeType complexContent extension base=company:PersonType

Re: [Geoserver-users] App-Schema: Inheritance question

Hi snuffy, The joining work is legacy of Niels Charlier during his time with our organisation, so I may not be 100% correct. From my understanding, this is because the same rows from the linked table could be chained by multiple parents from the main table. Therefore the parent id is needed as

Re: [Geoserver-users] OpenLayers with App-Schemas

Hi Christy, Apart from Ben's suggestions, I also made a very recent bug fix relating to WMS with app-schema: https://jira.codehaus.org/browse/GEOT-4550. Please try the latest from trunk if you're not already using it. Cheers Rini -- View this message in context:

Re: [Geoserver-users] app-schema tries to access non-existent objectid column

Hi Marcus, Looks like a bug and I think I have an idea how to fix it. I'll have a look next week. https://jira.codehaus.org/browse/GEOT-4553 Cheers Rini -- View this message in context:

Re: [Geoserver-users] app-schema error with schemas in class path

Hi Marcus, I've had similar problem when an imported schema is missing. I wonder which schemaURI you're using? If you're using https://www.seegrid.csiro.au/subversion/GeoSciML/branches/3.2.0/schemas/geologicunit/3.2/geologicUnit.xsd; in the schemaURI, you need to also specify a second schemaURI

Re: [Geoserver-users] Performance issue with App-schema

Hi Eero, Geoff Williams is working on a solution for this issue, and I believe he is close to finishing. Watch this issue: https://jira.codehaus.org/browse/GEOT-4510 Cheers Rini -- View this message in context:

Re: [Geoserver-users] app-schema and gazetteer

Hi Gianni, There's been a lot of bug fixes recently to support joining with feature chaining. Also, make sure you're not using functions (including getID()) in your idExpression inside your mapping files, but point directly to the database id columns instead. I'm wondering which version you're

Re: [Geoserver-users] app-schema query fails with org.geotools.feature.NameImpl cannot be cast to org.opengis.feature.type.AttributeDescriptor

Hi Marcus, This is a bug indeed. I have raised it here: https://jira.codehaus.org/browse/GEOT-4471. The bug only occurs when filtering by xpath attributes with types (i.e. gsml:MappedFeature) that has a geometry attribute with native CRS (from the database), i.e. gsml:shape. It doesn't occur with

Re: [Geoserver-users] App-schema not working with joining=true

Hi Miguel, I was able to recreate the same problem reported earlier (http://jira.codehaus.org/browse/GEOS-5618). The problem in the JIRA issue was because of getID() not being handled properly with joining. The bug wasn't detected because all the joining unit tests aren't using getID() anymore,

Re: [Geoserver-users] xlink:ref not well encoded in WFS response (app schema)

Hi Florent, App-schema doesn't support WFS 2.0.0, however you can use WFS 1.1.0 with GML 3.2 by specifying outputFormat=gml32 and version=1.1.0. With gml 3.2, you need to specify secondary namespaces in a separate namespace.xml and workspace.xml as shown in

Re: [Geoserver-users] app-schema: WFS-request, sortBy not evaluated

Hi, I am afraid sortBy is not supported in app-schema yet. Cheers Rini -- View this message in context: http://osgeo-org.1560.n6.nabble.com/app-schema-WFS-request-sortBy-not-evaluated-tp4996945p4997222.html Sent from the GeoServer - User mailing list archive at Nabble.com.

Re: [Geoserver-users] app-schema: WFS-request, sortBy not evaluated

App-schema streams from the database without sorting. If your data is indexed, it will be sorted by the index. Otherwise the order could be random depending on how the database returns the data. I have raised a JIRA issue for this: https://jira.codehaus.org/browse/GEOT-4241, however we are a bit

Re: [Geoserver-users] [ExternalEmail] Re: app-schema WMS

I was looking at this today. It's a bug in SLDParser (not setting namespace context when parsing Geometry in parseGeometry). It should set namespace context like it does when parsing filter (parseFilter). Workaround is to omit namespaces in sld:Geometry/ogc:PropertyName i.e.

Re: [Geoserver-users] App-Schemas and Feature Chaining (Updated)

Hi Shaw, I am guessing namespace.xml has http://sidelab:Locality in the uri. If that's the case, you should change it to http://sidelab, and it should work. If it's not that, it must be something in one of the config files (featuretype.xml etc.) that causes the feature type name to be built

Re: [Geoserver-users] app-schema mapping geometry column in PostGIS

Interesting. There was a bug similar like this, but it was specific to SQLServer using sqljdbc 3.0. I wonder if it was also affecting PostGIS.. The bug was fixed late September, so should be fixed in the latest release. http://jira.codehaus.org/browse/GEOT-3263 will.rogers wrote: That was

Re: [Geoserver-users] App schema feature chaining issue

Hi Ryan, What does your chaining attribute look like in the mapping file? When does the error occur, when you make a request, or during startup? Can you also attach a stack trace? Maybe I can help. Cheers Rini Ryan Zoerb wrote: Thanks for the response Ben. GWSI_LEVELS is a table. Here

Re: [Geoserver-users] geoserver 2.1 beta1: cannot detect mysql geometry

20, 2010 at 7:31 PM, Rini Angreani rini.angre...@csiro.auwrote: This looks like the same problem I reported: http://jira.codehaus.org/browse/GEOT-3263 It's been introduced (accidentally) since VARBINARY mapping was added to SQLDialect. The workaround was not to use JDBC 3.0 (use previous

Re: [Geoserver-users] Appschema: Circular feature-chaining

Hello Ryan, You can have multiple mappings of a feature type in one service, as long as they're not in the same location where its featuretype.xml is defined. E.g. you can't have 2 GeologicUnit mappings in GeologicUnit configuration location, as the featuretype.xml would not know which mapping