[Geoserver-devel] Jenkins build is back to normal : GeoServer-Master #2783

See -- ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net

[Geoserver-devel] Reminder: GeoTools / GeoServer Meeting at 19:30 UTC on Tuesday

GeoTools / GeoServer committee meeting on Skype at 19:30 UTC on Tuesday: http://www.timeanddate.com/worldclock/fixedtime.html?msg=GeoTools+%2F+GeoServer+Meeting=2016=4=5=19=30=0=1 -- Ben Caradoc-Davies Director Transient Software Limited New Zealand

[Geoserver-devel] Build failed in Jenkins: GeoServer-Master #2782

See -- Started by upstream project "GeoTools-Master-Security" build number 314 originally caused by: Started by an SCM change Started by an SCM change Started by an SCM change Started

Re: [Geoserver-devel] GeoServer imageio and GDAL 2.0.x

Even, That sounds very promising - thanks for your message. Did you run into any problems? Did you have a chance to do much testing? Thanks, Dave On Mon, Apr 4, 2016 at 11:01 AM, Even Rouault wrote: > Le lundi 04 avril 2016 19:29:49, Dave Blasby a écrit : > > Hi,

Re: [Geoserver-devel] Custom URL protocol handling

Hi Andrea, Chris, Andrea, thanks for the input. Chris, it seems like several handlers could be gathered up for the one-go at registering them. That said, I'm a little worried that if other applications in a container are trying to do the same, then we'll lose. I don't know if that concern

Re: [Geoserver-devel] GeoServer imageio and GDAL 2.0.x

Le lundi 04 avril 2016 19:29:49, Dave Blasby a écrit : > Hi, Simone, > > Another Boundless person (Amiram) used GDAL 2 with imageio-ext for a > project. Unfortunately, they only tested the MrSid and DTED formats > (include DTED as a WCS output). He indicated (for CentOS 7) to use SWIG > 1.3

Re: [Geoserver-devel] GeoServer imageio and GDAL 2.0.x

Hi, Simone, Another Boundless person (Amiram) used GDAL 2 with imageio-ext for a project. Unfortunately, they only tested the MrSid and DTED formats (include DTED as a WCS output). He indicated (for CentOS 7) to use SWIG 1.3 instead of 2.0 (included in centos7). I'll let him comment further.

Re: [Geoserver-devel] Custom URL protocol handling

Hi, I read the base question and the accepted answer from Andrea’s reference. It seems the para 4 could be an issue requiring a wrapper to be written to handle multiple custom protocols. Ref: http://stackoverflow.com/questions/26363573/registering-and-using-a-custom-java-net-url-protocol “4

Re: [Geoserver-devel] GeoServer imageio and GDAL 2.0.x

Dear Torben, I just talked to Daniele about this; we have not done any tests yet with GDAL 2.0 but we are planning to update the imageio-ext builds to 1.11.x as there are a few bugs that are bothering us. Do you want to help with the direct jump to 2.x? Regards, Simone Giannecchini == GeoServer

[Geoserver-devel] Shape export is empty [Windows Server] [SQLServer]

Hi List, I have a problem with the Shape-Zip export via WFS. I can download via WFS request, but the ZIP File is damaged / empty. EXCEL2007 and SHAPE export format is broken. GML 2, 3, excel old, csv works. Any Idea? It works on a Windows Server 2012 with SQL Server 2012. I think that the

Re: [Geoserver-devel] Custom URL protocol handling

Hi Jim, as said in the other mail, I don't know, but I'm afraid if you don't go for URL handlers you'll have to modify more than just geotools and geoserver (and go down in imageio). I was actually skeptical about joining this thread because I don't have any direct experience on this subject, nor

Re: [Geoserver-devel] Custom URL protocol handling

To make this concrete, I think that any HDFS or S3 support would likely be a community module for a bit. Proposing for #2 would involve any API work required, and then we could update existing plugins as needed. Cheers, Jim On 04/04/2016 11:03 AM, Andrew Hulbert wrote: > I thinks HDFS and S3

Re: [Geoserver-devel] Custom URL protocol handling

I thinks HDFS and S3 are stable enough to have some sort of support that ships out of the box. The only worry I would have is the dependency chain that comes with HDFS. If it proves to be larger than we'd like we can just have good doc on installation... I support #2 as much as possible too.

Re: [Geoserver-devel] Custom URL protocol handling

Hi Andrea, all, In terms of ease, would it be preferable to 1) ask HDFS/S3 minded users to add URL handlers to their JVM or 2) handle this at the GeoTools/GeoServer level? For #1, I get the sense that adding URL handlers is more challenging. Also, I doubt all installations would be ok with

Re: [Geoserver-devel] Custom URL protocol handling

Hi Rich, it should be something along these lines (as said, never tried personally, was just barely aware it should be possible): http://stackoverflow.com/questions/26363573/registering-and-using-a-custom-java-net-url-protocol Cheers Andrea On Mon, Apr 4, 2016 at 4:37 PM, Rich Fecher

Re: [Geoserver-devel] Custom URL protocol handling

It is definitely possible we missed an extension point to register protocol handlers at the JVM level. I just hadn't thought of it at the time and didn't dig in, but I'll keep it in mind. Also, I'm curious if that works in the case of 'hdfs' and 's3' protocol because then I'd think it should

Re: [Geoserver-devel] Custom URL protocol handling

Yeah the only thing we will have to worry about is if the code is written against java.io.File instead of some other URL lib. At some point I guess we could dig in and look. I'll ask Jim for more info and see if we can mock it up...while we're at it we can do S3 or something too for another

Re: [Geoserver-devel] Custom URL protocol handling

On Mon, Apr 4, 2016 at 4:30 PM, Andrea Aime wrote: > That said, I'm not sure this has ever been tried, not at any level, but > especially with imageio-ext, > Sorry, mis-typed, I meant jai-imageio there Cheers Andrea -- == GeoServer Professional Services from the

Re: [Geoserver-devel] Custom URL protocol handling

Hi Andrew, that's good news, it is exactly what the thread was making me wonder. As far as I know/remember, all the URL validation and handling revolves against the JVM native ability to handle a particular protocol. That said, I'm not sure this has ever been tried, not at any level, but

Re: [Geoserver-devel] Custom URL protocol handling

In general there's really no reason why we can't support a generic handler protocol like the Hadoop InputFormats do. For example you can just specifiy s3a:// or hdfs:// or file:// etc. Java has a setup to deal with handling URL and URI syntax and register handlers for it. We can make that be a

Re: [Geoserver-devel] Custom URL protocol handling

Hi Jim and Michael, Great idea regarding the GeoServer raster data store being more friendly to other URLs such as those using HDFS protocol. I'd like to add that it would be nice to be able to use some other format or perhaps a custom defined protocol for the URL string. We originally looked at

[Geoserver-devel] Some ideas about minimum community/software responsibility and participation

Hi, with this mail I want to put on the table a basic notion of minimum community/software responsibility and participation. As the GeoServer project has gained more and more traction, the community of people behind it has grown beyond the initial hardcore GeoServer developers, which is great.

[Geoserver-devel] [JIRA] (GEOS-7484) problems with INSPIRE xsd schema use in Application schema

Title: Message Title Adam Mydla created

Re: [Geoserver-devel] Custom URL protocol handling

Hi all, As a little more context, we are looking for the most suitable way to HDFS-enable the existing raster plugins. With some of the javax ImageIO SPI interfaces, it looked like we'd be close to being able to have a drop-in solution. Otherwise, it looks like we may have to touch each