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: http://osgeo-org.1560.x6.nabble.com/xlink-ref-not-well-encoded-in-WFS-response-app-schema-tp5002307p5161027.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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: http://osgeo-org.1560.x6.nabble.com/app-schema-and-a-mapping-to-generate-xlink-href-or-xsi-nil-on-the-same-element-tp5132993p5133068.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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 from the GeoServer - User mailing list archive at Nabble.com. -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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 archive at Nabble.com. -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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. -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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 this message in context: http://osgeo-org.1560.x6.nabble.com/Complex-features-and-WMS-tp5129235p5129337.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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 message in context: http://osgeo-org.1560.x6.nabble.com/App-Schema-encodeIfEmpty-tp5085600p5085688.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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 denormalising, if the sole purpose is to join simple properties like gml:name. I know, I still owe documentation update for this.. I just haven't got around to do it. Performance implication is the same with feature chaining complex properties.. i.e. bearable for plain GetFeature, but slow if you use filter and the filter involves the feature chained property. This is something yet to be fixed because it is not that straightforward. Cheers Rini -- View this message in context: http://osgeo-org.1560.x6.nabble.com/App-Schema-and-Join-Tables-tp5085695p5085699.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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: http://osgeo-org.1560.x6.nabble.com/App-Schema-plugin-2-4-1-mapping-the-AdministrativUnit-model-of-INSPIRE-tp5085125p5085744.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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 sequence element name=employeeID type=integer/ element name=salary type=integer/ element name=metadata type=gmd:MD_Metadata_PropertyType/ /sequence /extension /complexContent /complexType -- View this message in context: http://osgeo-org.1560.x6.nabble.com/App-schema-feature-linkage-issue-tp5084723p5085678.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135991iu=/4140/ostg.clktrk ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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 foreign key to distinguish the parents. e.g. super class id| joining condition = 1| x 2| y 3| x 4| z sub class id | joining condition === a| x b| y c| z Row 1 and 3 in the super class matches the same sub class rows (sub class id = a). Joining generates the following result set using INNER JOIN: sub class id | joining condition | super class id === a | x | 1 a | x | 3 b | y | 2 c | z | 4 Joining relies heavily on sorting so it doesn't have to run so many queries. The super class id here is used to signal when to stop building the chained feature for the parent. I hope that makes sense. -- View this message in context: http://osgeo-org.1560.x6.nabble.com/App-Schema-Inheritance-question-tp5081362p5083567.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60135031iu=/4140/ostg.clktrk ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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: http://osgeo-org.1560.x6.nabble.com/OpenLayers-with-App-Schemas-tp5075263p5075509.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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: http://osgeo-org.1560.x6.nabble.com/app-schema-tries-to-access-non-existent-objectid-column-tp5074565p5075198.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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 for gsmlu (it's not imported in geologicUnit.xsd). If you're using https://www.seegrid.csiro.au/subversion/GeoSciML/branches/3.2.0/schemas/geosciml/3.2/geosciml.xsd;, it imports gsmlu from the location that doesn't exist yet, i.e. http://schemas.geosciml.org/cgiutilities/3.2/cgiUtilities.xsd;. This can be solved by manipulating the app-schema cache. You do this by copying the cgiUtilities.xsd in the cache, such that it looks like it comes from the location that doesn't exist. More info on the cache structure: http://docs.geoserver.org/stable/en/user/data/app-schema/app-schema-resolution.html#cache Hope that helps. Cheers Rini -- View this message in context: http://osgeo-org.1560.x6.nabble.com/app-schema-error-with-schemas-in-class-path-tp5068649p5068845.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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: http://osgeo-org.1560.x6.nabble.com/Performance-issue-with-App-schema-tp5066947p5067208.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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 using? If you are already using the latest, then this is possibly a new bug. Can you please point me to your mapping files and the problematic query? Thanks Rini -- View this message in context: http://osgeo-org.1560.x6.nabble.com/app-schema-and-gazetteer-tp5053723p5057083.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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 the 3rd query because the underlying type doesn't have any geometry attribute. I know removing gsml:shape from the mapping file is not an option.. so there isn't really a workaround unfortunately. Cheers Rini -- View this message in context: http://osgeo-org.1560.x6.nabble.com/app-schema-query-fails-with-org-geotools-feature-NameImpl-cannot-be-cast-to-org-opengis-feature-typer-tp5053444p5055874.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- Try New Relic Now We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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, but I don't remember why I did that (it was causing problems at that time). I noticed you're not using idExpression in your types. Try adding idExpression in your mapping files and map them to your primary keys directly (not using getId()). If this doesn't work, you can send me some of your sample database dump (privately if you prefer) so I can debug this and investigate. I will schedule the bug to be fixed next iteration. Cheers Rini -- View this message in context: http://osgeo-org.1560.x6.nabble.com/App-schema-not-working-with-joining-true-tp5044084p5046958.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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 http://docs.geoserver.org/stable/en/user/data/app-schema/supported-gml-versions.html#secondary-namespace-for-gml-3-2-1-required. Try specifying namespace.xml and workspace.xml for xlink. I hope that helps. Cheers Rini -- View this message in context: http://osgeo-org.1560.n6.nabble.com/xlink-ref-not-well-encoded-in-WFS-response-app-schema-tp5002307p5004518.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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 short on resources so it's not going to be fixed any time soon. Cheers Rini -- View this message in context: http://osgeo-org.1560.n6.nabble.com/app-schema-WFS-request-sortBy-not-evaluated-tp4996945p4997226.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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. ogc:PropertyNamecollarLocation/BoreholeCollar/location/ogc:PropertyName -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/app-schema-WMS-tp6973393p7175386.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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 incorrectly. Cheers Rini Shaw Innes wrote: Further to my previous post - I have found this error which is coming up whenever I click the publish button on the complex feature layer. Caused by: org.geotools.data.DataSourceException: http://sidelab:Locality:Locality not found. Available: [http://sidelab:Locality] at org.geotools.data.complex.AppSchemaDataAccess.getMappingByElement(AppSchemaDataAccess.java:188) at org.geotools.data.complex.AppSchemaDataAccess.getFeatureSource(AppSchemaDataAccess.java:425) at org.geoserver.catalog.CatalogBuilder.buildFeatureType(CatalogBuilder.java:324) at org.geoserver.web.data.layer.NewLayerPage.buildLayerInfo(NewLayerPage.java:198) ... 71 more On 03/03/2011, at 8:32 PM, Ben Caradoc-Davies wrote: Please resend your email to the users list so that everyone can see it. Others may be able to assist. On 03/03/11 18:12, Shaw Innes wrote: Hi Ben, Thanks for the quick response. I realised that might make some difference so I changed my database schema to be all lower case - which brought me to some new errors - I've attached my config files which were in my complex data store. I've been trying to use the web GUI to configure these but it seems that maybe manually is safer. When I have this configuration in place my mapserver will no longer startup. I don't see anything in the logs though so I'm going to look into increasing the logging level. I don't suppose you could point me in the direction of a really simple example using PostGIS as a datasource to create a simple app schema? Once I can get a basic one working I'm sure I can extend it easily enough Thanks again Shaw -- Ben Caradoc-Davies ben.caradoc-dav...@csiro.au Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre -- Free Software Download: Index, Search Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users -- View this message in context: http://old.nabble.com/App-Schemas-and-Feature-Chaining-tp31056575p31064424.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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 what we thought. But we don't know why it's null. 'select count(*) from rivers_polyline where the_geom is null' gives 0. It now looks like we should be able to map a LineString on to the GeometricPrimitivePropertyType, so we're not sure what else might be wrong. -Original Message- From: Ben Caradoc-Davies [mailto:ben.caradoc-dav...@csiro.au] Sent: 08 December 2010 05:35 To: Rogers, Will (STFC,RAL,ESC) Cc: geoserver-users@lists.sourceforge.net Subject: Re: [Geoserver-users] app-schema mapping geometry column in PostGIS On 07/12/10 20:18, will.rog...@stfc.ac.uk wrote: The exception I get is: ows:ExceptionText org.geotools.feature.IllegalAttributeException:http://www.opengis.net/gml:GeometricPrimitivePropertyType not nillable:null value:null http://www.opengis.net/gml:GeometricPrimitivePropertyType not nillable /ows:ExceptionText [...] Does anyone have any idea what's wrong with this? I can provide more details if necessary. This error is caused by mapping a null from your database into a mandatory property. hy-p:geometry is a mandatory property of hy-p:SurfaceWaterType. The error is telling you that this property is not nillable and has a null value. What do you get for this? select count(1) from yourtablename where isnull(the_geom); app-schema supports conditional mappings of properties (even choosing between xlink:href and values) but I am not sure this will work in your case because geometries are handled as atomic types by GeoServer and app-schema has only limited ability to manipulate them: http://docs.geoserver.org/latest/en/user/data/app-schema/polymorphism.html -- Ben Caradoc-Davies ben.caradoc-dav...@csiro.au Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre -- Scanned by iCritical. -- This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users -- View this message in context: http://old.nabble.com/app-schema-mapping-geometry-column-in-PostGIS-tp30395768p30412675.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- This SF Dev2Dev email is sponsored by: WikiLeaks The End of the Free Internet http://p.sf.net/sfu/therealnews-com ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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 is the output from DESCRIBE GWSI_LEVELS: DESCRIBE GW_DATA_PORTAL.GWSI_LEVELS Name NullType -- - AGENCY_CD NOT NULLVARCHAR2(5) SITE_NO NOT NULLVARCHAR2(15) DATES DATE VALUE NUMBER REMARKVARCHAR2(5) REMARK_DS VARCHAR2(255) SOURCE_CD VARCHAR2(5) METHOD_CD VARCHAR2(5) METHOD_DS VARCHAR2(255) QW_ACCURACY VARCHAR2(5) QW_ACCURACY_NMVARCHAR2(255) HOST NOT NULLVARCHAR2(30) DBNUM NOT NULLVARCHAR2(2) DWH_INSERTDATE LEV_CNVARCHAR2(8) LEV_CRDATE LEV_MNVARCHAR2(8) LEV_MDNOT NULLDATE GW_LEV_PK NOT NULLNUMBER MP_LEV_VA VARCHAR2(7) SL_LEV_VA VARCHAR2(8) LEV_ENT_CDVARCHAR2(1) LEV_STATISTICS_CD VARCHAR2(1) LEV_STATISTICS_NM VARCHAR2(255) DATE_ACY_CD VARCHAR2(1) SL_DATUM_CD VARCHAR2(10) LEV_PARTY_TX VARCHAR2(6) LEV_WEB_CDVARCHAR2(1) LEV_AGENCY_CD VARCHAR2(5) LEV_MPNT_SEQ_NU NUMBER LEV_RMK_TXVARCHAR2(256) LEV_EQPID_TX VARCHAR2(20) DWH_SITE_ID NOT NULLNUMBER PARAMETER_CODECHAR(5) SOURCEVARCHAR2(10) VALUE_ALL NUMBER Thanks, Ryan On Nov 2, 2010, at 8:20 PM, Ben Caradoc-Davies wrote: Ryan, I do not think this is an app-schema problem as it is the inner feature type that is affected and this error will likely occur before any chaining takes place. My guess is this is either a subtle bug in the geotools oracle support, or an unintended interaction with your database configuration. I cannot find any hardcoded identifier TIMES in the code base. (1) Is GWSI_LEVELS a table, view, or materialized view? (2) What is the output of DESCRIBE GWSI_LEVELS? Kind regards, Ben. On 03/11/10 05:46, Ryan Zoerb wrote: Hi everyone. I'm trying to get application schema with feature chaining working, but I'm running into an issue. I've attached the two mapping files I'm using. WaterWell is the top level element, which can have several nested logElement's. I've been able to successfully get GeoServer to return a correct response without feature chaining, but when I added the chaining, I get this Oracle error: 'ORA-00904: TIMES: invalid identifier'. Here's the query that GeoServer is doing that returns the error: SELECT GW_LEV_PK,AGENCY_CD,SITE_NO,DATES,VALUE,REMARK,REMARK_DS,SOURCE_CD,METHOD_CD,METHOD_DS,QW_ACCURACY,QW_ACCURACY_NM,HOST,DBNUM,DWH_INSERT,LEV_CN,LEV_CR,LEV_MN,LEV_MD,MP_LEV_VA,SL_LEV_VA,LEV_ENT_CD,LEV_STATISTICS_CD,LEV_STATISTICS_NM,DATE_ACY_CD,SL_DATUM_CD,LEV_PARTY_TX,LEV_WEB_CD,LEV_AGENCY_CD,LEV_MPNT_SEQ_NU,LEV_RMK_TX,LEV_EQPID_TX,DWH_SITE_ID,PARAMETER_CODE,SOURCE,VALUE_ALL,AGENCY_CD,SITE_NO,DATES,VALUE,STATUS_CD,STATUS_DS,SOURCE_CD,METHOD_CD,METHOD_DS,QW_ACCURACY,QW_ACCURACY_NM,HOST,DBNUM,DWH_INSERT,LEV_CN,LEV_CR,LEV_MN,LEV_MD,TIMES,MP_LEV_VA,SL_LEV_VA,LEV_ENT_CD,LEV_STATISTICS_CD,LEV_STATISTICS_NM,DATE_ACY_CD,SL_DATUM_CD,LEV_PARTY_TX,LEV_WEB_CD,LEV_AGENCY_CD,LEV_MPNT_SEQ_NU,LEV_RMK_TX,LEV_EQPID_TX,DWH_SITE_ID FROM GWSI_LEVELS WHERE SITE_NO = ? The problem is that the GWSI_LEVELS table doesn't have a column called TIMES. All of the other columns are correct (even though most
Re: [Geoserver-users] geoserver 2.1 beta1: cannot detect mysql geometry
Yay, must be the correct solution if 2 people propose them independently then :) Justin Deoliveira-6 wrote: Ahh, thanks Rini, i filed a bug yesterday proposing the same fix (to have type mapping work with name first, before using the sql integer type reported by the driver). On Mon, Sep 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 versions instead). Cheers Rini Justin Deoliveira-6 wrote: Odd... another user had this same problem but with sql server. In that case it had something to do with the jdbc driver version being used. Are you using the jdbc driver shipped with geoserver? Also are you running on java 5 or java 6. I am still looking into that issue so hopefully will have some info soon. Any info you can provide about your environment would help though. -Justin On Sun, Sep 19, 2010 at 7:15 PM, nyem nye...@gmail.com wrote: It seems that my geoserver 2.1 beta1 installation cannot detect geometry type from mysql datastore. It shows the feature type as byte[] instead of Geometry. Is this a known issue with beta1? I'm running geoserver/mysql on Windows and the mysql plugin is from http://downloads.sourceforge.net/geoserver/geoserver-2.1-beta1-mysql-plugin.zip -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users -- View this message in context: http://old.nabble.com/geoserver-2.1-beta1%3A-cannot-detect-mysql-geometry-tp29755561p29765355.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users -- View this message in context: http://old.nabble.com/geoserver-2.1-beta1%3A-cannot-detect-mysql-geometry-tp29755561p29775639.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
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 to use. However, you can have a second GeologicUnit mapping file in MappedFeature folder. That means, only one mapping is used to serve the type as a top level feature (where featuretype.xml exists), and the other mappings are only used inside another feature type in a different location/folder. To achieve this, you can use mappingName (http://docs.geoserver.org/trunk/en/user/data/app-schema/mapping-file.html#typemappings-and-featuretypemapping). Sorry the documentation is not clear.. an improvement is long overdue. So in MappedFeature mapping file, you'd have something like: AttributeMapping targetAttributegsml:specification/targetAttribute sourceExpression OCQLGEOLOGIC_UNIT_ID/OCQL linkElementgeologicUnit_no_Occurrence/linkElement linkFieldFEATURE_LINK/linkField /sourceExpression /AttributeMapping Where geologicUnit_no_occurrence would have no specified attribute mapping for gsml:occurrence. To make this mapping unique from the top level GeologicUnit mapping, you must specify mappingName in its FeatureTypeMapping tag. In this case, mappingName would be geologicUnit_no_occurrence. You'd then include the location of geologicUnit_no_occurrence mapping, or define the FeatureTypeMapping in the same file (and would only exist for this MappedFeature). Same deal with GeologicUnit mapping, where you define it separately as a top level feature, and link occurrences to a separate MappedFeature mapping (with a different mappingName). Your second MappedFeature would have specification mapped as xlink:href. To sum up, to avoid having errors for multiple mappings per type: - mappingName has to override existing mapping with the same targetElement. - mappingName to be used instead of targetElement in linkElement tag on the chaining side. - there should only be 1 mapping file for the type where it is configured as top level feature (otherwise you'll get an error about feature type already exists or something to that effect). I hope it's not too confusing, and it works for you. Let me know otherwise. By the way, my colleague Victor Tey is close to fixing the problem you reported a long time ago: http://jira.codehaus.org/browse/GEOT-2843. Cheers Rini Ryan Clark wrote: Hello - I've ran into the old circular feature-chaining problem in a GeoSciML WFS service again. Basically it is exactly the problem outlined at http://docs.geoserver.org/stable/en/user/data/app-schema/feature-chaining.ht ml#multi-valued-properties-by-reference-xlink-href The approach outlined there requires that one or the other, GeologicUnit.occurence or MappedFeature.specification, be by xlink:href all of the time. If I make my occurrences by xlink:href, then whether I make a WFS query for gsml:GeologicUnit or gsml:MappedFeature, the occurrences will always be by xlink:href, and the value may or may not be resolvable, depending on how I construct the string and what exactly is in the WFS response document. What you'd really like is a service which followed these rules: 1) GeologicUnits that are being returned as MappedFeature.specifications would simply not include the optional gsml:occurrence property. 2) MappedFeature.specifications would only be by xlink:href if those MappedFeatures are being returned as GeologicUnit.occurrences. 3) In any other situation, occurrences or specifications would not be by xlink:href, unless they were being repeated within a single WFS response document. Is there any tricky way to do this? I tried building two gsml:GeologicUnit mapping files and using one as an includedType in the MappedFeature mapping file, but this means you have two mappings for one type, and it gags. My previous incarnation of a GeoSciML service accomplished this by actually being two services, one for only GeologicUnits, one for only MappedFeatures. The GeologicUnit service gave back MappedFeature occurrences where the specification was by xlink:href. The MappedFeature service gave back GeologicUnit specifications which did not include occurrences at all. This satisfied my three rules, but meant a lot of maintenance overhead, two services, and a bunch of duplicate mapping files. If anyone has had any interesting ideas about how to do this, I'd love to hear them! Thanks, Ryan
