On Tue, Jan 14, 2014 at 9:20 PM, Ian Schneider
<[email protected]>wrote:
>
>>>> On Mon, Jan 13, 2014 at 8:42 AM, Andrea Aime <
>>>> [email protected]> wrote:
>>>>
>>>>> On Mon, Jan 13, 2014 at 4:28 PM, Justin Deoliveira <
>>>>> [email protected]> wrote:
>>>>>
>>>>>> Yup, I implemented the mosaic support and that is code that I am not
>>>>>> familiar with so not surprised there are issues with the implementation.
>>>>>> I
>>>>>> cobbled it together based on the docs and code samples i could find.
>>>>>> Improvements very welcome, I'll delegate to you and the mosaic experts as
>>>>>> to what is appropriate.
>>>>>>
>>>>>
>>>>> My instinct would be to strip the granule handling from the importer,
>>>>> have it create the indexer.properties file instead,
>>>>> and have the mosaic machinery build everything else automatically.
>>>>>
>>>>> That makes sense to me.
>>>>
>>>>
>>>>> I'm just not sure whether we'd end up missing some feature that was
>>>>> required in the importer, that the normal
>>>>> mosaic machinery does not cover?
>>>>>
>>>>
>>>> I think the biggest thing is that we want to preserve is that we want
>>>> users to be able to specify timestamps manually without having to use a
>>>> regular expression or date format string. This stems from mapstory in which
>>>> users upload time series data without a consistent file naming convention.
>>>>
>>>
> The goals were 3, really:
>
> 1) don't make end users have to specify a regular expression (since they'd
> probably rather give up)
> 2) provide reasonable support for finding ISO dates in the file names
> without any configuration
> 3) allow specifying a format or literal value if some ambiguity or
> inconsistency existed
>
> Personally, I'm happy with 1 and 2 and in the case of 3 just saying -
> "your files should adhere to one of the following conventions".
>
>
>>
>>> Ah, I see... wondering, and what if the files were renamed to include a
>>> iso date at the end during import?
>>> Would it be bad? Just checking what options we have, Carlo's suggestions
>>> are good also, but what if we
>>> wanted to allow the configuration of more property extractors... I mean,
>>> we'd end up duplicating more and
>>> more of the mosaic own functionality.
>>>
>>
>> CCing ian as he is more familiar with this use case. BUt my thought is
>> yes it would be fine to rename the files after the user has configured the
>> timestamps and proceeded with import.
>>
>
> I can't comment much on the proposed implementation/internals except to
> say that renaming files would be fine, but if it's possible to support some
> reasonable defaults and (if possible) also allow a fallback to supporting
> user-specified values (sans regex), that would fulfill the use case.
>
I see, thanks for the feedback.
Given that the beta release is in just a few days, do you mind if we
disable the mosaic import functionality for the moment,
in order to graduate the module, and re-enable it once it can be fixed?
>
> Thanks for looking into the failures Andrea, not sure why I wasn't seeing
> them...
>
I guess you had out of date mosaic jars in your classpath, it happens if
you don't also build geotools from sources
Cheers
Andrea
--
== Our support, Your Success! Visit http://opensdi.geo-solutions.it for
more information ==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
