Re: [Geoserver-users] ImageMosaic JDBC entering in null values for attributes

Re: [Geoserver-users] ImageMosaic JDBC entering in null values for attributes

Re: [Geoserver-users] ImageMosaic JDBC entering in null values for attributes

Re: [Geoserver-users] ImageMosaic problem with grayscale JPEG image

Re: [Geoserver-users] ImageMosaic problem with grayscale JPEG image

Re: [Geoserver-users] ImageMosaic with mask

Re: [Geoserver-users] ImageMosaic with netCDF and custom dimensions in Geoserver

Re: [Geoserver-users] Imagemosaic: enforcing SuggestedSPI

Re: [Geoserver-users] ImageMosaic GrayChannel Styling

1|0|0|1|0|3|
STATISTICS_HISTOMAX=255
STATISTICS_HISTOMIN=0
STATISTICS_HISTONUMBINS=256
STATISTICS_MAXIMUM=255.0
STATISTICS_MEAN=128.9430632605046
STATISTICS_MEDIAN=126
STATISTICS_MINIMUM=6.0
STATISTICS_MODE=100
STATISTICS_SKIPFACTORX=1
STATISTICS_SKIPFACTORY=1
STATISTICS_STDDEV=21.914724246377162
Band 2 Block=256x256 Type=Byte, ColorInterp=Green
  Min=1.000 Max=255.000
  Minimum=1.000, Maximum=255.000, Mean=119.587, StdDev=17.895
  NoData Value=0
  Overviews: 15797x21273, 7899x10637, 3950x5319, 1975x2660, 988x1330, 494x665, 
247x333, 124x167
  Metadata:
PIXEL_SCALING=GAIN:0.01 OFFSET:-1.0 UNITS:fraction USAGE:val=DN*gain+offset 
NULLVAL_DN:0.0 NULLVAL_UNITS:-1.0
STATISTICS_EXCLUDEDVALUES=0.0
STATISTICS_HISTOBINFUNCTION=direct
STATISTICS_HISTOBINVALUES=0|2|0|0|1|0|0|0|0|0|0|1|0|0|1|1|1|0|0|0|0|0|0|0|0|1|0|0|0|0|0|0|0|1|0|1|0|0|0|0|0|0|0|1|0|1|1|2|0|3|2|2|2|1|0|2|1|4|2|0|1|2|4|4|6|5|5|4|8|6|9|10|10|15|13|16|16|26|28|27|40|59|61|89|92|137|168|204|290|393|572|829|1173|1806|3125|5559|11539|28512|91414|1060454|77439015|70108352|96509686|125053573|130820504|115150567|95493052|78671339|65296430|55341618|47481196|42262460|38494999|35586419|32892894|31082809|29621881|28408820|27237724|26837539|26606815|26419403|26425775|26570555|26631752|26765741|26806222|27075306|27262326|27334258|27217607|26959368|26868351|26552239|26031752|25536139|25098673|24536906|23778935|22906038|22402739|21675378|20426235|19649423|18663494|17726125|16824133|15848828|14817940|13812154|12874493|11953678|11100549|10304583|9504907|8800184|8107143|7520489|6928018|6399172|5877157|5399708|4988459|4603288|4260451|3906963|3594063|3280160|2986086|2730713|2487185|2256793|2042280|1841324|1654140|1477325|1333072|1190069|1068452|956574|857144|765540|682514|609036|547158|481575|422628|366204|310048|258568|211083|169432|133824|106212|76072|50699|34466|23622|17366|12829|7946|3199|1993|1365|953|637|501|356|226|166|150|93|87|67|62|42|35|32|18|23|18|14|19|10|11|4|4|6|12|5|7|4|1|3|1|3|3|1|3|3|0|2|1|0|3|0|2|0|1|1|0|0|2|1|0|8|
STATISTICS_HISTOMAX=255
STATISTICS_HISTOMIN=0
STATISTICS_HISTONUMBINS=256
STATISTICS_MAXIMUM=255.0
STATISTICS_MEAN=119.58710894910986
STATISTICS_MEDIAN=113
STATISTICS_MINIMUM=1.0
STATISTICS_MODE=104
STATISTICS_SKIPFACTORX=1
STATISTICS_SKIPFACTORY=1
STATISTICS_STDDEV=17.89533291249844
Band 3 Block=256x256 Type=Byte, ColorInterp=Blue
  Min=1.000 Max=255.000
  Minimum=1.000, Maximum=255.000, Mean=150.084, StdDev=15.284
  NoData Value=0
  Overviews: 15797x21273, 7899x10637, 3950x5319, 1975x2660, 988x1330, 494x665, 
247x333, 124x167
  Metadata:
PIXEL_SCALING=GAIN:0.01 OFFSET:-1.0 UNITS:fraction USAGE:val=DN*gain+offset 
NULLVAL_DN:0.0 NULLVAL_UNITS:-1.0
STATISTICS_EXCLUDEDVALUES=0.0
STATISTICS_HISTOBINFUNCTION=direct
STATISTICS_HISTOBINVALUES=0|1|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|1|0|1|0|0|0|1|0|0|1|0|1|0|0|1|0|1|1|0|0|0|0|1|1|1|3|2|3|2|3|3|1|1|2|1|0|4|1|2|6|6|4|7|3|9|5|15|4|9|9|11|12|17|25|29|20|21|46|35|68|63|99|92|121|106|169|233|292|346|493|644|850|1225|1591|2408|3715|6292|11314|24495|66560|229745|1156105|6611841|2352507|2101413|2110019|2226785|2397498|2602481|2835443|3102177|3399248|3731465|4088534|4479218|4883414|5307784|5761738|6246683|6775932|7316127|7887052|8468692|9081201|9786920|10553782|11270422|12031709|12898273|13859582|14767153|15701752|16891194|18279854|19791732|21255895|22729535|24258150|25898775|27698944|29627151|31744134|34080610|36570520|39136228|41733989|44647012|47573899|50448156|53389766|56145976|58665409|61293588|63862904|66018245|67447781|68335950|68808077|68425394|67255838|65354003|62725597|59324382|55661389|51587716|46960779|42381569|38034056|33740956|29613136|25789074|22337352|19228499|16438378|14066203|11950363|10115376|8554401|7270125|6197052|5252879|4483531|3847223|3316462|2863433|2500288|2187282|1939490|1751018|1604953|1484510|1376607|1287668|1217342|1170401|1131765|1097554|1041126|1019755|1026754|1076964|1336964|3657891|507854|98590|25323|8072|3275|1593|1002|687|486|316|274|211|168|131|90|94|81|59|46|37|34|28|25|26|24|12|11|16|9|9|3|7|6|11|4|3|3|6|3|5|1|4|7|6|3|2|0|0|1|1|1|0|1|1|16|
STATISTICS_HISTOMAX=255
STATISTICS_HISTOMIN=0
STATISTICS_HISTONUMBINS=256
STATISTICS_MAXIMUM=255.0
STATISTICS_MEAN=150.08418475089576
STATISTICS_MEDIAN=152
STATISTICS_MINIMUM=1.0
    STATISTICS_MODE=155
STATISTICS_SKIPFACTORX=1
STATISTICS_SKIPFACTORY=1
STATISTICS_STDDEV=15.284313311004041
From: Daniele Romagnoli 
Sent: Wednesday, 25 September 2019 5:12 PM
To: Andrew Cleland 
Cc: [email protected] 
Subject: Re: [Geoserver-users] ImageMosaic GrayChannel Styling
Hi Andrew,
can you share some details about your dataset?
A gdalinfo command run on the configured file can provide some info on it 
(datatype, bands, ...)
Please, let us know.
Regards,
Daniele
On Wed, Sep 25, 2019 at 5:06 AM Andrew Cleland 
mailto:[email protected]&g

Re: [Geoserver-users] ImageMosaic GrayChannel Styling

2019-09-25 Thread Daniele Romagnoli Hi Andrew, can you share some details about your dataset? A gdalinfo command run on the configured file can provide some info on it (datatype, bands, ...) Please, let us know. Regards, Daniele On Wed, Sep 25, 2019 at 5:06 AM Andrew Cleland wrote: > Hi all, > I'm migrating some layers from Geoserver 2.9.3 to 2.15.1. A Style for an > ImageMosaic layer is behaving unexpectedly on the new version of Geoserver. > The SLD is here: https://pastebin.com/DKyZhuZU > When this style is applied to a 3 band ImageMosaic, it shows up as > completely black. I've tried changing the Input Transparency Color and > Output Transparency Color in the Coverage Parameters options, which worked > to fix other layers, but did not help in this case. > I found some documentation about GrayChannel here > which suggests that this should work. It works on Geoserver 2.9.3. Have any > changes been made since then which could affect how GrayChannel styling is > applied? > Kind regards, > Andrew > 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 > If you want to request a feature or an improvement, also see this: > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users Regards, Daniele Romagnoli GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. Ing. Daniele Romagnoli Senior Software Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. 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 If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users From: Andrew Miskelly [mailto:[email protected]] Sent: Wednesday, 25 September 2019 1:25 PM To: [email protected] Subject: [Geoserver-users] ImageMosaic and S3-GeoTiff Hi Folks, There was a brief thread about using ImageMosaic with GeoTiffs which are stored in S3 - via the S3-GeoTiff plugin - earlier in the month. https://sourceforge.net/p/geoserver/mailman/message/36719882/ I'm interested to know whether anyone was able to get this working. In my case, ImageMosaic is facilitating a WMS time dimension. Apologies for not replying to the original thread - I found that my list subscription had lapsed. Regards, Andrew CONFIDENTIALITY NOTICE AND DISCLAIMER The information in this transmission may be confidential and/or protected by legal professional privilege, and is intended only for the person or persons to whom it is addressed. If you are not such a person, you are warned that any disclosure, copying or dissemination of the information is unauthorised. If you have received the transmission in error, please immediately contact this office by telephone, fax or email, to inform us of the error and to enable arrangements to be made for the destruction of the transmission, or its return at our cost. No liability is accepted for any unauthorised use of the information contained in this transmission. CONFIDENTIALITY NOTICE AND DISCLAIMER The information in this transmission may be confidential and/or protected by legal professional privilege, and is intended only for the person or persons to whom it is addressed. If you are not such a person, you are warned that any disclosure, copying or dissemination of the information is unauthorised. If you have received the transmission in error, please immediately contact this office by telephone, fax or email, to inform us of the error and to enable arrangements to be made for the destruction of the transmission, or its return at our cost. No liability is accepted for any unauthorised use of the information contained in this transmission. 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 If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users I have tried to do the same. SuggestedSPI=org.geotools.s3.geotiff.S3GeoTiffReader fails with this exception: https://pastebin.com/bKPRVuKR Is there a way to modify S3GeoTiffReader to allow it to be instantiated in AbstractGTDataStoreGranuleCatalog I'm running Geoserver 2.16-RC so that I have this fix , which I thought may have been causing issues with S3GeoTiffReader. I found this comment from a pull request for issue GEOT-5956 which suggests that using S3 in an ImageMosaic may be possible, but I couldn't find anything in the documentation. I may be on the wrong track with using S3GeoTiffReader for the SuggestedSPI. My complete mosaic.properties: SuggestedSPI=org.geotools.s3.geotiff.S3GeoTiffReader SuggestedFormat=org.geotools.s3.geotiff.S3GeoTiffFormat SuggestedIsSPI=org.geotools.s3.S3ImageInputStreamImplSpi TimeAttribute=ingestion ExpandToRGB=false TypeName=cog_ground_cover_s3geotiff Name=cog_ground_cover_s3geotiff LevelsNum=9 PathType=URL Heterogeneous=true Caching=false HeterogeneousCRS=true LocationAttribute=location Levels=30.0,30.0 119.99021526426077,119.99503311235458 239.9804305282887,239.99006622517481 479.8565217391588,479.98013245034963 959.7130434783176,959.9602649006993 1919.4260869566351,1917.3809523810633 3832.1875,3834.7619047621265 7664.375,7629.1578947366215 15328.75,15099.375 CheckAuxiliaryMetadata=false MosaicCRS=EPSG\:3577 AbsolutePath=true Kind regards, Andrew 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 If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users Thank you Daniele, for your help!! The test example you provided was very helpful to get me started. This entry in timeregex.properties works: regex=([0-9]{8})(?:/rtma2p5.)(t[0-9]{2}z),format=MMdd't'HH'z',fullPath=true Mosaic granules are in subdirectories as follows: rtma2p5.20190731/rtma2p5.t00z.2dvaranl_ndfd.grb2_wexp where time varies from 00 to 23 (for every hour) It took a while to write a regex pattern. It took some time studying regex rules. I also tested the pattern on https://www.compilejava.net with this test: import java.util.regex.Matcher; import java.util.regex.Pattern; import java.util.regex.PatternSyntaxException; public class TestPatternExtraction public static void main(String[] args) String expr="([0-9]{8})(?:/rtma2p5.)(t[0-9]{2}z)"; //String expr="(.*[0-9]{8}.*t[0-9]{2}z.*)"; String name= "/wfas/data/rtma/rhm/rtma2p5.20190731/rtma2p5.t03z.2dvaranl_ndfd.grb2_wexp"; Pattern regex = Pattern.compile(expr); Matcher regexMatcher = regex.matcher(name); while (regexMatcher.find()) { for (int i = 1; i <= regexMatcher.groupCount(); i++) { System.out.println("matched text: " + regexMatcher.group(i)); System.out.println("match start: " + regexMatcher.start(i)); System.out.println("match end: " + regexMatcher.end(i)); } catch (PatternSyntaxException ex) { // Syntax error in the regular expression }//end try }//end while }//end main This list conversation was also helpful: https://sourceforge.net/p/geoserver/mailman/message/36061535/ As well as firing up Eclipse and tracing through the code. Kind regards, On 8/14/19, Daniele Romagnoli wrote: > Hi Alexander, > you may combine custom *format *and *fullPath* parameter. > There is an example in the GeoTools TimestampFileNameExtractorTest: > https://github.com/geotools/geotools/blob/21.2/modules/plugin/imagemosaic/src/test/java/org/geotools/gce/imagemosaic/properties/time/TimestampFileNameExtractorTest.java#L110 > I'm not very familiar with regex so I cannot help you too much with that > part. I always have to check the rules, each time I need a complex regex, > which doesn't occur very often. > Once you have identified your regex, you can use the propertiesCollector > with this String for your file > *rtma2p5.20190731/rtma2p5.t00z.2dvaranl_ndfd.grb2_wexp*: > "regex=yourmatchingregex,format=MMdd't'HH'z',fullPath=true" > Please, let us know. > Regards, > Daniele 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 If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users Hi Alexander, you may combine custom *format *and *fullPath* parameter. There is an example in the GeoTools TimestampFileNameExtractorTest: https://github.com/geotools/geotools/blob/21.2/modules/plugin/imagemosaic/src/test/java/org/geotools/gce/imagemosaic/properties/time/TimestampFileNameExtractorTest.java#L110 I'm not very familiar with regex so I cannot help you too much with that part. I always have to check the rules, each time I need a complex regex, which doesn't occur very often. Once you have identified your regex, you can use the propertiesCollector with this String for your file *rtma2p5.20190731/rtma2p5.t00z.2dvaranl_ndfd.grb2_wexp*: "regex=yourmatchingregex,format=MMdd't'HH'z',fullPath=true" Please, let us know. Regards, Daniele On Tue, Aug 13, 2019 at 7:58 PM Alexander Petkov wrote: > Is it possible to use subdirectory/filename in order to extract a > timestamp during ImageMosaic coverage configuration? > Or, is only the File name used for timestamp extraction? > I have sub directories and files containing the following naming format: > rtma2p5.20190731/rtma2p5.t00z.2dvaranl_ndfd.grb2_wexp > where t00 is from 00 to 23. > Thanks in advance!! > 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 > If you want to request a feature or an improvement, also see this: > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users Regards, Daniele Romagnoli GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. Ing. Daniele Romagnoli Senior Software Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. 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 If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users On 7/19/19, Daniele Romagnoli wrote: > Hi Alexander-Petkov, > you can set the WrapStore=true parameter in the indexer.xml. > It should do wrapping through a hidden mapping between long names and > truncated names. > Please, let us know if that works. (We need to better document that option > somewhere in the doc.) > Regards, > Daniele > On Thu, Jul 18, 2019 at 10:35 PM alexander-petkov > wrote: >> Is there a way to specify an alternative table name for Postgis, where >> granule index for an Imagemosaic is stored? >> I have a Grib dataset, which resolves the variable to a very long name: >> Total_precipitation_surface_12_Hour_Accumulation_probability_above_0p254 >> During coverage configuration, the table name in Postgis gets truncated: >> Total_precipitation_surface_12_Hour_Accumulation_probability_ab >> This is due to current Postgresql table name length limitations. >> I can see that this variable name is defined in >> /resources/grib2/grib2VarMap.xml in the grib jar from ucar: >> "Total_precipitation_surface_12_Hour_Accumulation_probability_above_0p254" >> resources/grib2/grib2VarMap.xml: >> Is it possible to redefine/change the coverage name in the properties, or >> indexer.xml file prior to mosaic creation? >> Otherwise the attempt ends in error. >> Link to Grib file: >> https://tgftp.nws.noaa.gov/SL.us008001/ST.opnl/DF.gr2/DC.ndfd/AR.conus/VP.001-003/ds.pop12.bin >> Thanks a lot in advance!! >> 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 >> If you want to request a feature or an improvement, also see this: >> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/geoserver-users > Regards, > Daniele Romagnoli > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V > for more information. > Ing. Daniele Romagnoli > Senior Software Engineer > GeoSolutions S.A.S. > Via di Montramito 3/A > 55054 Massarosa (LU) > Italy > phone: +39 0584 962313 > fax: +39 0584 1660272 > http://www.geo-solutions.it > http://twitter.com/geosolutions_it > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail. 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 If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users Hi Alexander-Petkov, you can set the WrapStore=true parameter in the indexer.xml. It should do wrapping through a hidden mapping between long names and truncated names. Please, let us know if that works. (We need to better document that option somewhere in the doc.) Regards, Daniele On Thu, Jul 18, 2019 at 10:35 PM alexander-petkov wrote: > Is there a way to specify an alternative table name for Postgis, where > granule index for an Imagemosaic is stored? > I have a Grib dataset, which resolves the variable to a very long name: > Total_precipitation_surface_12_Hour_Accumulation_probability_above_0p254 > During coverage configuration, the table name in Postgis gets truncated: > Total_precipitation_surface_12_Hour_Accumulation_probability_ab > This is due to current Postgresql table name length limitations. > I can see that this variable name is defined in > /resources/grib2/grib2VarMap.xml in the grib jar from ucar: > "Total_precipitation_surface_12_Hour_Accumulation_probability_above_0p254" > resources/grib2/grib2VarMap.xml: > Is it possible to redefine/change the coverage name in the properties, or > indexer.xml file prior to mosaic creation? > Otherwise the attempt ends in error. > Link to Grib file: > https://tgftp.nws.noaa.gov/SL.us008001/ST.opnl/DF.gr2/DC.ndfd/AR.conus/VP.001-003/ds.pop12.bin > Thanks a lot in advance!! > 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 > If you want to request a feature or an improvement, also see this: > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users Regards, Daniele Romagnoli GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. Ing. Daniele Romagnoli Senior Software Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. 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 If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users

t;."SENTINEL2" WHERE  
0 = 1
2019-03-22 08:17:07,958 DEBUG [org.geotools.jdbc] - Setting the_geom to POLYGON 
((446500 4685000, 446500 482, 62 482, 62 4685000, 446500 
4685000))
2019-03-22 08:17:07,958 DEBUG [org.geotools.jdbc] - Setting 0 to POLYGON 
((446500 4685000, 446500 482, 62 482, 62 4685000, 446500 
4685000))
2019-03-22 08:17:07,958 DEBUG [org.geotools.jdbc] - Setting location to 
S2A_USER_MSI_L2A_DS_MPS_20180713T110521625Z_RGB.ecw
2019-03-22 08:17:07,958 DEBUG [org.geotools.jdbc] - Setting 1 to 
S2A_USER_MSI_L2A_DS_MPS_20180713T110521625Z_RGB.ecw
2019-03-22 08:17:07,958 DEBUG [org.geotools.jdbc] - Setting ingestion to 
2018-07-13 02:00:00.0
2019-03-22 08:17:07,958 DEBUG [org.geotools.jdbc] - Setting 2 to 2018-07-13 
02:00:00.0
2019-03-22 08:17:07,958 DEBUG [org.geotools.jdbc] - Setting elevation to null
2019-03-22 08:17:07,958 DEBUG [org.geotools.jdbc] - Setting 3 to null
2019-03-22 08:17:07,958 DEBUG [org.geotools.jdbc] - Inserting new feature with 
ps: INSERT INTO "public"."SENTINEL2" ( 
"the_geom","location","ingestion","elevation" ) VALUES ( ST_GeomFromWKB(?, 
32630),?,?,?)
2019-03-22 08:17:07,958 DEBUG [org.geotools.jdbc] - 1 = POLYGON ((446500 
4685000, 446500 482, 62 482, 62 4685000, 446500 4685000))
2019-03-22 08:17:07,958 DEBUG [org.geotools.jdbc] - 2 = 
S2A_USER_MSI_L2A_DS_MPS_20180713T110521625Z_RGB.ecw
2019-03-22 08:17:07,958 DEBUG [org.geotools.jdbc] - 3 = 2018-07-13 02:00:00.0
2019-03-22 08:17:07,958 DEBUG [org.geotools.jdbc] - 4 = null
2019-03-22 08:17:07,958 DEBUG [org.geotools.jdbc] - SELECT 
pg_get_serial_sequence('"public"."SENTINEL2"', 'fid')
2019-03-22 08:17:07,958 DEBUG [org.geotools.jdbc] - SELECT 
currval('public."SENTINEL2_fid_seq"')
2019-03-22 08:17:07,958 DEBUG [org.geotools.gce.imagemosaic] - Done with file 
\\192.168.250.33\Resultados\PUBLICACION_GEOSERVER\SENTINEL2\S2A_USER_MSI_L2A_DS_MPS_20180713T110521625Z_RGB.ecw
2019-03-22 08:17:07,958 DEBUG [org.geotools.gce.imagemosaic] - Nothing to 
process!!!
2019-03-22 08:17:07,958 DEBUG [org.geotools.jdbc] - CLOSE CONNECTION
2019-03-22 08:17:07,958 DEBUG [org.geotools.jdbc] - CREATE CONNECTION
2019-03-22 08:17:07,958 DEBUG [org.geotools.jdbc] - SELECT 
ST_AsText(ST_Force_2D(ST_Envelope(ST_Extent("the_geom"::geometry FROM 
"public"."SENTINEL2"
2019-03-22 08:17:07,958 DEBUG [org.geotools.jdbc] - CLOSE CONNECTION
2019-03-22 08:17:08,020 DEBUG [org.geotools.util] - 
InterpolationConverterFactory can be applied from Strings to Interpolation  
only.
2019-03-22 08:17:08,020 DEBUG [org.geotools.util] - 
InterpolationConverterFactory can be applied from Strings to Interpolation  
only.
2019-03-22 08:17:23,130 WARN [org.springframework.web.servlet.PageNotFound] - 
No mapping found for HTTP request with URI 
[/z98a/z98aStatics/rup/basic-theme/images/rup.separatorArrow.gif] in 
DispatcherServlet with name 'dispatcher'
2019-03-22 08:17:23,130 DEBUG [org.geotools.util] - 
InterpolationConverterFactory can be applied from Strings to Interpolation  
only.
2019-03-22 08:17:23,130 DEBUG [org.geotools.util] - 
InterpolationConverterFactory can be applied from Strings to Interpolation  
only.
2019-03-22 08:17:25,770 WARN [org.springframework.web.servlet.PageNotFound] - 
No mapping found for HTTP request with URI 
[/z98a/z98aStatics/rup/basic-theme/images/rup.separatorArrow.gif] in 
DispatcherServlet with name 'dispatcher'
2019-03-22 08:17:25,770 DEBUG [org.geotools.util] - 
InterpolationConverterFactory can be applied from Strings to Interpolation  
only.
2019-03-22 08:17:25,770 DEBUG [org.geotools.util] - 
InterpolationConverterFactory can be applied from Strings to Interpolation  
only.
I've tried to increase the coverage access keep alive time, but I'm not sure 
it's herlping with this.
Thanks.
Regards.
Agur bero bat,
David Alda Fernández de Lezea
Área de Sistemas de Información Geográfica, Planificación Territorial y 
Forestal Informazio Geografikoen Sistemak, Lurralde eta Baso Antolaketaren 
Arloa.
[email protected] | www.hazi.eus
T 945 003 240 – M 627 923 170 – F 945 003 290 
Hazi | Granja Modelo de Arkaute s/n | 01192 Arkaute – Araba
*********  LEGE OHARRA   ***   AVISOLEGAL   
***   DISCLAIMER   *
Mezu hau pertsonala eta isilpekoa da eta baimenik gabeko erabilera debekatua 
dago legalki. Jasotzailea ez bazara ezabatu mezua, bidali eta kontserbatu gabe.
Este mensaje es personal y confidencial y su uso no autorizado está prohibido 
legalmente. Si usted no es el destinatario, proceda a borrarlo, sin reenviarlo 
ni conservarlo.
This message is personal and confidential, unauthorised use is legally 
prohibited. If you are not the intended recipient, delete it without resending 
or backing it.
-Mensaje original-

Re: [Geoserver-users] ImageMosaic Harvesting Error

2019-03-20 Thread Humphries, Graham (StateGrowth) Do you have a statement, in your .NET code, that writes to the log file when the timeout occurs? I would set this at WARN or ERROR so you can see if there is an ongoing issue. Cheers, Graham Humphries -Original Message- From: David Alda Fernandez de Lezea [mailto:[email protected]] Sent: Thursday, 21 March 2019 1:45 AM To: Daniele Romagnoli Cc: [email protected] Subject: Re: [Geoserver-users] ImageMosaic Harvesting Error I’m using rest API to re-harvest to collect all the images stored in a folder. These all images are ecw files while the ones that apparently work are tiff. Not sure if this has something to do with the problem though.. I developed a little .NET program to publish some images and to re-harvest the datastores. In the code I set the WebRequest timeout to the maximum value admitted, but I’m not sure when can happen the time-out.. Is there any particular log level that could clarify the error? Thanks in advance. Regards. Agur bero bat, David Alda Fernández de Lezea Área de Sistemas de Información Geográfica, Planificación Territorial y Forestal Informazio Geografikoen Sistemak, Lurralde eta Baso Antolaketaren Arloa. [email protected] | www.hazi.eus T 945 003 240 – M 627 923 170 – F 945 003 290 Hazi | Granja Modelo de Arkaute s/n | 01192 Arkaute – Araba * LEGE OHARRA *** AVISOLEGAL *** DISCLAIMER * Mezu hau pertsonala eta isilpekoa da eta baimenik gabeko erabilera debekatua dago legalki. Jasotzailea ez bazara ezabatu mezua, bidali eta kontserbatu gabe. Este mensaje es personal y confidencial y su uso no autorizado está prohibido legalmente. Si usted no es el destinatario, proceda a borrarlo, sin reenviarlo ni conservarlo. This message is personal and confidential, unauthorised use is legally prohibited. If you are not the intended recipient, delete it without resending or backing it. De: Daniele Romagnoli [mailto:[email protected]] Enviado el: viernes, 15 de marzo de 2019 11:58 Para: David Alda Fernandez de Lezea CC: [email protected] Asunto: Re: [Geoserver-users] ImageMosaic Harvesting Error Dear David, could you please provide more details on your steps? How are you re-harvesting? (curl ? Are you harvesting a whole folder, a zip?) Did you notice any "specific" time interval after that happens once you start the harvest? (thinking about some timeout occurring at some level) Please, let us know. Regards, Daniele On Mon, Mar 11, 2019 at 5:39 PM David Alda Fernandez de Lezea wrote: Hi list, I’m having some isues whilwe re-harvesting data for an ImageMosaic datastore. I have several ones and the harvesting works as expected, but in this particular case I’m getting an error: 2019-03-11 14:44:01,302 DEBUG [geoserver.rest] - Exception while flushing and closing the entity stream. org.apache.catalina.connector.ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:367) org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:331) org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.java:101) org.geoserver.filters.FlushSafeResponse$FlushSafeServletOutputStream.flush(FlushSafeResponse.java:64) org.geoserver.monitor.MonitorServletResponse$MonitorOutputStream.flush(MonitorServletResponse.java:90) com.noelios.restlet.http.HttpServerCall.sendResponse(HttpServerCall.java:314) com.noelios.restlet.ext.servlet.ServletCall.sendResponse(ServletCall.java:306) org.geoserver.rest.GeoServerServletConverter.commit(GeoServerServletConverter.java:54) com.noelios.restlet.ext.servlet.ServletConverter.service(ServletConverter.java:130) org.geoserver.rest.RESTDispatcher.handleRequestInternal(RESTDispatcher.java:87) org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153) org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48) org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:923) org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:852) org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882) org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:789) at javax.servlet.http.HttpServlet.service(HttpServlet.java:650) at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)

Re: [Geoserver-users] ImageMosaic Harvesting Error

2019-03-20 Thread David Alda Fernandez de Lezea I’m using rest API to re-harvest to collect all the images stored in a folder. These all images are ecw files while the ones that apparently work are tiff. Not sure if this has something to do with the problem though.. I developed a little .NET program to publish some images and to re-harvest the datastores. In the code I set the WebRequest timeout to the maximum value admitted, but I’m not sure when can happen the time-out.. Is there any particular log level that could clarify the error? Thanks in advance. Regards. Agur bero bat, David Alda Fernández de Lezea Área de Sistemas de Información Geográfica, Planificación Territorial y Forestal Informazio Geografikoen Sistemak, Lurralde eta Baso Antolaketaren Arloa. [email protected] | www.hazi.eus T 945 003 240 – M 627 923 170 – F 945 003 290 Hazi | Granja Modelo de Arkaute s/n | 01192 Arkaute – Araba *  LEGE OHARRA   ***   AVISOLEGAL   ***   DISCLAIMER   * Mezu hau pertsonala eta isilpekoa da eta baimenik gabeko erabilera debekatua dago legalki. Jasotzailea ez bazara ezabatu mezua, bidali eta kontserbatu gabe. Este mensaje es personal y confidencial y su uso no autorizado está prohibido legalmente. Si usted no es el destinatario, proceda a borrarlo, sin reenviarlo ni conservarlo. This message is personal and confidential, unauthorised use is legally prohibited. If you are not the intended recipient, delete it without resending or backing it. De: Daniele Romagnoli [mailto:[email protected]] Enviado el: viernes, 15 de marzo de 2019 11:58 Para: David Alda Fernandez de Lezea CC: [email protected] Asunto: Re: [Geoserver-users] ImageMosaic Harvesting Error Dear David, could you please provide more details on your steps? How are you re-harvesting? (curl ? Are you harvesting a whole folder, a zip?) Did you notice any "specific" time interval after that happens once you start the harvest? (thinking about some timeout occurring at some level) Please, let us know. Regards, Daniele On Mon, Mar 11, 2019 at 5:39 PM David Alda Fernandez de Lezea wrote: Hi list, I’m having some isues whilwe re-harvesting data for an ImageMosaic datastore. I have several ones and the harvesting works as expected, but in this particular case I’m getting an error: 2019-03-11 14:44:01,302 DEBUG [geoserver.rest] - Exception while flushing and closing the entity stream. org.apache.catalina.connector.ClientAbortException: java.net.SocketException: Connection reset by peer: socket write error org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:367) org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:331) org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.java:101) org.geoserver.filters.FlushSafeResponse$FlushSafeServletOutputStream.flush(FlushSafeResponse.java:64) org.geoserver.monitor.MonitorServletResponse$MonitorOutputStream.flush(MonitorServletResponse.java:90) com.noelios.restlet.http.HttpServerCall.sendResponse(HttpServerCall.java:314) com.noelios.restlet.ext.servlet.ServletCall.sendResponse(ServletCall.java:306) org.geoserver.rest.GeoServerServletConverter.commit(GeoServerServletConverter.java:54) com.noelios.restlet.ext.servlet.ServletConverter.service(ServletConverter.java:130) org.geoserver.rest.RESTDispatcher.handleRequestInternal(RESTDispatcher.java:87) org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153) org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48) org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:923) org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:852) org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882) org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:789)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:650)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:731) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)

Re: [Geoserver-users] ImageMosaic Harvesting Error

2019-03-15 Thread Daniele Romagnoli Dear David, could you please provide more details on your steps? How are you re-harvesting? (curl ? Are you harvesting a whole folder, a zip?) Did you notice any "specific" time interval after that happens once you start the harvest? (thinking about some timeout occurring at some level) Please, let us know. Regards, Daniele On Mon, Mar 11, 2019 at 5:39 PM David Alda Fernandez de Lezea wrote: > Hi list, > I’m having some isues whilwe re-harvesting data for an ImageMosaic > datastore. I have several ones and the harvesting works as expected, but in > this particular case I’m getting an error: > 2019-03-11 14:44:01,302 DEBUG [geoserver.rest] - Exception while flushing > and closing the entity stream. > org.apache.catalina.connector.ClientAbortException: > java.net.SocketException: Connection reset by peer: socket write error > org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:367) > org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:331) > org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.java:101) > org.geoserver.filters.FlushSafeResponse$FlushSafeServletOutputStream.flush(FlushSafeResponse.java:64) > org.geoserver.monitor.MonitorServletResponse$MonitorOutputStream.flush(MonitorServletResponse.java:90) > com.noelios.restlet.http.HttpServerCall.sendResponse(HttpServerCall.java:314) > com.noelios.restlet.ext.servlet.ServletCall.sendResponse(ServletCall.java:306) > org.geoserver.rest.GeoServerServletConverter.commit(GeoServerServletConverter.java:54) > com.noelios.restlet.ext.servlet.ServletConverter.service(ServletConverter.java:130) > org.geoserver.rest.RESTDispatcher.handleRequestInternal(RESTDispatcher.java:87) > org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153) > org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48) > org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:923) > org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:852) > org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882) > org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:789) > javax.servlet.http.HttpServlet.service(HttpServlet.java:650) > javax.servlet.http.HttpServlet.service(HttpServlet.java:731) > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) > org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) > org.apache.catalina.filters.CorsFilter.handleNonCORS(CorsFilter.java:436) > org.apache.catalina.filters.CorsFilter.doFilter(CorsFilter.java:177) > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) > org.geoserver.filters.ThreadLocalsCleanupFilter.doFilter(ThreadLocalsCleanupFilter.java:28) > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) > org.geoserver.filters.SpringDelegatingFilter$Chain.doFilter(SpringDelegatingFilter.java:75) > org.geoserver.wms.animate.AnimatorFilter.doFilter(AnimatorFilter.java:71) > org.geoserver.filters.SpringDelegatingFilter$Chain.doFilter(SpringDelegatingFilter.java:71) > org.geoserver.monitor.MonitorFilter.doFilter(MonitorFilter.java:138) > org.geoserver.filters.SpringDelegatingFilter$Chain.doFilter(SpringDelegatingFilter.java:71) > org.geoserver.filters.SpringDelegatingFilter.doFilter(SpringDelegatingFilter.java:46) > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) > org.apa

Re: [Geoserver-users] Imagemosaic spanning the dateline

2018-12-17 Thread Lubomír Bucek Unfortunately, even creating two separate single tiff raster sources (left and right), where one is approximately -180, 0 and second approximately 0,180, does not work in my case. The results look the same as on pictures attached to the jira issue. No raster colorization for last metatile. -- Původní e-mail -- Od: Phil Scadden Komu: Lubomír Bucek Datum: 13. 12. 2018 3:10:48 Předmět: RE: [Geoserver-users] Imagemosaic spanning the dateline That looks very much what I see and the same warnings (also generating requests with Leaflet) ! This isn’t the first time I have hit this with rasters but first time using image mosaic. In past I have worked around by building two separate source, one for east, one for west. Then created a layer group from both of them and serve that.  I have major new rebuild of the rasters due jan, and if no progress, I will adopt that approach. It is pretty bizarre however. I have also stumbled into probably the same issue trying to build a layer spanning across the dateline seamlessly. If this is not related, please correct me. I do not possess any Java skills to spot the bug in code neither fix it and therefore tried to document what I have tried on GeoServer side - to no success so far.  https://osgeo-org.atlassian.net/browse/GEOS-9059 (https://osgeo-org.atlassian.net/browse/GEOS-9059) It could be used as a steppingstone for someone later. -- Původní e-mail -- Od: Phil Scadden mailto:[email protected])> Komu: GeoServer Mailing List List mailto:[email protected])> Datum: 13. 12. 2018 0:00:41 Předmět: Re: [Geoserver-users] Imagemosaic spanning the dateline Any insight at all into the warning message would help. (Like what was code trying to do when it generated it). From: Phil Scadden mailto:[email protected])> Sent: Tuesday, 11 December 2018 10:06 To: GeoServer Mailing List List mailto:[email protected])> Subject: Re: [Geoserver-users] Imagemosaic spanning the dateline After a bit of battle getting disk provisioning, I have now successfully built an imagemozaic in EPSG:3857 which does cover both sides of the dateline. If I use “tiled” in getmap requests, it returns imagery for one side the dateline – if dateline is not in frame, you can get imagery for either side, but moment you have datetime in frame, then you get one side or other. I am about to analyse the getmap requests buts when I look in the logs, I see it is full of WARN message like this: 2018-12-11 09:52:09,214 WARN [lite.gridcoverage2d] - Could not reduce the grid geometry inside the valid area bounds: ReferencedEnvelope[- 1.7976931348623157E308 : 1.7976931348623157E308, -85.0 : 85.0] Grid geometry isGridGeometry2D[GridEnvelope2D[0..1063, 0..1063], PARAM_MT[ "Affine",   PARAMETER["num_row", 3],   PARAMETER["num_col", 3],   PARAMETER["elt_0_0", 9.554628534313876],   PARAMETER["elt_0_2", 19841652.786989305],   PARAMETER["elt_1_1", -9.554628534317445],   PARAMETER["elt_1_2", -4118861.8190303175]]] The messages vary in terms of the elt_ parameters and the GridEnvelope2D content, but ALWAYS have ReferencedEnvelope[-1.7976931348623157E308 : 1.7976931348623157E308, -85.0 : 85.0] The lat/long bounding box on the layer is -179.99 -60.23 179. -19.3111 Can anyone tell me what the WARN message is about? (or should I give up now and create 2 imagemozaics, one for each side of the dateline). From: Phil Scadden mailto:[email protected])> Sent: Monday, 29 October 2018 16:21 Cc: GeoServer Mailing List List mailto:[email protected])> Subject: Re: [Geoserver-users] Imagemosaic spanning the dateline That is encouraging. Trying it if I can figure the REST. While there is no accounting for some random consumer might request, any sensible query isn’t going to ask for the raster in anything but 3857 and it would make no sense outside SW Pacific. From: Andrea Aime mailto:[email protected])> Sent: Sunday, 28 October 2018 05:59 To: Phil Scadden mailto:[email protected])> Cc: GeoServer Mailing List List mailto:[email protected])> Subject: Re: [Geoserver-users] Imagemosaic spanning the dateline That looks very much what I see and the same warnings (also generating requests with Leaflet) ! This isn’t the first time I have hit this with rasters but first time using image mosaic. In past I have worked around by building two separate source, one for east, one for west. Then created a layer group from both of them and serve that. I have major new rebuild of the rasters due jan, and if no progress, I will adopt that approach. It is pretty bizarre however. From: Lubomír Bucek Sent: Thursday, 13 December 2018 14:09 To: Phil Scadden Subject: Re: [Geoserver-users] Imagemosaic spanning the dateline Good evening, I have also stumbled into probably the same issue trying to build a layer spanning across the dateline seamlessly. If this is not related, please correct me. I do not possess any Java skills to spot the bug in code neither fix it and therefore tried to document what I have tried on GeoServer side - to no success so far. https://osgeo-org.atlassian.net/browse/GEOS-9059 It could be used as a steppingstone for someone later. Best, Lubomír Bucek -- Původní e-mail -- Od: Phil Scadden mailto:[email protected]>> Komu: GeoServer Mailing List List mailto:[email protected]>> Datum: 13. 12. 2018 0:00:41 Předmět: Re: [Geoserver-users] Imagemosaic spanning the dateline Any insight at all into the warning message would help. (Like what was code trying to do when it generated it). From: Phil Scadden mailto:[email protected]>> Sent: Tuesday, 11 December 2018 10:06 To: GeoServer Mailing List List mailto:[email protected]>> Subject: Re: [Geoserver-users] Imagemosaic spanning the dateline After a bit of battle getting disk provisioning, I have now successfully built an imagemozaic in EPSG:3857 which does cover both sides of the dateline. If I use “tiled” in getmap requests, it returns imagery for one side the dateline – if dateline is not in frame, you can get imagery for either side, but moment you have datetime in frame, then you get one side or other. I am about to analyse the getmap requests buts when I look in the logs, I see it is full of WARN message like this: 2018-12-11 09:52:09,214 WARN [lite.gridcoverage2d] - Could not reduce the grid geometry inside the valid area bounds: ReferencedEnvelope[-1.7976931348623157E308 : 1.7976931348623157E308, -85.0 : 85.0] Grid geometry isGridGeometry2D[GridEnvelope2D[0..1063, 0..1063], PARAM_MT["Affine", PARAMETER["num_row", 3], PARAMETER["num_col", 3], PARAMETER["elt_0_0", 9.554628534313876], PARAMETER["elt_0_2", 19841652.786989305], PARAMETER["elt_1_1", -9.554628534317445], PARAMETER["elt_1_2", -4118861.8190303175]]] The messages vary in terms of the elt_ parameters and the GridEnvelope2D content, but ALWAYS have ReferencedEnvelope[-1.7976931348623157E308 : 1.7976931348623157E308, -85.0 : 85.0] The lat/long bounding box on the layer is -179.99 -60.23 179. -19.3111 Can anyone tell me what the WARN message is about? (or should I give up now and create 2 imagemozaics, one for each side of the dateline). From: Phil Scadden mailto:[email protected]>> Sent: Monday, 29 October 2018 16:21 Cc: GeoServer Mailing List List mailto:[email protected]>> Subject: Re: [Geoserver-users] Imagemosaic spanning the dateline That is encouraging. Trying it if I can figure the REST. While there is no accounting for some random consumer might request, any sensible query isn’t going to ask for the raster in anything but 3857 and it would make no sense outside SW Pacific. From: Andrea Aime mailto:[email protected]>> Sent: Sunday, 28 October 2018 05:59 To: Phil Scadden mailto:[email protected]>> Cc: GeoServer Mailing List List mailto:[email protected]>> Subject: Re: [Geoserver-users] Imagemosaic spanning the dateline Hi Phil, we have done that in the past, even with granules spanning the dateline, using a heterogeneous CRS setup (each image in its own UTM zone, the ones crossing the dateline in UTM 1 or 60). That said, it's always tricky, so I won't promise it will work in your case. Having the source CRS in 3857, that will surely be source of troubles if someone asks the map in output in 4326, last time I stumbled in that case if the client asked for the entire globe to be displayed in 4326 the envelope reprojection would fail Cheers Andrea mailto:[email protected]>> wrote: Before I waste a lot of time on something impossible, I thought I would ask whether it is okay to have an image mosaic that crosses the dateline. None of the granules cross the 180 (more accurately, the data is split into tiles that don’t cross the 180), but the mosaic itself will span a bi

Re: [Geoserver-users] Imagemosaic spanning the dateline

2018-12-12 Thread Lubomír Bucek Good evening,  I have also stumbled into probably the same issue trying to build a layer spanning across the dateline seamlessly. If this is not related, please correct me. I do not possess any Java skills to spot the bug in code neither fix it and therefore tried to document what I have tried on GeoServer side - to no success so far.  https://osgeo-org.atlassian.net/browse/GEOS-9059 (https://osgeo-org.atlassian.net/browse/GEOS-9059) It could be used as a steppingstone for someone later. Best, Lubomír Bucek -- Původní e-mail -- Od: Phil Scadden Komu: GeoServer Mailing List List Datum: 13. 12. 2018 0:00:41 Předmět: Re: [Geoserver-users] Imagemosaic spanning the dateline Any insight at all into the warning message would help. (Like what was code trying to do when it generated it). After a bit of battle getting disk provisioning, I have now successfully built an imagemozaic in EPSG:3857 which does cover both sides of the dateline. If I use “tiled” in getmap requests, it returns imagery for one side the dateline – if dateline is not in frame, you can get imagery for either side, but moment you have datetime in frame, then you get one side or other. I am about to analyse the getmap requests buts when I look in the logs, I see it is full of WARN message like this: 2018-12-11 09:52:09,214 WARN [lite.gridcoverage2d] - Could not reduce the grid geometry inside the valid area bounds: ReferencedEnvelope[- 1.7976931348623157E308 : 1.7976931348623157E308, -85.0 : 85.0] Grid geometry isGridGeometry2D[GridEnvelope2D[0..1063, 0..1063], PARAM_MT[ "Affine",   PARAMETER["num_row", 3],   PARAMETER["num_col", 3],   PARAMETER["elt_0_0", 9.554628534313876],   PARAMETER["elt_0_2", 19841652.786989305],   PARAMETER["elt_1_1", -9.554628534317445],   PARAMETER["elt_1_2", -4118861.8190303175]]] The messages vary in terms of the elt_ parameters and the GridEnvelope2D content, but ALWAYS have ReferencedEnvelope[-1.7976931348623157E308 : 1.7976931348623157E308, -85.0 : 85.0] The lat/long bounding box on the layer is -179.99 -60.23 179. -19.3111 Can anyone tell me what the WARN message is about? (or should I give up now and create 2 imagemozaics, one for each side of the dateline). From: Phil Scadden mailto:[email protected])> Sent: Monday, 29 October 2018 16:21 Cc: GeoServer Mailing List List mailto:[email protected])> Subject: Re: [Geoserver-users] Imagemosaic spanning the dateline That is encouraging. Trying it if I can figure the REST. While there is no accounting for some random consumer might request, any sensible query isn’t going to ask for the raster in anything but 3857 and it would make no sense outside SW Pacific. From: Andrea Aime mailto:[email protected])> Sent: Sunday, 28 October 2018 05:59 To: Phil Scadden mailto:[email protected])> Cc: GeoServer Mailing List List mailto:[email protected])> Subject: Re: [Geoserver-users] Imagemosaic spanning the dateline Before I waste a lot of time on something impossible, I thought I would ask whether it is okay to have an image mosaic that crosses the dateline. None of the granules cross the 180 (more accurately, the data is split into tiles that don’t cross the 180), but the mosaic itself will span a big hunk of the SW Pacific. CRS is 3857 for each tile. The reason I ask is the LL, UR coordinates for an envelope2d would violate the common assumption that LL x is < LR x that flat-earthers are so used to. Notice: This email and any attachments are confidential and may not be used, published or redistributed without the prior written consent of the Institute of Geological and Nuclear Sciences Limited (GNS Science). If received in error please destroy and immediately notify GNS Science. Do not copy or disclose the contents. Geoserver-users mailing list Please make sure you read the following two resources before posting to this

Re: [Geoserver-users] Imagemosaic spanning the dateline

2018-12-12 Thread Phil Scadden Any insight at all into the warning message would help. (Like what was code trying to do when it generated it). From: Phil Scadden Sent: Tuesday, 11 December 2018 10:06 To: GeoServer Mailing List List Subject: Re: [Geoserver-users] Imagemosaic spanning the dateline After a bit of battle getting disk provisioning, I have now successfully built an imagemozaic in EPSG:3857 which does cover both sides of the dateline. If I use “tiled” in getmap requests, it returns imagery for one side the dateline – if dateline is not in frame, you can get imagery for either side, but moment you have datetime in frame, then you get one side or other. I am about to analyse the getmap requests buts when I look in the logs, I see it is full of WARN message like this: 2018-12-11 09:52:09,214 WARN [lite.gridcoverage2d] - Could not reduce the grid geometry inside the valid area bounds: ReferencedEnvelope[-1.7976931348623157E308 : 1.7976931348623157E308, -85.0 : 85.0] Grid geometry isGridGeometry2D[GridEnvelope2D[0..1063, 0..1063], PARAM_MT["Affine", PARAMETER["num_row", 3], PARAMETER["num_col", 3], PARAMETER["elt_0_0", 9.554628534313876], PARAMETER["elt_0_2", 19841652.786989305], PARAMETER["elt_1_1", -9.554628534317445], PARAMETER["elt_1_2", -4118861.8190303175]]] The messages vary in terms of the elt_ parameters and the GridEnvelope2D content, but ALWAYS have ReferencedEnvelope[-1.7976931348623157E308 : 1.7976931348623157E308, -85.0 : 85.0] The lat/long bounding box on the layer is -179.99 -60.23 179. -19.3111 Can anyone tell me what the WARN message is about? (or should I give up now and create 2 imagemozaics, one for each side of the dateline). From: Phil Scadden mailto:[email protected]>> Sent: Monday, 29 October 2018 16:21 Cc: GeoServer Mailing List List mailto:[email protected]>> Subject: Re: [Geoserver-users] Imagemosaic spanning the dateline That is encouraging. Trying it if I can figure the REST. While there is no accounting for some random consumer might request, any sensible query isn’t going to ask for the raster in anything but 3857 and it would make no sense outside SW Pacific. From: Andrea Aime mailto:[email protected]>> Sent: Sunday, 28 October 2018 05:59 To: Phil Scadden mailto:[email protected]>> Cc: GeoServer Mailing List List mailto:[email protected]>> Subject: Re: [Geoserver-users] Imagemosaic spanning the dateline Hi Phil, we have done that in the past, even with granules spanning the dateline, using a heterogeneous CRS setup (each image in its own UTM zone, the ones crossing the dateline in UTM 1 or 60). That said, it's always tricky, so I won't promise it will work in your case. Having the source CRS in 3857, that will surely be source of troubles if someone asks the map in output in 4326, last time I stumbled in that case if the client asked for the entire globe to be displayed in 4326 the envelope reprojection would fail Cheers Andrea On Fri, Oct 26, 2018 at 2:35 AM Phil Scadden mailto:[email protected]>> wrote: Before I waste a lot of time on something impossible, I thought I would ask whether it is okay to have an image mosaic that crosses the dateline. None of the granules cross the 180 (more accurately, the data is split into tiles that don’t cross the 180), but the mosaic itself will span a big hunk of the SW Pacific. CRS is 3857 for each tile. The reason I ask is the LL, UR coordinates for an envelope2d would violate the common assumption that LL x is < LR x that flat-earthers are so used to. Notice: This email and any attachments are confidential and may not be used, published or redistributed without the prior written consent of the Institute of Geological and Nuclear Sciences Limited (GNS Science). If received in error please destroy and immediately notify GNS Science. Do not copy or disclose the contents. 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 If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected]<mailto:[email protected]> 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 55054 Mass

Re: [Geoserver-users] Imagemosaic spanning the dateline

2018-12-10 Thread Phil Scadden So with dateline east of the map centre line: https://data.gns.cri.nz/webmaps/petroleum/wms?service=WMS&request=GetMap&layers=gns%3Aswath&styles=&format=image%2Fpng&transparent=true&version=1.1.1&tiled=true&showOnSelector=false&height=256&width=256&srs=EPSG%3A3857&bbox=17532819.79994059,-5009377.085697311,18785164.07136492,-3757032.8142729844 returns nothing. https://data.gns.cri.nz/webmaps/petroleum/wms?service=WMS&request=GetMap&layers=gns%3Aswath&styles=&format=image%2Fpng&transparent=true&version=1.1.1&tiled=true&showOnSelector=false&height=256&width=256&srs=EPSG%3A3857&bbox=-20037508.342789244,-5009377.085697311,-18785164.07136492,-3757032.8142729844 returns a tile. Zoom into the western side and suddenly: https://data.gns.cri.nz/webmaps/petroleum/wms?service=WMS&request=GetMap&layers=gns%3Aswath&styles=&format=image%2Fpng&transparent=true&version=1.1.1&tiled=true&showOnSelector=false&height=256&width=256&srs=EPSG%3A3857&bbox=18941707.105292957,-3600489.7803449426,19098250.139220998,-3443946.7464169012 does return a tile. Beyond me why location of mapframe and zoom make a difference. Even when map frame is exclusively to west, only see tiles when I start to zoom in. the request URLs look correct to me and format unaffected by frame. No granule in the mosaic crosses the dateline. Sent: Tuesday, 11 December 2018 10:06 To: GeoServer Mailing List List Subject: Re: [Geoserver-users] Imagemosaic spanning the dateline After a bit of battle getting disk provisioning, I have now successfully built an imagemozaic in EPSG:3857 which does cover both sides of the dateline. If I use “tiled” in getmap requests, it returns imagery for one side the dateline – if dateline is not in frame, you can get imagery for either side, but moment you have datetime in frame, then you get one side or other. I am about to analyse the getmap requests buts when I look in the logs, I see it is full of WARN message like this: 2018-12-11 09:52:09,214 WARN [lite.gridcoverage2d] - Could not reduce the grid geometry inside the valid area bounds: ReferencedEnvelope[-1.7976931348623157E308 : 1.7976931348623157E308, -85.0 : 85.0] Grid geometry isGridGeometry2D[GridEnvelope2D[0..1063, 0..1063], PARAM_MT["Affine", PARAMETER["num_row", 3], PARAMETER["num_col", 3], PARAMETER["elt_0_0", 9.554628534313876], PARAMETER["elt_0_2", 19841652.786989305], PARAMETER["elt_1_1", -9.554628534317445], PARAMETER["elt_1_2", -4118861.8190303175]]] The messages vary in terms of the elt_ parameters and the GridEnvelope2D content, but ALWAYS have ReferencedEnvelope[-1.7976931348623157E308 : 1.7976931348623157E308, -85.0 : 85.0] The lat/long bounding box on the layer is -179.99 -60.23 179. -19.3111 Can anyone tell me what the WARN message is about? (or should I give up now and create 2 imagemozaics, one for each side of the dateline). From: Phil Scadden mailto:[email protected]>> Sent: Monday, 29 October 2018 16:21 Cc: GeoServer Mailing List List mailto:[email protected]>> Subject: Re: [Geoserver-users] Imagemosaic spanning the dateline That is encouraging. Trying it if I can figure the REST. While there is no accounting for some random consumer might request, any sensible query isn’t going to ask for the raster in anything but 3857 and it would make no sense outside SW Pacific. From: Andrea Aime mailto:[email protected]>> Sent: Sunday, 28 October 2018 05:59 To: Phil Scadden mailto:[email protected]>> Cc: GeoServer Mailing List List mailto:[email protected]>> Subject: Re: [Geoserver-users] Imagemosaic spanning the dateline Hi Phil, we have done that in the past, even with granules spanning the dateline, using a heterogeneous CRS setup (each image in its own UTM zone, the ones crossing the dateline in UTM 1 or 60). That said, it's always tricky, so I won't promise it will work in your case. Having the source CRS in 3857, that will surely be source of troubles if someone asks the map in output in 4326, last time I stumbled in that case if the client asked for the entire globe to be displayed in 4326 the envelope reprojection would fail Cheers Andrea On Fri, Oct 26, 2018 at 2:35 AM Phil Scadden mailto:[email protected]>> wrote: Before I waste a lot of time on something impossible, I thought I would ask whether it is okay to have an image mosaic that crosses the dateline. None of the granules cross the 180 (more accurately, the data is split into tiles that don’t cross the 180), but the mosaic itself will span a big hunk of the SW Pacific. CRS is 3857 for each tile. The reason I ask is the LL, UR coordinates for an envelope2d would violate the common

Re: [Geoserver-users] Imagemosaic spanning the dateline

2018-12-10 Thread Phil Scadden After a bit of battle getting disk provisioning, I have now successfully built an imagemozaic in EPSG:3857 which does cover both sides of the dateline. If I use “tiled” in getmap requests, it returns imagery for one side the dateline – if dateline is not in frame, you can get imagery for either side, but moment you have datetime in frame, then you get one side or other. I am about to analyse the getmap requests buts when I look in the logs, I see it is full of WARN message like this: 2018-12-11 09:52:09,214 WARN [lite.gridcoverage2d] - Could not reduce the grid geometry inside the valid area bounds: ReferencedEnvelope[-1.7976931348623157E308 : 1.7976931348623157E308, -85.0 : 85.0] Grid geometry isGridGeometry2D[GridEnvelope2D[0..1063, 0..1063], PARAM_MT["Affine", PARAMETER["num_row", 3], PARAMETER["num_col", 3], PARAMETER["elt_0_0", 9.554628534313876], PARAMETER["elt_0_2", 19841652.786989305], PARAMETER["elt_1_1", -9.554628534317445], PARAMETER["elt_1_2", -4118861.8190303175]]] The messages vary in terms of the elt_ parameters and the GridEnvelope2D content, but ALWAYS have ReferencedEnvelope[-1.7976931348623157E308 : 1.7976931348623157E308, -85.0 : 85.0] The lat/long bounding box on the layer is -179.99 -60.23 179. -19.3111 Can anyone tell me what the WARN message is about? (or should I give up now and create 2 imagemozaics, one for each side of the dateline). From: Phil Scadden Sent: Monday, 29 October 2018 16:21 Cc: GeoServer Mailing List List Subject: Re: [Geoserver-users] Imagemosaic spanning the dateline That is encouraging. Trying it if I can figure the REST. While there is no accounting for some random consumer might request, any sensible query isn’t going to ask for the raster in anything but 3857 and it would make no sense outside SW Pacific. From: Andrea Aime mailto:[email protected]>> Sent: Sunday, 28 October 2018 05:59 To: Phil Scadden mailto:[email protected]>> Cc: GeoServer Mailing List List mailto:[email protected]>> Subject: Re: [Geoserver-users] Imagemosaic spanning the dateline Hi Phil, we have done that in the past, even with granules spanning the dateline, using a heterogeneous CRS setup (each image in its own UTM zone, the ones crossing the dateline in UTM 1 or 60). That said, it's always tricky, so I won't promise it will work in your case. Having the source CRS in 3857, that will surely be source of troubles if someone asks the map in output in 4326, last time I stumbled in that case if the client asked for the entire globe to be displayed in 4326 the envelope reprojection would fail Cheers Andrea On Fri, Oct 26, 2018 at 2:35 AM Phil Scadden mailto:[email protected]>> wrote: Before I waste a lot of time on something impossible, I thought I would ask whether it is okay to have an image mosaic that crosses the dateline. None of the granules cross the 180 (more accurately, the data is split into tiles that don’t cross the 180), but the mosaic itself will span a big hunk of the SW Pacific. CRS is 3857 for each tile. The reason I ask is the LL, UR coordinates for an envelope2d would violate the common assumption that LL x is < LR x that flat-earthers are so used to. Notice: This email and any attachments are confidential and may not be used, published or redistributed without the prior written consent of the Institute of Geological and Nuclear Sciences Limited (GNS Science). If received in error please destroy and immediately notify GNS Science. Do not copy or disclose the contents. 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 If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected]<mailto:[email protected]> 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 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che

Re: [Geoserver-users] ImageMosaic Schema Index

2018-11-17 Thread Andrea Aime Hi Marc, no, there is currently no config that would make the mosaic create an index on a database column. However, the JDBC data stores expose a createIndex method, so it would be possible to add a config and make it go, if the backing store is a database, with some coding. Cheers Andrea On Fri, Nov 16, 2018 at 6:25 PM Marc DiPasquale wrote: > Is it possible to create a database index on one of the columns in a > schema being defined via indexer.xml and _auxiliary.xml when creating an > ImageMosaic store? > Let's use an example from the docssay we wanted to create a database > index on "updated" is there a way to define that in the config below? > 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 > If you want to request a feature or an improvement, also see this: > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > [email protected] > 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 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- *Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.* 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 If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users That is encouraging. Trying it if I can figure the REST. While there is no accounting for some random consumer might request, any sensible query isn’t going to ask for the raster in anything but 3857 and it would make no sense outside SW Pacific. From: Andrea Aime Sent: Sunday, 28 October 2018 05:59 To: Phil Scadden Cc: GeoServer Mailing List List Subject: Re: [Geoserver-users] Imagemosaic spanning the dateline Hi Phil, we have done that in the past, even with granules spanning the dateline, using a heterogeneous CRS setup (each image in its own UTM zone, the ones crossing the dateline in UTM 1 or 60). That said, it's always tricky, so I won't promise it will work in your case. Having the source CRS in 3857, that will surely be source of troubles if someone asks the map in output in 4326, last time I stumbled in that case if the client asked for the entire globe to be displayed in 4326 the envelope reprojection would fail Cheers Andrea On Fri, Oct 26, 2018 at 2:35 AM Phil Scadden mailto:[email protected]>> wrote: Before I waste a lot of time on something impossible, I thought I would ask whether it is okay to have an image mosaic that crosses the dateline. None of the granules cross the 180 (more accurately, the data is split into tiles that don’t cross the 180), but the mosaic itself will span a big hunk of the SW Pacific. CRS is 3857 for each tile. The reason I ask is the LL, UR coordinates for an envelope2d would violate the common assumption that LL x is < LR x that flat-earthers are so used to. Notice: This email and any attachments are confidential and may not be used, published or redistributed without the prior written consent of the Institute of Geological and Nuclear Sciences Limited (GNS Science). If received in error please destroy and immediately notify GNS Science. Do not copy or disclose the contents. 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 If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected]<mailto:[email protected]> 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 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail. Notice: This email and any attachments are confidential and may not be used, published or redistributed without the prior written consent of the Institute of Geological and Nuclear Sciences Limited (GNS Science). If received in error please destroy and immediately notify GNS Science. Do not copy or disclose the contents. 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 If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users Hi Phil, we have done that in the past, even with granules spanning the dateline, using a heterogeneous CRS setup (each image in its own UTM zone, the ones crossing the dateline in UTM 1 or 60). That said, it's always tricky, so I won't promise it will work in your case. Having the source CRS in 3857, that will surely be source of troubles if someone asks the map in output in 4326, last time I stumbled in that case if the client asked for the entire globe to be displayed in 4326 the envelope reprojection would fail Cheers Andrea On Fri, Oct 26, 2018 at 2:35 AM Phil Scadden wrote: > Before I waste a lot of time on something impossible, I thought I would > ask whether it is okay to have an image mosaic that crosses the dateline. > None of the granules cross the 180 (more accurately, the data is split into > tiles that don’t cross the 180), but the mosaic itself will span a big hunk > of the SW Pacific. CRS is 3857 for each tile. The reason I ask is the LL, > UR coordinates for an envelope2d would violate the common assumption that > LL x is < LR x that flat-earthers are so used to. > Notice: This email and any attachments are confidential and may not be > used, published or redistributed without the prior written consent of the > Institute of Geological and Nuclear Sciences Limited (GNS Science). If > received in error please destroy and immediately notify GNS Science. Do not > copy or disclose the contents. > 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 > If you want to request a feature or an improvement, also see this: > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > [email protected] > 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 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it --- *Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.* 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 If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users but i have always the same results. You have other idea can I try? I don't know if is correct, but can I make transparency in my sld for "NaN" value? Thanks, Peppe 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 If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users Hi Peppe, GeoServer 2.8.0 is probably just too old to have a meaningful discuss about it, I'd first recommend to upgrade to 2.12.x Since you have data with NODATA embedded, I would suggest to then enable JAI_EXT and let it handle it without fiddling with background colors, input transparent color and output transparent color (btw, the last two are colors, they do not make sense if the mosaic is made of scientific data, at least as far as I know). JAI_EXT is not enabled by default, you'll have to set up a system variable to kick it on: http://docs.geoserver.org/stable/en/user/configuration/image_processing/index.html#jai-ext Cheers Andrea On Thu, Jan 11, 2018 at 2:41 PM, peppe wrote: > Dear Geoserver Users, > I'm trying to display imagemosaic where image are irregular and near each > other. > Imagemosaic are displayed with a SLD > Images overlap and no transparency is applied > When publish imagemosaic, i set BackgroundValues as -999 > If try to set InputTransparentColor or OutputTransparentColor, but I have > exception on geoserver. > I use: > geoserver 2.8.0 > apache-tomcat-7.0.57 with java 1.8.0_101 64bit > windows7 > My SLD looks like this: >xmlns="http://www.opengis.net/sld"; xmlns:ogc="http://www.opengis.net/ogc > xmlns:xlink="http://www.w3.org/1999/xlink"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://www.opengis.net/sld > http://schemas.opengis.net/sld/1.0.0/StyledLayerDescriptor.xsd";> > gtopo > NDVI style > NDVI color progression >opacity="0.0"/> >opacity="1.0"/> >label="values" > opacity="1.0"/> >label="values" > opacity="1.0"/> >label="values" > opacity="1.0"/> >opacity="1.0"/> >label="values" > opacity="1.0"/> >opacity="1.0"/> >label="values" > opacity="1.0"/> >opacity="1.0"/> > gdal info image (no data value is -999) > E:\DevApps\testCaseImageMosaic>gdalinfo > 180690_92_S2A_MSIL2A_20180106T100401_N0206_R122_T32TQQ_20180106T120734.tif > Driver: GTiff/GeoTIFF > Files: > 180690_92_S2A_MSIL2A_20180106T100401_N0206_R122_T32TQQ_20180106T120734.tif > Size is 943, 606 > Coordinate System is: > GEOGCS["WGS 84", > DATUM["WGS_1984", > SPHEROID["WGS 84",6378137,298.257223563, > AUTHORITY["EPSG","7030"]], > AUTHORITY["EPSG","6326"]], > PRIMEM["Greenwich",0], > UNIT["degree",0.0174532925199433], > AUTHORITY["EPSG","4326"]] > Origin = (12.281968477673896,45.019667104849084) > Pixel Size = (0.15804510078,-0.15804510078) > Metadata: > AREA_OR_POINT=Area > Image Structure Metadata: > INTERLEAVE=BAND > Corner Coordinates: > Upper Left ( 12.2819685, 45.0196671) ( 12d16'55.09"E, 45d 1'10.80"N) > Lower Left ( 12.2819685, 45.0100896) ( 12d16'55.09"E, 45d 0'36.32"N) > Upper Right ( 12.2968721, 45.0196671) ( 12d17'48.74"E, 45d 1'10.80"N) > Lower Right ( 12.2968721, 45.0100896) ( 12d17'48.74"E, 45d 0'36.32"N) > Center ( 12.2894203, 45.0148783) ( 12d17'21.91"E, 45d 0'53.56"N) > Band 1 Block=943x2 Type=Float32, ColorInterp=Gray > NoData Value=-999 > I tried to use other geoserver, but i have exception whene publish > imagemosaic: > GeoServer 2.12.1: imagemosaic doesn't work > GeoServer 2.11.4: imagemosaic doesn't work > 10 gen 15:55:13 INFO [geoserver.web] - Getting list of coverages for saved > store file://E:\DevApps\testCaseImageMosaic > java.lang.RuntimeException: Could not list layers for this store, an error > occurred retrieving them: Failed to create reader from > file://E:\DevApps\testCaseImageMosaic and hints null > org.geoserver.web.data.layer.NewLayerPageProvider.getItemsInternal( > NewLayerPageProvider.java:158) > GeoServer 2.10.5: imagemosaic doesn't work > 10 gen 16:18:00 WARN [geoserver.catalog] - Unable to convert coverage URL > a URI, attempting to use it as a path > 10 gen 16:18:00 INFO [geoserver.web] - Getting list of coverages for saved > store file://E:\DevApps\testCaseImageMosaic > java.lang.RuntimeException: Could not list layers for this store, an error > occurred retrieving them: Failed to create reader from > file://E:\DevApps\testCaseImageMosaic and hints null > overlap imagemosaic with geoserver > original images in arcgis > original_image_in_arcgis.png> > Someone can help us to solve this problem? > Thanks a lot > 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

Re: [Geoserver-users] ImageMosaic plugin configuration files documentation

2017-08-25 Thread Andrea Aime Hi Marco, you're not the only one, just today I was looking for one of the many properties mosaic exposes and it's nowhere to be found in the documentation, I had to search in the sources (and as usual running against a deadline, so no time contribute the missing bits to it). In any case, there is another documentation set here: http://geoserver.geo-solutions.it/edu/en/multidim/imagemosaic/ Maybe that will be useful. In case that helps and you can give back to the project, documentation improvements are most welcomed, there is a guide here to make quick fixes: http://docs.geoserver.org/latest/en/docguide/quickfix.html Cheers Andrea On Thu, Aug 24, 2017 at 8:32 AM, Marco Tosato wrote: > Hello everyone! > I'm experimenting with ImageMosaic plugin, I studied the documentation > from the GeoServer User Manual and performed some test, but I'm unable to > find a place where the configuration files directived are explained in > details. > I also found some misplaced directives in the GeoServer User Manual, for > example the following directives > LocationAttribute > TimeAttribute > AdditionalDomainAttribute > are all to be placed inside the* **.properties* file (as > per test performed on GeoServer directly) wile the User Manual states that > the TimeAttribute should be placed in *index.properties* file. > I would like to have a deeper understanding of ImageMosaic configuration > files, is there a place where the parameters to be placed inside the > *.properties files are described? I found myself in trouble because > GeoServer User Manual does not describe the AdditionalDomainAttribute and > does not specifyes which property collectors are availeble. > I'm I looking in the wrong place searching for the .properties files > documentation in GeoServer User Manual? Maybe there is some plug-in > specific documentation I was unable to find? > Thanks a lot for your help :) > Marco > PS: my setup is as follow >- GeoServer Version 2.11.2 >- GeoTools Version 17.2 >- GeoWebCache Version 1.11.1 >- Tomcat8 8.0.32-1ubuntu1.4 >- Ubuntu 16.04 > The ImageMosaic plug-in is the one distributed with GeoServer 2.11.2 WAR > GeoServer have been deployed via WAR file. > 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 > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users 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 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or 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

Re: [Geoserver-users] ImageMosaic stitching precision

2017-04-13 Thread Arnaud L. Le 13/04/2017 à 11:49, Andrea Aime a écrit : > Ideally, try to setup a new mosaic with just 2 granules, with a > shapefile index, and see if you can reproduce the problem. > Increase the number of granules until you can, then pack everything into > a zip file and attach it to an issue in Jira. OK, I'll do that ASAP. Probably not this week though. > Just to be sure, are you reprojecting the data? If you are, it would be > sort of normal to have such jump every now and then. AFAIK, no. I'm trying very hard not to reproject, but indeed this does looks like a reprojection jump. The tif is in EPSG:32631 (but it has no .prf file, only a .tfw file), the imagemosaic is configured with native src EPSG:32631 and data src EPSG:32631. I am querying this layer via wms and specifying CRS=EPSG:32631. That's all I can think of. The only problem I see is that the tif have no prj files, but since the mosaic is defined with the correct data src I think it should not matter, right ? Regards Arnaud 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users > I'd be glad to help you with this. > What should I provide to make it easy to replicate this ? Ideally, try to setup a new mosaic with just 2 granules, with a shapefile index, and see if you can reproduce the problem. Increase the number of granules until you can, then pack everything into a zip file and attach it to an issue in Jira. Just to be sure, are you reprojecting the data? If you are, it would be sort of normal to have such jump every now and then. It could be improved I believe, but definitely not trivial (be prepared to sponsor some development or in that case). Cheers Andrea 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 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users Le 13/04/2017 à 10:09, Andrea Aime a écrit : > On Wed, Apr 12, 2017 at 2:12 PM, Arnaud L. > wrote: > Trying to make a sample dataset I realized that this was not a > stitching problem, because the glitch is inside a tile, not on a > border between tiles. > So this is something totally different I believe... or is it not ? > It may be, hard to tell what is it without actually looking into it I'd be glad to help you with this. What should I provide to make it easy to replicate this ? I can provide the corresponding tiff with its world file, but will it be enough ? The index is in a postgis database, so I could dump the appropriate line ? Regards Arnaud 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users On Wed, Apr 12, 2017 at 2:12 PM, Arnaud L. wrote: > Trying to make a sample dataset I realized that this was not a stitching > problem, because the glitch is inside a tile, not on a border between tiles. > So this is something totally different I believe... or is it not ? It may be, hard to tell what is it without actually looking into it Cheers Andrea 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 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users > in my case I’m also using CF-compliant netCDF and haven’t needed to make > world files. Geoserver creates dot files as part of imagemosaic creation, > which I have not inspected closely (index data? I should go and look). > > If I am understanding your responses it sounds like the tiling behavior > should work with world files (possibly generated by GeoServer) and by > having correct information in user_projections/netcdf.projections.properties, > indexer.xml, ancillary.xml, and datastore.properties in the directory as > usual. GeoServer will then automatically detect that these netCDF files > are geographic tiles and create a store/layer appropriately. > This is pretty much how it worked for me. I would check also that the > directory where your data are writeable by tomcat? I presume so if it’s > creating dot files > > Thanks for the reference to the REST API, but I am starting out small > with a handful of files (eight files) before I expand to the full set. > However, each time I try pointing GeoServer to my directory when adding a > store (through the web UI) it has repeatedly failed on a variety of issues > depending on small changes in my input files and/or configuration. The > world files might be the problem for me, but otherwise it seems likely that > there are other errors that may be happening before the geographic tiling > is performed. > I did a lot of reading geoserver logs to find out where all my bugs were > and zap them one at a time. I won’t get back to attempting RESTful creation > of my massive mosaic until May - but maybe some other folks can assist? > Also, I based my entire procedure on this really useful resource: > https://github.com/bencaradocdavies/geoserver/wiki/RAP-Native-Grid- > ImageMosaic 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users Le 12/04/2017 à 13:59, Andrea Aime a écrit : > That setting is used only while reprojecting, has no control over stitching. > For the residual issues, plan B, "open a ticket in the bug tracker with > sample data and > requests showing the issue, so that developers can debug it on their own > machine" Trying to make a sample dataset I realized that this was not a stitching problem, because the glitch is inside a tile, not on a border between tiles. So this is something totally different I believe... or is it not ? PS : Of course I checked the tile itself and it looks good, the glitch is only on the WMS representation. Regards Arnaud 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users On Wed, Apr 12, 2017 at 1:17 PM, Arnaud L. wrote: > 2.11.0 does help, thanks ! I don't have black lines anymore. > I still do have some stitching problems though, as illustrated here : > http://i.imgur.com/0VUlYWU.png > I tries with both "accurate resolution computation" on and off, but this > setting has no effect on the problem. That setting is used only while reprojecting, has no control over stitching. For the residual issues, plan B, "open a ticket in the bug tracker with sample data and requests showing the issue, so that developers can debug it on their own machine" Cheers Andrea 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 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users Le 12/04/2017 à 10:35, Arnaud L. a écrit : > Le 12/04/2017 à 10:28, Andrea Aime a écrit : >> I've recently made a change that _might_ >> help: https://osgeo-org.atlassian.net/browse/GEOT-5615 >> The fix is present in GeoServer 2.10.2 and 2.11.0. If you are not using >> them, I'd suggest to upgrade and >> see if that helps, > Indeed, I'm still on 2.8.4. I'll give 2.11.0 a try ASAP, hoping that the > upgrade will go smoothly. 2.11.0 does help, thanks ! I don't have black lines anymore. I still do have some stitching problems though, as illustrated here : http://i.imgur.com/0VUlYWU.png I tries with both "accurate resolution computation" on and off, but this setting has no effect on the problem. BTW, 2.8.4 was running without JAI (it was a mistake, because of an update of the JRE), and 2.11.0 is running with JAI. I don't know if this alone could explain the difference. Also I am running with multithreading on and therefore JAI ImageRead off, so I'm not sure that JAI is used anyway. Regards Arnaud 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users Le 12/04/2017 à 10:28, Andrea Aime a écrit : > I've recently made a change that _might_ > help: https://osgeo-org.atlassian.net/browse/GEOT-5615 > The fix is present in GeoServer 2.10.2 and 2.11.0. If you are not using > them, I'd suggest to upgrade and > see if that helps, Indeed, I'm still on 2.8.4. I'll give 2.11.0 a try ASAP, hoping that the upgrade will go smoothly. I'll keep you informed, and I'll have a look at the tracker anyway. Thanks again ! Arnaud 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users Hi Arnaud, honestly I don't know, seems like an arithmetic issue happening somewhere in the mosaicking code. I've recently made a change that _might_ help: https://osgeo-org.atlassian.net/browse/GEOT-5615 The fix is present in GeoServer 2.10.2 and 2.11.0. If you are not using them, I'd suggest to upgrade and see if that helps, if you're already there instead, open a ticket in the bug tracker with sample data and requests showing the issue, so that developers can debug it on their own machine Cheers Andrea On Wed, Apr 12, 2017 at 9:39 AM, Arnaud L. wrote: > Hi all, > I have set up an ImageMosaic store with existing TIFF tiles. They are > not GeoTIFFs, but regular TIFF files with worldfiles. > The index is stored in PostGIS (the information was already present > there, I only had to create a view to match the index schema). > In some cases, the stitching of rasters is not perfect and a black line > appears between tiles. > The rasters are in EPSG:32631, and I am also querying GeoServer's WMS in > EPSG:32631, so no reprojection is done. > The rasters are all 1000 pixels in widht and height, the resolution is > 0.15875 (in EPSG 32631, so 0.15875 m/pix), so each raster is 158.75m in > width and height. > Here is an example request, and the resulting raster : > WMS url : > http://localhost/geoserver/dev/wms?SERVICE=WMS&VERSION=1. > 3.0&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true& > LAYERS=dev%3Ageorasters_test&CRS=EPSG%3A32631&STYLES&WIDTH= > 1920&HEIGHT=1349&BBOX=742405.64625%2C5087266.7415625% > 2C742710.44625%2C5087480.895312501 > Raster : http://i.imgur.com/pE2H4QJ.png > Slightly changing the bbox fixes things up (1 meter to the east) : > WMS url : > http://localhost/geoserver/dev/wms?SERVICE=WMS&VERSION=1. > 3.0&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true& > LAYERS=dev%3Ageorasters_test&CRS=EPSG%3A32631&STYLES&WIDTH= > 1920&HEIGHT=1349&BBOX=742406.64625%2C5087266.741562501% > 2C742711.44625%2C5087480.895312501 > Raster : http://i.imgur.com/PjflMLd.png > In my GeoServer layer's configuration, I have tried with "Accurate > resolution computation" to true and false, to no avail (both examples > above are with this setting set to true). > Is there any other setting controlling the stitching mechanism ? > Where could be the problem here ? In the index, or in the data ? Both > are supposed to be 100% accurate, and indeed the both work without > problem with another stitching library (no idea what it is exactly, it's > a custom dll developed by a third party in .NET). > Thanks a lot for your help ! > Arnaud > 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 > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users 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 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result

Re: [Geoserver-users] ImageMosaic with tiled data

2017-04-11 Thread Andrea Aime On Wed, Apr 12, 2017 at 1:40 AM, Adam Steer wrote: > HI Aaron > in my case I’m also using CF-compliant netCDF and haven’t needed to make > world files. Geoserver creates dot files as part of imagemosaic creation, > which I have not inspected closely (index data? I should go and look). Yep, they are index files used to locate the data inside the netcdf without having to re-parse its headers every time. I did a lot of reading geoserver logs to find out where all my bugs were > and zap them one at a time. I won’t get back to attempting RESTful creation > of my massive mosaic until May - but maybe some other folks can assist? > Also, I based my entire procedure on this really useful resource: > https://github.com/bencaradocdavies/geoserver/wiki/RAP-Native-Grid- > ImageMosaic Now that would make for a nice tutorial in the official guide, if anyone is interested in translating the markdown to rst Cheers Andrea 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 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users in my case I’m also using CF-compliant netCDF and haven’t needed to make world files. Geoserver creates dot files as part of imagemosaic creation, which I have not inspected closely (index data? I should go and look). > If I am understanding your responses it sounds like the tiling behavior > should work with world files (possibly generated by GeoServer) and by having > correct information in user_projections/netcdf.projections.properties, > indexer.xml, ancillary.xml, and datastore.properties in the directory as > usual. GeoServer will then automatically detect that these netCDF files are > geographic tiles and create a store/layer appropriately. This is pretty much how it worked for me. I would check also that the directory where your data are writeable by tomcat? I presume so if it’s creating dot files > Thanks for the reference to the REST API, but I am starting out small with a > handful of files (eight files) before I expand to the full set. However, > each time I try pointing GeoServer to my directory when adding a store > (through the web UI) it has repeatedly failed on a variety of issues > depending on small changes in my input files and/or configuration. The world > files might be the problem for me, but otherwise it seems likely that there > are other errors that may be happening before the geographic tiling is > performed. I did a lot of reading geoserver logs to find out where all my bugs were and zap them one at a time. I won’t get back to attempting RESTful creation of my massive mosaic until May - but maybe some other folks can assist? Also, I based my entire procedure on this really useful resource: https://github.com/bencaradocdavies/geoserver/wiki/RAP-Native-Grid-ImageMosaic 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users Thanks for the information. My netCDF files are CF-compliant and are readable and geo-locatable in all of the netCDF tools I am using. When you mention world files, what do you mean? Do you mean that the netCDF data be CF-compliant and be geo-located or something else entirely? If it is a separate file, can you refer me to an example? I have seen GeoServer sometimes create hidden (i.e., ".20170331T1615Z_3376911e8b9a4c789001ddeb28f4a90e75a1") directories but not sure if this is the same thing. Are these the automatically created files Adam is referring to? If they are separate files, is there a way to easily generate them from netCDF files? If I am understanding your responses it sounds like the tiling behavior should work with world files (possibly generated by GeoServer) and by having correct information in user_projections/netcdf.projections.properties, indexer.xml, ancillary.xml, and datastore.properties in the directory as usual. GeoServer will then automatically detect that these netCDF files are geographic tiles and create a store/layer appropriately. Thanks for the reference to the REST API, but I am starting out small with a handful of files (eight files) before I expand to the full set. However, each time I try pointing GeoServer to my directory when adding a store (through the web UI) it has repeatedly failed on a variety of issues depending on small changes in my input files and/or configuration. The world files might be the problem for me, but otherwise it seems likely that there are other errors that may be happening before the geographic tiling is performed. Aaron On Thu, Apr 6, 2017 at 8:32 PM, Adam Steer wrote: > Hi Aaron - with netCDF files I’ve used a postGIS store to index the data > and then create an imagemosaic store. > I’ve been meaning to test a very large mosaic - which needs some care to > build [1]. My process is described after Daniele’s comments - it works fine > for a few hundred tiles but not for many thousands with interesting > reference systems :) > But in short, yes, and with netCDF, and with a world file for each > (although Geoserver will create it’s own indexing parts - so the data > directory needs to be writable by tomcat. We link files from our RO > filesystem into someplace on the geoserver host to enable this) > Cheers > [1] https://sourceforge.net/p/geoserver/mailman/message/35736574/ > Dr. Adam Steer > Earth systems data service specialist > National Computational Infrastructure > Leonard Huxley Building, Mills Road > The Australian National University > Acton ACT 2600 Australia > [email protected] > +61 2 6125 1413 > http://nci.org.au > > On 7 Apr 2017, at 12:44 am, Jason Newmoyer > wrote: > > As long as the tiles have geographic metadata (world file, geotiff, etc) > then ImageMosaic will automatically index them with a shapefile. You just > point the new store to the directory containing all of the tiles when > creating it. > > Jason Newmoyer > > Newmoyer Geospatial Solutions > > 843.606.0424 > > [email protected] > > On Wed, Apr 5, 2017 at 5:40 PM, Aaron Braeckel > wrote: > > Hello, > > I am trying to determine if ImageMosaic can be used to gather and > re-assemble tiles into a virtual mosaic. I am using ImageMosaic (as > opposed to ImagePyramid) since we need to aggregate our weather data across > time and elevation and other custom dimensions. The files I am receiving > have tile indices indicating their physical location relative to one > another, but I have yet to find any ImageMosaic indexer option to aggregate > them into a geographic mosaic. > > For example I have several files with information similar to the > following, where "T01" refers to the tile index from 1 to 4 (T01 is upper > left, T02 is upper right, etc.): > > 20170331T1645Z_SITE_FIELD_T01.nc > > 20170331T1645Z_SITE_FIELD_T02.nc > > 20170331T1645Z_SITE_FIELD_T03.nc > > 20170331T1645Z_SITE_FIELD_T04.nc > > In several areas of the GeoServer documentation it seems to be saying > that this can be done but I have not found any configuration mechanism to > do so. Is there any way to configure the indexer.xml file to reassemble > these files into a single, virtual dataset? While I can re-assemble these > tiles into the mosaic myself and use those in GeoServer it is not the most > desirable option due to the data volumes. > > Thanks! > > Aaron > > 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 > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] ImageMosaic with tiled data

2017-04-06 Thread Adam Steer Hi Aaron - with netCDF files I’ve used a postGIS store to index the data and then create an imagemosaic store. I’ve been meaning to test a very large mosaic - which needs some care to build [1]. My process is described after Daniele’s comments - it works fine for a few hundred tiles but not for many thousands with interesting reference systems :) But in short, yes, and with netCDF, and with a world file for each (although Geoserver will create it’s own indexing parts - so the data directory needs to be writable by tomcat. We link files from our RO filesystem into someplace on the geoserver host to enable this) Cheers [1] https://sourceforge.net/p/geoserver/mailman/message/35736574/ Dr. Adam Steer Earth systems data service specialist National Computational Infrastructure Leonard Huxley Building, Mills Road The Australian National University Acton ACT 2600 Australia [email protected] +61 2 6125 1413 http://nci.org.au > On 7 Apr 2017, at 12:44 am, Jason Newmoyer > wrote: > As long as the tiles have geographic metadata (world file, geotiff, etc) then > ImageMosaic will automatically index them with a shapefile. You just point > the new store to the directory containing all of the tiles when creating it. > Jason Newmoyer > Newmoyer Geospatial Solutions > 843.606.0424 > [email protected] > On Wed, Apr 5, 2017 at 5:40 PM, Aaron Braeckel wrote: > Hello, > I am trying to determine if ImageMosaic can be used to gather and re-assemble > tiles into a virtual mosaic. I am using ImageMosaic (as opposed to > ImagePyramid) since we need to aggregate our weather data across time and > elevation and other custom dimensions. The files I am receiving have tile > indices indicating their physical location relative to one another, but I > have yet to find any ImageMosaic indexer option to aggregate them into a > geographic mosaic. > For example I have several files with information similar to the following, > where "T01" refers to the tile index from 1 to 4 (T01 is upper left, T02 is > upper right, etc.): > 20170331T1645Z_SITE_FIELD_T01.nc > 20170331T1645Z_SITE_FIELD_T02.nc > 20170331T1645Z_SITE_FIELD_T03.nc > 20170331T1645Z_SITE_FIELD_T04.nc > In several areas of the GeoServer documentation it seems to be saying that > this can be done but I have not found any configuration mechanism to do so. > Is there any way to configure the indexer.xml file to reassemble these files > into a single, virtual dataset? While I can re-assemble these tiles into the > mosaic myself and use those in GeoServer it is not the most desirable option > due to the data volumes. > Thanks! > Aaron > 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 > [email protected] > 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 > [email protected] > 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users As long as the tiles have geographic metadata (world file, geotiff, etc) then ImageMosaic will automatically index them with a shapefile. You just point the new store to the directory containing all of the tiles when creating it. Jason Newmoyer Newmoyer Geospatial Solutions 843.606.0424 [email protected] On Wed, Apr 5, 2017 at 5:40 PM, Aaron Braeckel wrote: > Hello, > I am trying to determine if ImageMosaic can be used to gather and > re-assemble tiles into a virtual mosaic. I am using ImageMosaic (as > opposed to ImagePyramid) since we need to aggregate our weather data across > time and elevation and other custom dimensions. The files I am receiving > have tile indices indicating their physical location relative to one > another, but I have yet to find any ImageMosaic indexer option to aggregate > them into a geographic mosaic. > For example I have several files with information similar to the > following, where "T01" refers to the tile index from 1 to 4 (T01 is upper > left, T02 is upper right, etc.): > 20170331T1645Z_SITE_FIELD_*T01*.nc > 20170331T1645Z_SITE_FIELD_*T02*.nc > 20170331T1645Z_SITE_FIELD_*T03.*nc > 20170331T1645Z_SITE_FIELD_*T04*.nc > In several areas of the GeoServer documentation it seems to be saying that > this can be done but I have not found any configuration mechanism to do > so. Is there any way to configure the indexer.xml file to reassemble these > files into a single, virtual dataset? While I can re-assemble these tiles > into the mosaic myself and use those in GeoServer it is not the most > desirable option due to the data volumes. > Thanks! > Aaron > 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 > [email protected] > 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users Hi Daniele I didn’t see that part of the documentation, and haven’t copied the imageio jar to the right place - I’ll test this tomorrow (GMT+11) and report back… Thanks! > On 19 Dec 2016, at 9:59 pm, Daniele Romagnoli > wrote: > Hi Adam, > today I have investigated on a very similar issue for a colleague. I think I > have found the cause of your previous problem with GDAL. > Long story short, as part of GEOS-7578 the GDAL bindings jar has been removed > from the imageio-ext geoserver extension zip so that you have to manually > install it in WEB-INF lib in order to have the GDAL extensions properly > working. > The GeoServer GDAL documentation has also been updated: > http://docs.geoserver.org/stable/en/user/data/raster/gdal.html#installing-gdal-native-libraries > with this line: > From the javainfo directory in the archive, copy the > imageio-ext-gdal-bindings-1.9.2.jar to the WEB-INF/lib directory of your > GeoServer installation. > Do you remember if you did that? > Cheers, > Daniele > On Wed, Nov 30, 2016 at 7:49 AM, Adam Steer wrote: > Thanks Daniele - delayed also here due to work ‘stuff’. > I just got to setting up a new instance of geoserver (master/latest, deployed > from the nightly war file) for testing. it showed the same errors as my 2.10 > attempt - until I removed the GDAL plugin. > So far the imagemosaic part is working now! (no GDAL plugin) > Anyway - I found tomcat’s ‘localhost’ log so I’ll purposely break it tomorrow > and post some log outputs (linked at github.io)… > Regards > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. > Ing. Daniele Romagnoli > Senior Software Engineer > GeoSolutions S.A.S. > Via di Montramito 3/A > 55054 Massarosa (LU) > Italy > phone: +39 0584 962313 > fax: +39 0584 1660272 > http://www.geo-solutions.it > http://twitter.com/geosolutions_it > AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 > Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i > file/s allegato/i sono da considerarsi strettamente riservate. Il loro > utilizzo è consentito esclusivamente al destinatario del messaggio, per le > finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio > senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia > via e-mail e di procedere alla distruzione del messaggio stesso, > cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo > anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per > finalità diverse, costituisce comportamento contrario ai principi dettati dal > D.Lgs. 196/2003. > The information in this message and/or attachments, is intended solely for > the attention and use of the named addressee(s) and may be confidential or > proprietary in nature or covered by the provisions of privacy act > (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection > Code).Any use not in accord with its purpose, any disclosure, reproduction, > copying, distribution, or either dissemination, either whole or partial, is > strictly forbidden except previous formal approval of the named addressee(s). > If you are not the intended recipient, please contact immediately the sender > by telephone, fax or e-mail and delete the information in this message that > has been received in error. The sender does not give any warranty or accept > liability as the content, accuracy or 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users Hi Adam, today I have investigated on a very similar issue for a colleague. I think I have found the cause of your previous problem with GDAL. Long story short, as part of GEOS-7578 the GDAL bindings jar has been removed from the imageio-ext geoserver extension zip so that you have to manually install it in WEB-INF lib in order to have the GDAL extensions properly working. The GeoServer GDAL documentation has also been updated: http://docs.geoserver.org/stable/en/user/data/raster/gdal.html#installing-gdal-native-libraries with this line: >From the javainfo directory in the archive, copy the imageio-ext-gdal-bindings-1.9.2.jar to the WEB-INF/lib directory of your GeoServer installation. Do you remember if you did that? Cheers, Daniele On Wed, Nov 30, 2016 at 7:49 AM, Adam Steer wrote: > Thanks Daniele - delayed also here due to work ‘stuff’. > I just got to setting up a new instance of geoserver (master/latest, > deployed from the nightly war file) for testing. it showed the same errors > as my 2.10 attempt - until I removed the GDAL plugin. > So far the imagemosaic part is working now! (no GDAL plugin) > Anyway - I found tomcat’s ‘localhost’ log so I’ll purposely break it > tomorrow and post some log outputs (linked at github.io)… > Regards GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. Ing. Daniele Romagnoli Senior Software Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users Thanks Daniele - delayed also here due to work ‘stuff’. I just got to setting up a new instance of geoserver (master/latest, deployed from the nightly war file) for testing. it showed the same errors as my 2.10 attempt - until I removed the GDAL plugin. So far the imagemosaic part is working now! (no GDAL plugin) Anyway - I found tomcat’s ‘localhost’ log so I’ll purposely break it tomorrow and post some log outputs (linked at github.io)… Regards Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users to recall the problem: > >> > I am using Geoserver 2.7.5. I want to create a layer out of several > >> > geotiffs so I created an imagemosaic. The geotiffs are 32bit tifs an I > >> > want to colorize them using Geoserver Styles. The single tifs overlap at > >> > the edges and partly have no data values there which appear in the > >> > mosaic. To avoid that I wanted to set the "Input Transparent Color". But > >> > when setting a value I get an Error: > >> > org.geotools.data.DataSourceException: Unable to create this mosaic > >> > org.geotools.gce.imagemosaic.RasterLayerResponse.prepareResponse(RasterLayerResponse.java:1336) > >> > org.geotools.gce.imagemosaic.RasterLayerResponse.processRequest(RasterLayerResponse.java:1226) > >> > org.geotools.gce.imagemosaic.RasterLayerResponse.createResponse(RasterLayerResponse.java:1192) > >> > org.geotools.gce.imagemosaic.RasterManager.read(RasterManager.java:1153) > >> > org.geotools.gce.imagemosaic.ImageMosaicReader.read(ImageMosaicReader.java:874) > >> > org.geotools.gce.imagemosaic.ImageMosaicReader.read(ImageMosaicReader.java:853) > >> > org.geoserver.catalog.SingleGridCoverage2DReader.read(SingleGridCoverage2DReader.java:147) > >> > org.geoserver.catalog.CoverageDimensionCustomizerReader.read(CoverageDimensionCustomizerReader.java:227) > >> > org.geoserver.catalog.CoverageDimensionCustomizerReader.read(CoverageDimensionCustomizerReader.java:217) > >> > org.geoserver.wms.featureinfo.RasterLayerIdentifier.identify(RasterLayerIdentifier.java:170) > >> > org.geoserver.wms.GetFeatureInfo.execute(GetFeatureInfo.java:78) > >> > at org.geoserver.wms.GetFeatureInfo.run(GetFeatureInfo.java:44) > >> > ... 107 more > >> > Caused by: java.lang.IllegalStateException: Unsupported data type. > >> > org.geotools.image.ImageWorker.makeColorTransparent(ImageWorker.java:1848) > >> > org.geotools.gce.imagemosaic.RasterLayerResponse.createBlankResponse(RasterLayerResponse.java:1675) > >> > org.geotools.gce.imagemosaic.RasterLayerResponse.prepareResponse(RasterLayerResponse.java:1333) > >> > ... 118 more > >> > It seems it is not possible to set the InputTransparentColor for 32bit > >> > images which seems logical. But how can I get a similar setting for > >> > 32bit images? It was recommended to use JAI-Ext for proper support for nodata: > >> Wit the latest versions of GeoServer (2.8.x and on if my memory serves > >> me right) if you enable JAI-Ext there should be proper support for > >> nodata introduced, hence you simply have to make sure your data > >> reports nodata properly. Meanwhile I installed Geoserver 2.9.2 with JAI-Ext but the problem is still the same. Are there some settings I need to set for JAI-Extension? I started Geoserver with JAI-Ext enabled. Regards, Sabine Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users Another possibility is that your database contains an an old indexer schema that has changed since adjusting your indexer. Have you tried using datastore.properties to configure an embedded H2 database? It will be created automatically and so you can be sure that it is fresh. Kind regards, On 24/11/16 23:42, 小明 wrote: > Hi all: When i use imagemosaic it's throw "Caused by: > java.io.IOException: Schema 'default' does not exist".. Ben Caradoc-Davies Director Transient Software Limited New Zealand Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users I guess something is wrong with your indexer configuration. Are you using the new indexer.xml format? Kind regards, On 24/11/16 23:42, 小明 wrote: > Hi all: When i use imagemosaic it's throw "Caused by: > java.io.IOException: Schema 'default' does not exist".. Ben Caradoc-Davies Director Transient Software Limited New Zealand Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users >From the log, I see this: the ImageMosaicFormatFactory looks for the Kakadu jar and it doesn't find This is part of the ImageMosaicFormatFactory plugin discovery steps: it looks for available image readers at runtime and report a debug message if they are missing. Nov 15 08:44:40 the-geoserver server[23733]: 15 Nov 08:44:40 DEBUG [gce.imagemosaic] - Unable to load kakadu JPEG2000 reader spi Nov 15 08:44:40 the-geoserver server[23733]: java.lang.ClassNotFoundException: it.geosolutions.imageio.plugins.jp2k.JP2KKakaduImageReaderSpi So not an issue. After that, it should look for the available GDAL (jar) plugins. Since your log previously reported that GDAL native library is not available, I assume you have installed the GDAL extensions (gdal jars) on your geoserver.. Nov 15 08:44:37 the-geoserver server[23733]: Nov 15, 2016 8:44:37 AM it.geosolutions.imageio.gdalframework.GDALUtilities loadGDAL Nov 15 08:44:37 the-geoserver server[23733]: WARNING: Failed to load the GDAL native libs. This is not a problem unless you need to use the GDAL plugins: they won't be enabled. Nov 15 08:44:37 the-geoserver server[23733]: java.lang.UnsatisfiedLinkError: no gdaljni in java.library.path You have additional confirmation of missing GDAL native libs by the related geotools format factories: Nov 15 08:44:40 the-geoserver server[23733]: 15 Nov 08:44:40 DEBUG [gdal.erdasimg] - ErdasImgFormatFactory is not availaible. Nov 15 08:44:40 the-geoserver server[23733]: 15 Nov 08:44:40 DEBUG [gdal.envihdr] - EnviHdrFormatFactory is not availaible. Nov 15 08:44:40 the-geoserver server[23733]: 15 Nov 08:44:40 DEBUG [gdal.ehdr] - EsriHdrFormatFactory is not availaible. Nov 15 08:44:40 the-geoserver server[23733]: 15 Nov 08:44:40 DEBUG [gdal.dted] - DTEDFormatFactory is not availaible. Nov 15 08:44:40 the-geoserver server[23733]: 15 Nov 08:44:40 DEBUG [gdal.jp2mrisd] - JP2MrSIDFormatFactory is not availaible. Nov 15 08:44:40 the-geoserver server[23733]: 15 Nov 08:44:40 DEBUG [gdal.rpftoc] - RPFTOCFormatFactory is not availaible. Nov 15 08:44:40 the-geoserver server[23733]: 15 Nov 08:44:40 DEBUG [gdal.mrsid] - MrSIDFormatFactory is not availaible. Nov 15 08:44:40 the-geoserver server[23733]: 15 Nov 08:44:40 DEBUG [gdal.jp2k] - JP2KFormatFactory is not availaible. Nov 15 08:44:40 the-geoserver server[23733]: 15 Nov 08:44:40 DEBUG [gdal.jp2ecw] - JP2ECWFormatFactory is not availaible. Nov 15 08:44:40 the-geoserver server[23733]: 15 Nov 08:44:40 DEBUG [gdal.ecw] - ECWFormatFactory is not availaible. Nov 15 08:44:40 the-geoserver server[23733]: 15 Nov 08:44:40 DEBUG [gdal.nitf] - NITFFormatFactory is not availaible. (Note that GeoServer-GDAL extensions are based on GDAL 1.9.2. The yum gdal-java installation isn't guaranteed to work since it depends on how they have generated the java bindings) Back to the ImageMosaic checks... After the Kakadu check, the ImageMosaicFormatFactory initialization looks for GDAL plugins. At this point, no other classNotFoundException will occur since the jars are in the classpath. The isAvailable method of the GDAL utilities will return false (since no JNI has been found) so no GDAL plugins will be supported in ImageMosaic. Finally, the ImageMosaicFormatFactory should reach its own isAvailable method, looking for JAI classes on the classpath. At this point it should have been properly initialized. So we still need to figure out where that ServiceConfigurationError comes from. Do you also have "localhost" logs or any other logs being created by tomcat containing additional reports? Cheers, Daniele On Mon, Nov 14, 2016 at 11:22 PM, Adam Steer wrote: > Hi Daniele > the contents of 'journalctl -f -u tomcat’ from a tomcat restart to > clicking through to the admin interface ‘add store’ page are here: > https://adamsteer.github.io/geoserver_logs/2.10.0_centos7_ > java1.8_tomcat7_startup.txt > As far as I can see, this is supposed to be the Centos 7 way of getting > log files to spew to stdout - it seems to contain all the things > catalina.out would. > One interesting (and maybe relevant? maybe a separate issue completely) > snippet: > Nov 15 08:44:37 the-geoserver server[23733]: WARNING: Failed to load the > GDAL native libs. This is not a problem unless you need to use the GDAL > plugins: they won't be enabled. > Nov 15 08:44:37 the-geoserver server[23733]: java.lang.UnsatisfiedLinkError: > no gdaljni in java.library.path > …but, on the same machine: > gdalinfo --version > GDAL 1.11.4, released 2016/01/25 > …and libgdaljni is here (from yum install gdal-java): > /usr/lib/java/gdal/libgdaljni.so > $PATH includes this location, but I have not figured out how to append a > value to java.library.path yet. > Finally, I spun up a 2.9.2 geoserver on the same infrastructure (centOS7, > Java 1.8, Tomcat 7, identical plugin list) and have the option to add > imagemosaics there. For us this is specific to Geoserver 2.1.0.0 can you provide some more details on your issue? Which GeoServer version are you using? Did you configured any indexer/properties file to handle your data? do you have some more info on your NetCDF sample? (as an instance an "ncdump -h yourfile.nc") Please, let us know. Cheers, Daniele On Wed, Nov 23, 2016 at 2:43 PM, 小明 <[email protected]> wrote: > Hi all: >I create a image mosaic store which store the index in a database,. > when i publish layer it's throw a error like below: > * Caused by: java.lang.IllegalArgumentException: The specified > coverageName is unavailable at > org.geotools.gce.imagemosaic.ImageMosaicReader.checkUnspecifiedCoverage(ImageMosaicReader.java:1072) > org.geotools.gce.imagemosaic.ImageMosaicReader.getOriginalEnvelope(ImageMosaicReader.java:1181) > org.geoserver.catalog.SingleGridCoverage2DReader.getOriginalEnvelope(SingleGridCoverage2DReader.java:115) > org.geoserver.catalog.CatalogBuilder.buildCoverage(CatalogBuilder.java:893) > org.geoserver.catalog.CatalogBuilder.buildCoverage(CatalogBuilder.java:855) > org.geoserver.web.data.layer.NewLayerPage.buildLayerInfo(NewLayerPage.java:346)* > * Why???* > Geoserver-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. Ing. Daniele Romagnoli Senior Software Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or 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. Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users Dear Simone, as proposed I created a JIRA Issue for improvement on this topic: https://osgeo-org.atlassian.net/browse/GEOS-7856 Regards, Sabine > Gesendet: Mittwoch, 09. November 2016 um 16:19 Uhr > Von: "Simone Giannecchini" > An: "Sabine Ohlendorf" > Cc: "Simone Giannecchini" , "Geoserver > Mailinglist" > Betreff: Re: Re: [Geoserver-users] Imagemosaic: Input Transparent Color for > 32bit tifs > Ciao Sabine, > open a jira report and attach some small sample data or a link to > dropbox or something like that which we can use. > We might give you an ftp server privately if needed. > Regards, > Simone Giannecchini > GeoServer Professional Services from the experts! > Visit http://goo.gl/it488V for more information. > Ing. Simone Giannecchini > @simogeo > Founder/Director > GeoSolutions S.A.S. > Via di Montramito 3/A > 55054 Massarosa (LU) > Italy > phone: +39 0584 962313 > fax: +39 0584 1660272 > mob: +39 333 8128928 > http://www.geo-solutions.it > http://twitter.com/geosolutions_it > AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 > Le informazioni contenute in questo messaggio di posta elettronica e/o > nel/i file/s allegato/i sono da considerarsi strettamente riservate. > Il loro utilizzo è consentito esclusivamente al destinatario del > messaggio, per le finalità indicate nel messaggio stesso. Qualora > riceviate questo messaggio senza esserne il destinatario, Vi preghiamo > cortesemente di darcene notizia via e-mail e di procedere alla > distruzione del messaggio stesso, cancellandolo dal Vostro sistema. > Conservare il messaggio stesso, divulgarlo anche in parte, > distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità > diverse, costituisce comportamento contrario ai principi dettati dal > D.Lgs. 196/2003. > The information in this message and/or attachments, is intended solely > for the attention and use of the named addressee(s) and may be > confidential or proprietary in nature or covered by the provisions of > privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New > Data Protection Code).Any use not in accord with its purpose, any > disclosure, reproduction, copying, distribution, or either > dissemination, either whole or partial, is strictly forbidden except > previous formal approval of the named addressee(s). If you are not the > intended recipient, please contact immediately the sender by > telephone, fax or e-mail and delete the information in this message > that has been received in error. The sender does not give any warranty > or accept liability as the content, accuracy or 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. > On Wed, Nov 9, 2016 at 1:59 PM, Sabine Ohlendorf > wrote: > > Hi Simone, > > thank you for your message and sorry for late reply. > > I will try to update to the new version of geoserver (2.8.x) and test. > > How could I provide some sample data to you? > > Regards, > > Sabine > >> Gesendet: Dienstag, 25. Oktober 2016 um 09:13 Uhr > >> Von: "Simone Giannecchini" > >> An: "Sabine Ohlendorf" > >> Cc: "Geoserver Mailinglist" > >> Betreff: Re: [Geoserver-users] Imagemosaic: Input Transparent Color for > >> 32bit tifs > >> Ciao Sabine, > >> as you noticed the XXXTransparentColor settings do not apply to "real" > >> data (float, double, 16bits etc...). > >> Wit the latest versions of GeoServer (2.8.x and on if my memory serves > >> me right) if you enable JAI-Ext there should be proper support for > >> nodata introduced, hence you simply have to make sure your data > >> reports nodata properly. > >> Maybe some sample data could help identifying this issue. > >> Regards, > >> Simone Giannecchini > >> GeoServer Professional Services from the experts! > >> Visit http://goo.gl/it488V for more information. > >> Ing. Simone Giannecchini > >> @simogeo > >> Founder/Director > >> GeoSolutions S.A.S. > >> Via di Montramito 3/A > >> 55054 Massarosa (LU) > >> Italy > >> phone: +39 0584 962313 > >> fax: +39 0584 1660272 > >> mob: +39 333 8128928 > >> http://www.geo-solutions.it

Re: [Geoserver-users] imagemosaic extension for geoserver 2.10?

2016-11-14 Thread Adam Steer Hi Daniele the contents of 'journalctl -f -u tomcat’ from a tomcat restart to clicking through to the admin interface ‘add store’ page are here: https://adamsteer.github.io/geoserver_logs/2.10.0_centos7_java1.8_tomcat7_startup.txt As far as I can see, this is supposed to be the Centos 7 way of getting log files to spew to stdout - it seems to contain all the things catalina.out would. One interesting (and maybe relevant? maybe a separate issue completely) snippet: Nov 15 08:44:37 the-geoserver server[23733]: WARNING: Failed to load the GDAL native libs. This is not a problem unless you need to use the GDAL plugins: they won't be enabled. Nov 15 08:44:37 the-geoserver server[23733]: java.lang.UnsatisfiedLinkError: no gdaljni in java.library.path …but, on the same machine: gdalinfo --version GDAL 1.11.4, released 2016/01/25 …and libgdaljni is here (from yum install gdal-java): /usr/lib/java/gdal/libgdaljni.so $PATH includes this location, but I have not figured out how to append a value to java.library.path yet. Finally, I spun up a 2.9.2 geoserver on the same infrastructure (centOS7, Java 1.8, Tomcat 7, identical plugin list) and have the option to add imagemosaics there. For us this is specific to Geoserver 2.1.0.0 Hope that’s more useful! Cheers > On 15 Nov 2016, at 2:45 AM, Daniele Romagnoli > wrote: > Hi Adam, > Can you provide the full logs as text attachments? > The part you posted is simply a debug message (very low level) reporting that > the imageMosaic won't be able to handle mosaics of JP2K images being unable > to find the proper JP2K plugin, which shouldn't be a problem in your case and > which shouldn't prevent the ImageMosaic plugin to be enabled. > Therefore I think that we need to scan the logs more deeply. (You may also > want to provide the localhost.log and catalina.log logs if they contain > additional exceptions) > Please, let us know. > Cheers, > Daniele > On Mon, Nov 14, 2016 at 6:55 AM, Adam Steer wrote: > Hi Daniele, apologies for the delay! > Some more info - as well as Java 1.8 and Centos 7, I’m running on tomcat 7. > The (hopefully) relevant part of a more verbose log is shown below. > I wonder if i need to go install the imageo-ext stuff > (http://geoserver.geo-solutions.it/edu/en/install_run/imageio_ext_install.html)? > ...which seems odd if the imagmosaic is ‘in the box’ with geoserver. Hmm. > Maybe just a joy of CentOS. > Thanks again > 2016-11-14 16:32:20,568 DEBUG [gce.imagemosaic] - Unable to load kakadu > JPEG2000 reader spi > java.lang.ClassNotFoundException: > it.geosolutions.imageio.plugins.jp2k.JP2KKakaduImageReaderSpi > org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1720) > org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1571) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:264) > org.geotools.gce.imagemosaic.ImageMosaicFormatFactory.hasJP2Kakadu(ImageMosaicFormatFactory.java:190) > org.geotools.gce.imagemosaic.ImageMosaicFormatFactory.(ImageMosaicFormatFactory.java:68) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at java.lang.Class.newInstance(Class.java:442) > java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:380) > at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404) > at java.util.ServiceLoader$1.next(ServiceLoader.java:480) > org.geotools.factory.FactoryRegistry.register(FactoryRegistry.java:826) > org.geotools.factory.FactoryRegistry.scanForPlugins(FactoryRegistry.java:772) > org.geotools.factory.FactoryRegistry.scanForPlugins(FactoryRegistry.java:750) > org.geotools.coverage.grid.io.GridFormatFinder.scanForPlugins(GridFormatFinder.java:122) > org.geotools.coverage.grid.io.GridFormatFinder.getAvailableFormats(GridFormatFinder.java:85) > org.geotools.coverage.grid.io.GridFormatFinder.getFormatArray(GridFormatFinder.java:144) > org.geoserver.data.util.CoverageStoreUtils.(CoverageStoreUtils.java:45) > org.geoserver.catalog.ResourcePool.getGridCoverageFormat(ResourcePool.java:1684) > org.geoserver.catalog.impl.CoverageStoreInfoImpl.getFormat(CoverageStoreInfoImpl.java:49) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > sun.reflect.DelegatingMet

Re: [Geoserver-users] imagemosaic extension for geoserver 2.10?

2016-11-14 Thread Daniele Romagnoli Hi Adam, Can you provide the full logs as text attachments? The part you posted is simply a debug message (very low level) reporting that the imageMosaic won't be able to handle mosaics of JP2K images being unable to find the proper JP2K plugin, which shouldn't be a problem in your case and which shouldn't prevent the ImageMosaic plugin to be enabled. Therefore I think that we need to scan the logs more deeply. (You may also want to provide the localhost.log and catalina.log logs if they contain additional exceptions) Please, let us know. Cheers, Daniele On Mon, Nov 14, 2016 at 6:55 AM, Adam Steer wrote: > Hi Daniele, apologies for the delay! > Some more info - as well as Java 1.8 and Centos 7, I’m running on tomcat 7. > The (hopefully) relevant part of a more verbose log is shown below. > I wonder if i need to go install the imageo-ext stuff ( > http://geoserver.geo-solutions.it/edu/en/install_ > run/imageio_ext_install.html)? ...which seems odd if the imagmosaic is > ‘in the box’ with geoserver. Hmm. Maybe just a joy of CentOS. > Thanks again > 2016-11-14 16:32:20,568 DEBUG [gce.imagemosaic] - Unable to load kakadu > JPEG2000 reader spi > java.lang.ClassNotFoundException: it.geosolutions.imageio.plugins.jp2k. > JP2KKakaduImageReaderSpi > at org.apache.catalina.loader.WebappClassLoader.loadClass( > WebappClassLoader.java:1720) > at org.apache.catalina.loader.WebappClassLoader.loadClass( > WebappClassLoader.java:1571) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:264) > at org.geotools.gce.imagemosaic.ImageMosaicFormatFactory. > hasJP2Kakadu(ImageMosaicFormatFactory.java:190) > at org.geotools.gce.imagemosaic.ImageMosaicFormatFactory.( > ImageMosaicFormatFactory.java:68) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance( > NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance( > DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at java.lang.Class.newInstance(Class.java:442) > at java.util.ServiceLoader$LazyIterator.nextService( > ServiceLoader.java:380) > at java.util.ServiceLoader$LazyIterator.next( > ServiceLoader.java:404) > at java.util.ServiceLoader$1.next(ServiceLoader.java:480) > at org.geotools.factory.FactoryRegistry.register( > FactoryRegistry.java:826) > at org.geotools.factory.FactoryRegistry.scanForPlugins( > FactoryRegistry.java:772) > at org.geotools.factory.FactoryRegistry.scanForPlugins( > FactoryRegistry.java:750) > at org.geotools.coverage.grid.io.GridFormatFinder.scanForPlugins( > GridFormatFinder.java:122) > at org.geotools.coverage.grid.io.GridFormatFinder. > getAvailableFormats(GridFormatFinder.java:85) > at org.geotools.coverage.grid.io.GridFormatFinder.getFormatArray( > GridFormatFinder.java:144) > at org.geoserver.data.util.CoverageStoreUtils.( > CoverageStoreUtils.java:45) > at org.geoserver.catalog.ResourcePool.getGridCoverageFormat( > ResourcePool.java:1684) > at org.geoserver.catalog.impl.CoverageStoreInfoImpl.getFormat( > CoverageStoreInfoImpl.java:49) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke( > NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke( > DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.geoserver.catalog.impl.ModificationProxy.invoke( > ModificationProxy.java:147) > at com.sun.proxy.$Proxy13.getFormat(Unknown Source) > at org.geoserver.catalog.ResourcePool.getGridCoverageReader( > ResourcePool.java:1439) > at org.geoserver.catalog.ResourcePool.getGridCoverageReader( > ResourcePool.java:1394) > at org.geoserver.catalog.ResourcePool.getGridCoverageReader( > ResourcePool.java:1389) > at org.geoserver.wms.WMSValidator.validate(WMSValidator.java:49) > at org.geoserver.catalog.impl.CatalogImpl$ > CatalogValidatorVisitor.visit(CatalogImpl.java:1724) > at org.geoserver.catalog.impl.LayerInfoImpl.accept( > LayerInfoImpl.java:237) > at org.geoserver.catalog.impl.CatalogImpl.postValidate( > CatalogImpl.java:1675) > at org.geoserver.catalog.impl.CatalogImpl.validate( > CatalogImpl.java:690) > at org.geoserver.catalog.impl.CatalogImpl.add(CatalogImpl. > java:622) > at org.geoserver.config.GeoServerLoader.readCatalog( > GeoServerLoader.java:452) > at org.geoserver.config.GeoServerLoader.readCatalog( > GeoServerLoader.java:238) > at org.geoserver.config.DefaultGeoServerLoader.loadCatalog( > DefaultGeoServerLoader.java:36)

Re: [Geoserver-users] imagemosaic extension for geoserver 2.10?

2016-11-13 Thread Adam Steer Hi Daniele, apologies for the delay! Some more info - as well as Java 1.8 and Centos 7, I’m running on tomcat 7. The (hopefully) relevant part of a more verbose log is shown below. I wonder if i need to go install the imageo-ext stuff (http://geoserver.geo-solutions.it/edu/en/install_run/imageio_ext_install.html)? ...which seems odd if the imagmosaic is ‘in the box’ with geoserver. Hmm. Maybe just a joy of CentOS. Thanks again 2016-11-14 16:32:20,568 DEBUG [gce.imagemosaic] - Unable to load kakadu JPEG2000 reader spi java.lang.ClassNotFoundException: it.geosolutions.imageio.plugins.jp2k.JP2KKakaduImageReaderSpi org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1720) org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1571) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:264) org.geotools.gce.imagemosaic.ImageMosaicFormatFactory.hasJP2Kakadu(ImageMosaicFormatFactory.java:190) org.geotools.gce.imagemosaic.ImageMosaicFormatFactory.(ImageMosaicFormatFactory.java:68) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at java.lang.Class.newInstance(Class.java:442) java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:380) at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404) at java.util.ServiceLoader$1.next(ServiceLoader.java:480) org.geotools.factory.FactoryRegistry.register(FactoryRegistry.java:826) org.geotools.factory.FactoryRegistry.scanForPlugins(FactoryRegistry.java:772) org.geotools.factory.FactoryRegistry.scanForPlugins(FactoryRegistry.java:750) org.geotools.coverage.grid.io.GridFormatFinder.scanForPlugins(GridFormatFinder.java:122) org.geotools.coverage.grid.io.GridFormatFinder.getAvailableFormats(GridFormatFinder.java:85) org.geotools.coverage.grid.io.GridFormatFinder.getFormatArray(GridFormatFinder.java:144) org.geoserver.data.util.CoverageStoreUtils.(CoverageStoreUtils.java:45) org.geoserver.catalog.ResourcePool.getGridCoverageFormat(ResourcePool.java:1684) org.geoserver.catalog.impl.CoverageStoreInfoImpl.getFormat(CoverageStoreInfoImpl.java:49) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) org.geoserver.catalog.impl.ModificationProxy.invoke(ModificationProxy.java:147) at com.sun.proxy.$Proxy13.getFormat(Unknown Source) org.geoserver.catalog.ResourcePool.getGridCoverageReader(ResourcePool.java:1439) org.geoserver.catalog.ResourcePool.getGridCoverageReader(ResourcePool.java:1394) org.geoserver.catalog.ResourcePool.getGridCoverageReader(ResourcePool.java:1389) at org.geoserver.wms.WMSValidator.validate(WMSValidator.java:49) org.geoserver.catalog.impl.CatalogImpl$CatalogValidatorVisitor.visit(CatalogImpl.java:1724) org.geoserver.catalog.impl.LayerInfoImpl.accept(LayerInfoImpl.java:237) org.geoserver.catalog.impl.CatalogImpl.postValidate(CatalogImpl.java:1675) at org.geoserver.catalog.impl.CatalogImpl.validate(CatalogImpl.java:690) at org.geoserver.catalog.impl.CatalogImpl.add(CatalogImpl.java:622) org.geoserver.config.GeoServerLoader.readCatalog(GeoServerLoader.java:452) org.geoserver.config.GeoServerLoader.readCatalog(GeoServerLoader.java:238) org.geoserver.config.DefaultGeoServerLoader.loadCatalog(DefaultGeoServerLoader.java:36) org.geoserver.config.GeoServerLoader.postProcessBeforeInitialization(GeoServerLoader.java:109) org.geoserver.config.GeoServerLoaderProxy.postProcessBeforeInitialization(GeoServerLoaderProxy.java:59) org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:408) org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1570) org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:545) org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowi

Re: [Geoserver-users] imagemosaic extension for geoserver 2.10?

2016-11-10 Thread Daniele Romagnoli Resending my previous message due to a bounce caused by message too long. Removing quoted text of previous discussion to make it shorter. Hi Adam, do you have any chance to raise the logging level (making it more verbose), restart GeoServer and provide the the full logs? It seems the ImageMosaicFormatFactory cannot be instantiated. This explains why you don't see the ImageMosaic plugin in the Coverage Stores list. The ImageMosaicFormatFactory does an availability check by checking if a couple of JAI and JAI-ImageIO classes are available. However the ArcGridFormatFactory and GeoTIFFFormatFactorySpi do the same check and I see them available on your installation so I would exclude a JAI issue. The log reports there is something going wrong with the SPI initialization: ServiceConfigurationError: https://docs.oracle.com/javase/7/docs/api/java/util/ ServiceConfigurationError.html (JAI util has a very similar class) Maybe a debug logging level can provide additional details. Please, let us know. Cheers, Daniele > On Thu, Nov 10, 2016 at 12:56 AM, Adam Steer > wrote: >> Hi all >> System is: >> Centos 7 >> $ java -version >> openjdk version "1.8.0_111" >> OpenJDK Runtime Environment (build 1.8.0_111-b15) >> OpenJDK 64-Bit Server VM (build 25.111-b15, mixed mode) >> …and yes, Daniele got it - deployed using the 2.10 war file in tomcat. >> Here’s some hopefully relevant log info: >> 2016-11-10 10:43:15,535 WARN [geotools.factory] - Can't load a service >> for category "GridFormatFactorySpi". Cause is "ServiceConfigurationError: >> org.geotools.coverage.grid.io.GridFormatFactorySpi: >> Provider org.geotools.gce.imagemosaic.ImageMosaicFormatFactory could not >> be instantiated". >> 2016-11-10 10:43:53,558 WARN [support.DisposableBeanAdapter] - >> Invocation of destroy method failed on bean with name 'geoServerLoader': >> org.springframework.beans.factory.BeanCreationNotAllowedException: Error >> creating bean with name 'geoWebCacheExtensions': Singleton bean creation >> not allowed while the singletons of this factory are in destruction (Do not >> request a bean from a BeanFactory in a destroy method implementation!) >> 2016-11-10 10:44:05,423 WARN [geotools.factory] - Can't load a service >> for category "GridFormatFactorySpi". Cause is "ServiceConfigurationError: >> org.geotools.coverage.grid.io.GridFormatFactorySpi: >> Provider org.geotools.gce.imagemosaic.ImageMosaicFormatFactory could not >> be instantiated". >> 2016-11-10 10:44:08,749 WARN [turbojpeg.TurboJPEGMapResponse] - The >> turbo jpeg encoder is not available, check the native libs installation >> 2016-11-10 10:44:08,784 WARN [netcdf.layer] - No CF-Standard File found >> …the CF file thing I can fix. Turbo jpeg is odd - it’s installed by yum, >> I’ll see if a hand install works? >> Screenshot attached. >> Thanks! GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. Ing. Daniele Romagnoli Senior Software Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts n

Re: [Geoserver-users] Imagemosaic: Input Transparent Color for 32bit tifs

2016-11-09 Thread Simone Giannecchini Ciao Sabine, open a jira report and attach some small sample data or a link to dropbox or something like that which we can use. We might give you an ftp server privately if needed. Regards, Simone Giannecchini GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. Ing. Simone Giannecchini @simogeo Founder/Director GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 333 8128928 http://www.geo-solutions.it http://twitter.com/geosolutions_it AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or 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. On Wed, Nov 9, 2016 at 1:59 PM, Sabine Ohlendorf wrote: > Hi Simone, > thank you for your message and sorry for late reply. > I will try to update to the new version of geoserver (2.8.x) and test. > How could I provide some sample data to you? > Regards, > Sabine >> Gesendet: Dienstag, 25. Oktober 2016 um 09:13 Uhr >> Von: "Simone Giannecchini" >> An: "Sabine Ohlendorf" >> Cc: "Geoserver Mailinglist" >> Betreff: Re: [Geoserver-users] Imagemosaic: Input Transparent Color for >> 32bit tifs >> Ciao Sabine, >> as you noticed the XXXTransparentColor settings do not apply to "real" >> data (float, double, 16bits etc...). >> Wit the latest versions of GeoServer (2.8.x and on if my memory serves >> me right) if you enable JAI-Ext there should be proper support for >> nodata introduced, hence you simply have to make sure your data >> reports nodata properly. >> Maybe some sample data could help identifying this issue. >> Regards, >> Simone Giannecchini >> GeoServer Professional Services from the experts! >> Visit http://goo.gl/it488V for more information. >> Ing. Simone Giannecchini >> @simogeo >> Founder/Director >> GeoSolutions S.A.S. >> Via di Montramito 3/A >> 55054 Massarosa (LU) >> Italy >> phone: +39 0584 962313 >> fax: +39 0584 1660272 >> mob: +39 333 8128928 >> http://www.geo-solutions.it >> http://twitter.com/geosolutions_it >> AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 >> Le informazioni contenute in questo messaggio di posta elettronica e/o >> nel/i file/s allegato/i sono da considerarsi strettamente riservate. >> Il loro utilizzo è consentito esclusivamente al destinatario del >> messaggio, per le finalità indicate nel messaggio stesso. Qualora >> riceviate questo messaggio senza esserne il destinatario, Vi preghiamo >> cortesemente di darcene notizia via e-mail e di procedere alla >> distruzione del messaggio stesso, cancellandolo dal Vostro sistema. >> Conservare il messaggio stesso, divulgarlo anche in parte, >> distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità >> diverse, costituisce comportamento contrario ai principi dettati dal >> D.Lgs. 196/2003. >> The information in this message and/o

Re: [Geoserver-users] Imagemosaic: Input Transparent Color for 32bit tifs

2016-11-09 Thread Sabine Ohlendorf Hi Simone, thank you for your message and sorry for late reply. I will try to update to the new version of geoserver (2.8.x) and test. How could I provide some sample data to you? Regards, Sabine > Gesendet: Dienstag, 25. Oktober 2016 um 09:13 Uhr > Von: "Simone Giannecchini" > An: "Sabine Ohlendorf" > Cc: "Geoserver Mailinglist" > Betreff: Re: [Geoserver-users] Imagemosaic: Input Transparent Color for 32bit > Ciao Sabine, > as you noticed the XXXTransparentColor settings do not apply to "real" > data (float, double, 16bits etc...). > Wit the latest versions of GeoServer (2.8.x and on if my memory serves > me right) if you enable JAI-Ext there should be proper support for > nodata introduced, hence you simply have to make sure your data > reports nodata properly. > Maybe some sample data could help identifying this issue. > Regards, > Simone Giannecchini > GeoServer Professional Services from the experts! > Visit http://goo.gl/it488V for more information. > Ing. Simone Giannecchini > @simogeo > Founder/Director > GeoSolutions S.A.S. > Via di Montramito 3/A > 55054 Massarosa (LU) > Italy > phone: +39 0584 962313 > fax: +39 0584 1660272 > mob: +39 333 8128928 > http://www.geo-solutions.it > http://twitter.com/geosolutions_it > AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 > Le informazioni contenute in questo messaggio di posta elettronica e/o > nel/i file/s allegato/i sono da considerarsi strettamente riservate. > Il loro utilizzo è consentito esclusivamente al destinatario del > messaggio, per le finalità indicate nel messaggio stesso. Qualora > riceviate questo messaggio senza esserne il destinatario, Vi preghiamo > cortesemente di darcene notizia via e-mail e di procedere alla > distruzione del messaggio stesso, cancellandolo dal Vostro sistema. > Conservare il messaggio stesso, divulgarlo anche in parte, > distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità > diverse, costituisce comportamento contrario ai principi dettati dal > D.Lgs. 196/2003. > The information in this message and/or attachments, is intended solely > for the attention and use of the named addressee(s) and may be > confidential or proprietary in nature or covered by the provisions of > privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New > Data Protection Code).Any use not in accord with its purpose, any > disclosure, reproduction, copying, distribution, or either > dissemination, either whole or partial, is strictly forbidden except > previous formal approval of the named addressee(s). If you are not the > intended recipient, please contact immediately the sender by > telephone, fax or e-mail and delete the information in this message > that has been received in error. The sender does not give any warranty > or accept liability as the content, accuracy or 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. > On Mon, Oct 24, 2016 at 6:14 PM, Sabine Ohlendorf > wrote: > > Dear List, > > I am using Geoserver 2.7.5. I want to create a layer out of several > > geotiffs so I created an imagemosaic. The geotiffs are 32bit tifs an I want > > to colorize them using Geoserver Styles. The single tifs overlap at the > > edges and partly have no data values there which appear in the mosaic. To > > avoid that I wanted to set the "Input Transparent Color". But when setting > > a value I get an Error: > > org.geotools.data.DataSourceException: Unable to create this mosaic > > org.geotools.gce.imagemosaic.RasterLayerResponse.prepareResponse(RasterLayerResponse.java:1336) > > org.geotools.gce.imagemosaic.RasterLayerResponse.processRequest(RasterLayerResponse.java:1226) > > org.geotools.gce.imagemosaic.RasterLayerResponse.createResponse(RasterLayerResponse.java:1192) > > org.geotools.gce.imagemosaic.RasterManager.read(RasterManager.java:1153) > > org.geotools.gce.imagemosaic.ImageMosaicReader.read(ImageMosaicReader.java:874) > > org.geotools.gce.imagemosaic.ImageMosaicReader.read(ImageMosaicReader.java:853) > > org.geoserver.catalog.SingleGridCoverage2DReader.read(SingleGridCoverage2DReader.java:147) > > org.geoserver.catalog.CoverageDimensionCustomizerReader.read(CoverageDimensionCustomizerReader.java:227)

Re: [Geoserver-users] imagemosaic extension for geoserver 2.10?

2016-11-09 Thread Ian Turton Looks good in the 2.10.0 I installed yesterday (Ubuntu 14.02, Java 1.8.0_111) On 9 November 2016 at 09:10, Daniele Romagnoli < [email protected]> wrote: > Hi Adam, > On Wed, Nov 9, 2016 at 3:09 AM, Adam Steer wrote: >> Hi all - new user question alert! >> What is the geoserver 2.10 way of creating imagemosaics? >> The documentation here: http://docs.geoserver.org/late >> st/en/user/data/raster/imagemosaic/configuration.html >> …and here: http://docs.geoserver.org/latest/en/user/data/raster/imagemo >> saic/tutorial.html >> …mentions an extension, but there is no imagemosaic extension listed here >> to download: http://geoserver.org/release/stable/ > The ImageMosaic is a standard plugin, indeed. It seems the main title of > that page has been changed in the latest 2 months. The previous > documentation was indeed referring to that as a plugin. > http://docs.geoserver.org/2.9.x/en/user/data/raster/ > imagemosaic/tutorial.html >> I have these Jars in my WEB-INF/lib/: >> -rw-r--r--. 1 tomcat tomcat 428213 Oct 27 00:27 gt-imagemosaic-16.0.jar >> -rw-r--r--. 1 tomcat tomcat 130066 Oct 28 09:48 >> gt-imagemosaic-jdbc-16.0.jar >> -rw-r--r--. 1 tomcat tomcat 31234 Jun 24 14:08 jt-mosaic-1.0.11.jar >> …which seem to suggest that some mechanics for imagemosaic creation is >> there. > Yes. (I suppose you have deployed the geoserver 2.10.0 war in tomcat, > right?) >> …but there is no option to add an imagemosaic store on the ‘new data >> source’ web GUI page (as listed in the tutorial linked above), > That's quite strange. Can you share a screenshot with the available > formats reported on the "new data source" page? > Did you have any exceptions/warning in the logs? >> and I’m hesitant to go follow programmatic mosaic creation tutorials >> without being able to click through a simple example first. > Please, let us know. > Cheers, > Daniele >> Scratching my head a little - If anyone can shed light on the process I’d >> really appreciate it. >> Thanks >> Developer Access Program for Intel Xeon Phi Processors >> Access to Intel Xeon Phi processor-based developer platforms. >> With one year of Intel Parallel Studio XE. >> Training and support from Colfax. >> Order your platform today. http://sdm.link/xeonphi >> Geoserver-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/geoserver-users > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. > Ing. Daniele Romagnoli > Senior Software Engineer > GeoSolutions S.A.S. > Via di Montramito 3/A > 55054 Massarosa (LU) > Italy > phone: +39 0584 962313 > fax: +39 0584 1660272 > http://www.geo-solutions.it > http://twitter.com/geosolutions_it > *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* > Le informazioni contenute in questo messaggio di posta elettronica e/o > nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il > loro utilizzo è consentito esclusivamente al destinatario del messaggio, > per le finalità indicate nel messaggio stesso. Qualora riceviate questo > messaggio senza esserne il destinatario, Vi preghiamo cortesemente di > darcene notizia via e-mail e di procedere alla distruzione del messaggio > stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, > divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od > utilizzarlo per finalità diverse, costituisce comportamento contrario ai > principi dettati dal D.Lgs. 196/2003. > The information in this message and/or attachments, is intended solely for > the attention and use of the named addressee(s) and may be confidential or > proprietary in nature or covered by the provisions of privacy act > (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection > Code).Any use not in accord with its purpose, any disclosure, reproduction, > copying, distribution, or either dissemination, either whole or partial, is > strictly forbidden except previous formal approval of the named > addressee(s). If you are not the intended recipient, please contact > immediately the sender by telephone, fax or e-mail and delete the > information in this message that has been received in error. The sender > does not give any warranty or accept liability as the content, accuracy or > 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. > Developer Access Program for Intel Xeon Phi Processors > Access to I

Re: [Geoserver-users] imagemosaic extension for geoserver 2.10?

2016-11-09 Thread Daniele Romagnoli Hi Adam, On Wed, Nov 9, 2016 at 3:09 AM, Adam Steer wrote: > Hi all - new user question alert! > What is the geoserver 2.10 way of creating imagemosaics? > The documentation here: http://docs.geoserver.org/ > latest/en/user/data/raster/imagemosaic/configuration.html > …and here: http://docs.geoserver.org/latest/en/user/data/raster/ > imagemosaic/tutorial.html > …mentions an extension, but there is no imagemosaic extension listed here > to download: http://geoserver.org/release/stable/ The ImageMosaic is a standard plugin, indeed. It seems the main title of that page has been changed in the latest 2 months. The previous documentation was indeed referring to that as a plugin. http://docs.geoserver.org/2.9.x/en/user/data/raster/imagemosaic/tutorial.html > I have these Jars in my WEB-INF/lib/: > -rw-r--r--. 1 tomcat tomcat 428213 Oct 27 00:27 gt-imagemosaic-16.0.jar > -rw-r--r--. 1 tomcat tomcat 130066 Oct 28 09:48 > gt-imagemosaic-jdbc-16.0.jar > -rw-r--r--. 1 tomcat tomcat 31234 Jun 24 14:08 jt-mosaic-1.0.11.jar > …which seem to suggest that some mechanics for imagemosaic creation is > there. Yes. (I suppose you have deployed the geoserver 2.10.0 war in tomcat, right?) > …but there is no option to add an imagemosaic store on the ‘new data > source’ web GUI page (as listed in the tutorial linked above), That's quite strange. Can you share a screenshot with the available formats reported on the "new data source" page? Did you have any exceptions/warning in the logs? > and I’m hesitant to go follow programmatic mosaic creation tutorials > without being able to click through a simple example first. Please, let us know. Cheers, Daniele > Scratching my head a little - If anyone can shed light on the process I’d > really appreciate it. > Thanks > Developer Access Program for Intel Xeon Phi Processors > Access to Intel Xeon Phi processor-based developer platforms. > With one year of Intel Parallel Studio XE. > Training and support from Colfax. > Order your platform today. http://sdm.link/xeonphi > Geoserver-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. Ing. Daniele Romagnoli Senior Software Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or 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. Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi___ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users Ciao Sabine, as you noticed the XXXTransparentColor settings do not apply to "real" data (float, double, 16bits etc...). Wit the latest versions of GeoServer (2.8.x and on if my memory serves me right) if you enable JAI-Ext there should be proper support for nodata introduced, hence you simply have to make sure your data reports nodata properly. Maybe some sample data could help identifying this issue. Regards, Simone Giannecchini GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. Ing. Simone Giannecchini @simogeo Founder/Director GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 333 8128928 http://www.geo-solutions.it http://twitter.com/geosolutions_it AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or 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. On Mon, Oct 24, 2016 at 6:14 PM, Sabine Ohlendorf wrote: > Dear List, > I am using Geoserver 2.7.5. I want to create a layer out of several geotiffs > so I created an imagemosaic. The geotiffs are 32bit tifs an I want to > colorize them using Geoserver Styles. The single tifs overlap at the edges > and partly have no data values there which appear in the mosaic. To avoid > that I wanted to set the "Input Transparent Color". But when setting a value > I get an Error: > org.geotools.data.DataSourceException: Unable to create this mosaic > org.geotools.gce.imagemosaic.RasterLayerResponse.prepareResponse(RasterLayerResponse.java:1336) > org.geotools.gce.imagemosaic.RasterLayerResponse.processRequest(RasterLayerResponse.java:1226) > org.geotools.gce.imagemosaic.RasterLayerResponse.createResponse(RasterLayerResponse.java:1192) > org.geotools.gce.imagemosaic.RasterManager.read(RasterManager.java:1153) > org.geotools.gce.imagemosaic.ImageMosaicReader.read(ImageMosaicReader.java:874) > org.geotools.gce.imagemosaic.ImageMosaicReader.read(ImageMosaicReader.java:853) > org.geoserver.catalog.SingleGridCoverage2DReader.read(SingleGridCoverage2DReader.java:147) > org.geoserver.catalog.CoverageDimensionCustomizerReader.read(CoverageDimensionCustomizerReader.java:227) > org.geoserver.catalog.CoverageDimensionCustomizerReader.read(CoverageDimensionCustomizerReader.java:217) > org.geoserver.wms.featureinfo.RasterLayerIdentifier.identify(RasterLayerIdentifier.java:170) > at org.geoserver.wms.GetFeatureInfo.execute(GetFeatureInfo.java:78) > at org.geoserver.wms.GetFeatureInfo.run(GetFeatureInfo.java:44) > ... 107 more > Caused by: java.lang.IllegalStateException: Unsupported data type. > org.geotools.image.ImageWorker.makeColorTransparent(ImageWorker.java:1848) > org.geotools.gce.imagemosaic.RasterLayerResponse.createBlankResponse(RasterLayerResponse.java:1675) > org.geotools.gce.imagemosaic.RasterLayerResponse.prepareResponse(RasterLayerResponse.java:1333) > ... 118 more > It seems it is not possible to set the InputTransparentColor for 32bit images > which seems logical. But how can I get a similar setting for 32bit images? > Regards, > Sabine Do you have some data (tiff or else) wich is working with the plugin Image Mosaic ? maybe it's my data... and just for know, when you use the plugin, GDAL raster must be installed ? View this message in context: http://osgeo-org.1560.x6.nabble.com/ImageMosaic-don-t-load-tp5279099p5279550.html Sent from the GeoServer - User mailing list archive at Nabble.com. Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users I've attached your sample data and stack trace to https://osgeo-org.atlassian.net/browse/GEOS-7340 , and updated the title. Don't know when it will be fixed, ROIGeometry needs first to be moved from JAITools (dead projecto) to jai-ext, and references to it updated in GeoTools and GeoServer... it's going to take time (too large of a job to do in spare time). Cheers Andrea 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 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or 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. Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users so, the projection of my raster is EPSG 4326 and i don't use any reprojection on my data and is i set "forced declared" or the others options is the same. My footprints is set on "None" and the others option are on default. What dou you mean by the request that makes it happen ? e004.rar here is my sample data, it's DTED2. Hope there will be an issue... View this message in context: http://osgeo-org.1560.x6.nabble.com/ImageMosaic-don-t-load-tp5279099p5279496.html Sent from the GeoServer - User mailing list archive at Nabble.com. Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users thanks, it seems the issue is not platform specific, but I cannot easily reproduce it using my local sample data. It seems it takes a mosaic of DEM or other single band surface, _maybe_ on the fly reprojection (what's your projection policy? does it change anything if you set it to "force declared"?), using the default "raster" style, and something else that makes the ROI appear in the computation chain... do you have footprint enabled? Or maybe you are reprojecting in the request? As I suggested on the parallel discussion in stackexchange, can you attach in the ticket tracker a small data sample and the request that makes it happen? Cheers Andrea On Wed, Aug 3, 2016 at 10:46 PM, ra2f wrote: > Geographic Information Systems Stack Exchange > sign up log in > Questions Tags Users Badges Unanswered Ask > Read this post in our app! > up vote > down vote > favorite > Image Mosaic in GeoServer? > geoserver > I use to geoserver in 2.9 under Windows Server on 2008 64bits. The plugin > GDAL raster is correctly installed, but by wanting to make a mosaic and > loaded her in a GIS, nothing displays. If I make one raster it is OK (tiff > or dted), but a mosaic not.. even for 2 rasters. > In the log I have the following error: Error rendering coverage one the > path ogr.geotools.coverage.processing. CoverageProcessingException: > java.lang. UnsupportedOperationException: Not implemented > Ideas? > I have installed JAI lib and JAI image I/O but it didn't change anything.. > Log geoserver : > 2016-08-03 10:49:34,770 INFO [geoserver.wms] - > Request: getServiceInfo > 2016-08-03 10:49:34,801 INFO [geoserver.wms] - > Request: getCapabilities > Namespace = raster > UpdateSequence = null > Request = GetCapabilities > RawKvp = {REQUEST=GetCapabilities, SERVICE=WMS} > Get = false > BaseUrl = http://localhost:8080/geoserver/ > RequestCharset = null > Version = 1.3.0 > 2016-08-03 10:49:37,438 INFO [geoserver.wms] - > Request: getServiceInfo > 2016-08-03 10:49:37,453 INFO [geoserver.wms] - > Request: getCapabilities > Namespace = raster > UpdateSequence = null > Request = GetCapabilities > RawKvp = {REQUEST=GetCapabilities, SERVICE=WMS} > Get = false > BaseUrl = http://localhost:8080/geoserver/ > RequestCharset = null > Version = 1.3.0 > 2016-08-03 10:49:37,699 INFO [geoserver.wms] - > Request: getServiceInfo > 2016-08-03 10:49:41,179 ERROR [geoserver.ows] - > org.geoserver.platform.ServiceException: Error rendering coverage on the > fast path > org.geoserver.wms.map.RenderedImageMapOutputFormat.produceMap(RenderedImageMapOutputFormat.java:346) > org.geoserver.wms.map.RenderedImageMapOutputFormat.produceMap(RenderedImageMapOutputFormat.java:261) > org.geoserver.wms.map.RenderedImageMapOutputFormat.produceMap(RenderedImageMapOutputFormat.java:131) > at org.geoserver.wms.GetMap.executeInternal(GetMap.java:505) > at org.geoserver.wms.GetMap.run(GetMap.java:249) > at org.geoserver.wms.GetMap.run(GetMap.java:119) > org.geoserver.wms.DefaultWebMapService.getMap(DefaultWebMapService.java:320) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:302) > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) > org.geoserver.kml.WebMapServiceKmlInterceptor.invoke(WebMapServiceKmlInterceptor.java:34) > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) > org.geoserver.gwc.wms.CacheSeedingWebMapService.invoke(CacheSeedingWebMapService.java:62) > org.geoserver.gwc.wms.CacheSeedingWebMapService.invoke(CacheSeedingWebMapService.java:36) > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) > org.geoserver.gwc.wms.CachingWebMapService.invoke(CachingWebMapService.java:74) > org.geoserver.gwc.wms.CachingWebMapService.invoke(CachingWebMapService.java:55) > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) > org.geoserver.ows.util.RequestObjectLogger.invoke(RequestObjectLogger.java:55) > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:208) > at com.sun.proxy.$Proxy61.getMap(Un

Re: [Geoserver-users] ImageMosaic don't load

2016-08-04 Thread Geographic Information Systems Stack Exchange sign up log in Questions Tags Users Badges Unanswered Ask Read this post in our app! up vote down vote favorite Image Mosaic in GeoServer? geoserver I use to geoserver in 2.9 under Windows Server on 2008 64bits. The plugin GDAL raster is correctly installed, but by wanting to make a mosaic and then loaded her in a GIS, nothing displays. If I make one raster it is OK (tiff or dted), but a mosaic not.. even for 2 rasters. In the log I have the following error: Error rendering coverage one the fast path ogr.geotools.coverage.processing. CoverageProcessingException: java.lang. UnsupportedOperationException: Not implemented Ideas? I have installed JAI lib and JAI image I/O but it didn't change anything.. Log geoserver : 2016-08-03 10:49:34,770 INFO [geoserver.wms] - Request: getServiceInfo 2016-08-03 10:49:34,801 INFO [geoserver.wms] - Request: getCapabilities Namespace = raster UpdateSequence = null Request = GetCapabilities RawKvp = {REQUEST=GetCapabilities, SERVICE=WMS} Get = false BaseUrl = http://localhost:8080/geoserver/ RequestCharset = null Version = 1.3.0 2016-08-03 10:49:37,438 INFO [geoserver.wms] - Request: getServiceInfo 2016-08-03 10:49:37,453 INFO [geoserver.wms] - Request: getCapabilities Namespace = raster UpdateSequence = null Request = GetCapabilities RawKvp = {REQUEST=GetCapabilities, SERVICE=WMS} Get = false BaseUrl = http://localhost:8080/geoserver/ RequestCharset = null Version = 1.3.0 2016-08-03 10:49:37,699 INFO [geoserver.wms] - Request: getServiceInfo 2016-08-03 10:49:41,179 ERROR [geoserver.ows] - org.geoserver.platform.ServiceException: Error rendering coverage on the fast path org.geoserver.wms.map.RenderedImageMapOutputFormat.produceMap(RenderedImageMapOutputFormat.java:346) org.geoserver.wms.map.RenderedImageMapOutputFormat.produceMap(RenderedImageMapOutputFormat.java:261) org.geoserver.wms.map.RenderedImageMapOutputFormat.produceMap(RenderedImageMapOutputFormat.java:131) at org.geoserver.wms.GetMap.executeInternal(GetMap.java:505) at org.geoserver.wms.GetMap.run(GetMap.java:249) at org.geoserver.wms.GetMap.run(GetMap.java:119) org.geoserver.wms.DefaultWebMapService.getMap(DefaultWebMapService.java:320) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:302) org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) org.geoserver.kml.WebMapServiceKmlInterceptor.invoke(WebMapServiceKmlInterceptor.java:34) org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) org.geoserver.gwc.wms.CacheSeedingWebMapService.invoke(CacheSeedingWebMapService.java:62) org.geoserver.gwc.wms.CacheSeedingWebMapService.invoke(CacheSeedingWebMapService.java:36) org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) org.geoserver.gwc.wms.CachingWebMapService.invoke(CachingWebMapService.java:74) org.geoserver.gwc.wms.CachingWebMapService.invoke(CachingWebMapService.java:55) org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) org.geoserver.ows.util.RequestObjectLogger.invoke(RequestObjectLogger.java:55) org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:208) at com.sun.proxy.$Proxy61.getMap(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.geoserver.ows.Dispatcher.execute(Dispatcher.java:840) org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:268) org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:147) org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:50) org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959) org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893) org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:968)

Re: [Geoserver-users] ImageMosaic don't load

2016-08-03 Thread Andrea Aime On Tue, Aug 2, 2016 at 2:52 PM, ra2f wrote: > In the log I have the following error: > Error rendering coverage one the fast path > ogr.geotools.coverage.processing. > CoverageProcessingException: java.lang. UnsupportedOperationException: Not > implemented Hum... please share the full stack trace, you'll find it in the geoserver logs. Just a hunch, are you on OSX? Cheers Andrea 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 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or 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. Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users I am already working with the REST API with OWSLib. I tried using purge='all' and recurse=True and here is the output I get in GeoServer logs : The thing is that the table is apparently removed so I don't see why GeoServer is complaining. But the purge = 'all' does no do exactely as I expected : it removed all the granules and the table, but the directory that was holding the granules still exists after the purge and contains datastore.properties, indexer.properties, timeregex.properties and sample_image. I was expecting this folder and all its content to disappear. Cyril View this message in context: http://osgeo-org.1560.x6.nabble.com/ImageMosaic-drop-bbox-table-tp5271113p5271810.html Sent from the GeoServer - User mailing list archive at Nabble.com. What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381 Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users

1 2 3 >