Re: [Geoserver-devel] Complex features in the user manual

Ben Caradoc-Davies ha scritto: > I have added an introductory page on complex features. > http://docs.geoserver.org/trunk/en/user/data/app-schema/complex-features.html > > All feedback is appreciated. I think I have been fair to simple > features. ;-) Yes you were, it's a good read which I woul

[Geoserver-devel] Complex features in the user manual

I have added an introductory page on complex features. http://docs.geoserver.org/trunk/en/user/data/app-schema/complex-features.html All feedback is appreciated. I think I have been fair to simple features. ;-) Kind regards, -- Ben Caradoc-Davies Software Engineer, CSIRO Exploration and Mini

Re: [Geoserver-devel] Roadmap wiki page lets go

So Andrea is suggesting something like a release champion; to avoid passing things around. That may work - however to be honest the hard part here is filling in your own work that you are doing (and that happens regardless of if you are in charge of the release or not). If we do lack a volun

Re: [Geoserver-devel] stepping down from the PSC

Thanks for the amazingly hard work Justin; you have been an excellent representative for the PSC. Jody On 22/09/2009, at 1:52 AM, Justin Deoliveira wrote: > Hi all, > > For various reasons I have decided to step down from the GeoServer > project steering committee. I do however plan to remain a

[Geoserver-devel] WFSConfiguration's SchemaBuilder catching up disabled feature types

Hi, Just found out that FeatureTypeSchemaBuilder$GML3.addApplicationTypes is creating schemas for disabled types because it's checking on FeatureTypeInfo.isEnabled() instead of the derived property FeatureTypeInfo.enabled() which also checks if the parent StoreInfo is enabled. This may cause

Re: [Geoserver-devel] Roadmap wiki page lets go

Mike Pumphrey ha scritto: > I like that wiki page as well. > > But what if no one volunteers for a release? Once in a while it might happen. If it happens often we'll have no other choice but to reconsider the way we do planning inside the PSC. If the PSC cannot take a decision on that, well, we

[Geoserver-devel] [jira] Created: (GEOS-3528) Filtering capabilities for the ImageMosaic coverage plugin

Filtering capabilities for the ImageMosaic coverage plugin -- Key: GEOS-3528 URL: http://jira.codehaus.org/browse/GEOS-3528 Project: GeoServer Issue Type: Wish Components: WMS

Re: [Geoserver-devel] Roadmap wiki page lets go

I like that wiki page as well. But what if no one volunteers for a release? Thanks, Mike Pumphrey OpenGeo - http://opengeo.org Andrea Aime wrote: > Jody Garnett ha scritto: >> Hi Andrea; thanks for summing things up. >> >> I am juggling a lot of things this week trying to get geotools out the

[Geoserver-devel] Hudson build is back to normal: geoserver-trunk #1818

See -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your devel

Re: [Geoserver-devel] Some never should happen exception

I can't comment on this specific issue, but I would like to say that any error that says "This should never happen"...um...should never happen. :) I don't really know the details on how error handling works in GeoServer, so perhaps this is a way of putting a ribbon on NullPointerExceptions? A

Re: [Geoserver-devel] stepping down from the PSC

I second Gabriel here, I am sorry to hear those words from you and I hope you are going to let things calm down a bit before taking such a decision. There has been some discussion lately on the devel list about PSC related stuff, which probably came through badly (my fault as well) but anyway, I be

Re: [Geoserver-devel] Roadmap wiki page lets go

Jody Garnett ha scritto: > Hi Andrea; thanks for summing things up. > > I am juggling a lot of things this week trying to get geotools out the > door; in collaboration with the next geoserver. Can we *try* doing the > wiki page now for this release and see how it goes? > > At this late date I

[Geoserver-devel] [jira] Created: (GEOS-3527) Add an option to delete data when deleting configuration

Add an option to delete data when deleting configuration Key: GEOS-3527 URL: http://jira.codehaus.org/browse/GEOS-3527 Project: GeoServer Issue Type: Improvement Components:

Re: [Geoserver-devel] stepping down from the PSC

Hi Andrea, I thank you for your comments. They are much appreciated. And I can assure this is not in response in to the roadmap thread in any way. I more or less made my decision weeks before the roadmap thread even started. It has been something I have been considering for quite some time, so

Re: [Geoserver-devel] stepping down from the PSC

hum, that's a cold shower... I'm very sorry to hear that. I know I've being quite out of the loop lately mostly focused on paid work rather than community stuff so I might have missed a discussion or two... sorry about that, I could have tried to help out somehow. In any case, it feels like loos

Re: [Geoserver-devel] stepping down from the PSC

Andrea Aime ha scritto: > Justin Deoliveira ha scritto: >> Hi all, >> >> For various reasons I have decided to step down from the GeoServer >> project steering committee. I do however plan to remain an active member >> of the development community. >> >> The docs with regard to the process of ste

Re: [Geoserver-devel] stepping down from the PSC

Justin Deoliveira ha scritto: > Hi all, > > For various reasons I have decided to step down from the GeoServer > project steering committee. I do however plan to remain an active member > of the development community. > > The docs with regard to the process of stepping down state that if I > w

[Geoserver-devel] [jira] Created: (GEOS-3526) problem with SRS EPSG:32662

problem with SRS EPSG:32662 --- Key: GEOS-3526 URL: http://jira.codehaus.org/browse/GEOS-3526 Project: GeoServer Issue Type: Bug Components: WMS Environment: windows Reporter: Jeremy Tru

[Geoserver-devel] stepping down from the PSC

Hi all, For various reasons I have decided to step down from the GeoServer project steering committee. I do however plan to remain an active member of the development community. The docs with regard to the process of stepping down state that if I wish I may nominate a successor: http://geoser

[Geoserver-devel] [jira] Created: (GEOS-3525) GeoTIFF coverages will not render under 2.0rc1

GeoTIFF coverages will not render under 2.0rc1 -- Key: GEOS-3525 URL: http://jira.codehaus.org/browse/GEOS-3525 Project: GeoServer Issue Type: Bug Components: WMS Affects Versions: 2.

[Geoserver-devel] Build failed in Hudson: geoserver-trunk #1817

See -- [...truncated 20228 lines...] PARAMETER["central_meridian", -93.0], PARAMETER["latitude_of_origin", 0.0], PARAMETER["scale_factor", 0.9996], PARAMETER["false_easting", 50.0],

Re: [Geoserver-devel] GSIP 42 - crowdsourcing GeoServer QA

Some feedback on this one ... - I am keen to give it a go (obvious since I volunteered to help test). - Can we use the "Resolved" status a request for testers to review; and then can mark an issue "Closed" when verified. On 18/09/2009, at 7:29 PM, Andrea Aime wrote: > Hi all, > I've put toghet

Re: [Geoserver-devel] Where to put extensions in the user manual?

Hi Ben. A while back, I believe it was Justin and I that decided (very informally) that we would put all of the datastore/coveragestore extensions in the Working With Data section, and the non-store extensions (Charts, etc) in the Extensions section. Thinking about it now, I think it wouldn't

Re: [Geoserver-devel] why are basenames 'wfs' etc hardcoded?

Hi, afaik there's no plan to do so so far. Why is it a problem though? it's machine to machine communication so it shouldn't matter at all. path-substring detection (aka, proxifiedUrl) is there to get the actual root context. From there on it's up to the server to define the service end points. I

[Geoserver-devel] why are basenames 'wfs' etc hardcoded?

Hi, I think this question belongs more to the dev list than the users list. When trying to setup a WFS with a different URL than .../wfs (e.g. /ows/railroads) I saw that the "wfs" part of the URL is hard coded in the source: ResponseUtils.appendPath(proxifiedBaseUrl, "wfs"). Is this nessecary?

Re: [Geoserver-devel] Geoserver REST API with FeatureTypes

My guess it is misconfigured in someway. Can you include the requests you are making in order to see the issue. What client are you using? cURL? If you could send the shapefile that would be even better. One thing to check for is that it has a .prj file that defines the spatial reference system

[Geoserver-devel] [jira] Created: (GEOS-3524) double EPSG string in WFS 1.0 getCapabilities

double EPSG string in WFS 1.0 getCapabilities - Key: GEOS-3524 URL: http://jira.codehaus.org/browse/GEOS-3524 Project: GeoServer Issue Type: Bug Components: WFS Affects Versions: 2.0-

[Geoserver-devel] Roadmap wiki page lets go

Hi Andrea; thanks for summing things up. I am juggling a lot of things this week trying to get geotools out the door; in collaboration with the next geoserver. Can we *try* doing the wiki page now for this release and see how it goes? At this late date I want to do something; you already have

[Geoserver-devel] [jira] Created: (GEOS-3523) outputformat=shape-zip generates shapefiles with utf-8 encoding

outputformat=shape-zip generates shapefiles with utf-8 encoding --- Key: GEOS-3523 URL: http://jira.codehaus.org/browse/GEOS-3523 Project: GeoServer Issue Type: Bug Compon