Hey Simone, did you guys ever get time stuff working with vector stuff as well?
It'd be awesome to get 'time' in as a feature for geoserver 2.1.x, and it sounds like you all did most of the work already, it just needs to be documented? I could probably help out with a bit of time to help document, and/or in a few weeks OpenGeo may be able to put some resources towards it. If it's there we also could soon work on a GeoExt time slider or something, maybe incorporate simile, that could show off the capabilities. C On Mon, Nov 8, 2010 at 7:23 AM, Simone Giannecchini < [email protected]> wrote: > Ciao Jefferson, > first a few questions: > > - can you point can you run a gdalinfo on two of those files and paste it > over? > - which version of geoserver are you playing with? > > Now about time management in the ImageMosaic plugin. That is still > undocumented but I can give you a simple example of it is working > right now. > I have a attached a simple zip file that you can use as reference; it > contains a few geotiff from the blue marble over various months, plus > the properties files needed to driver the indexer > which I am now going to explain. > Notice that the outcome index will be a shapefile. > > - indexer.properties - > Drives the indexer to automagically index the directory. Here below > an explanation of the params: > > - TimeAttribute=ingestion tell the indexer which name to use for the > TimeAttribute in the index > - Schema= the_geom:Polygon,location:String,ingestion:java.util.Date > schema for the final index > - PropertyCollectors=TimestampFileNameExtractorSPI[timeregex](ingestion) > tell the PropertyCollector TimestampFileNameExtractor to extract the > value of the ingestion attribute for each granule of the mosaic and > assign it to the ingestion attribute by using the timeregex regular > expression. > > - timeregex.properties - > > Contains a regular expression that extract a time from the name of the > file. In this case regex=[0-9]{6} > > > == How this works == > - place the indexer.properites file as well as the sibling regex files > inside the directory to index > - point the imagemosaic to that directory and create a coverage for it > > A shapefile should be created automatically with the proper fields for > time management. > GeoServer will see by default the TIME attribute in the mosaic and > will expose in the GetCapabilities response. There is one culprit > though, > shapefile does not allow time up to millisec since they are based on > old version of the db4 database file. Therefore we have extended it > to do so, but you need to enable such extension adding the following > switch to GeoServer: > > -Dorg.geotools.shapefile.datetime=true > > Once you get geoserver up and running and you confirm that the > GetCapabilities looks like this: > > http://pastebin.com/CiPPxKBC > > you can open up the openlayers preview and play with the TIME in > ISO8601 format like this: > > ...&format=application/openlayers&TIME=2004-05 > > Hope that helps. > > Ciao, > Simone. > > > > ------------------------------------------------------- > === > Notice that our office phone number has recently changed! > Please, update your records! > === > Ing. Simone Giannecchini > GeoSolutions S.A.S. > Founder > Via Poggio alle Viti 1187 > 55054 Massarosa (LU) > Italy > > phone: +39 0584962313 > fax: +39 0584962313 > mob: +39 333 8128928 > > > http://www.geo-solutions.it > http://geo-solutions.blogspot.com/ > http://www.linkedin.com/in/simonegiannecchini > http://twitter.com/simogeo > > ------------------------------------------------------- > > > > On Thu, Nov 4, 2010 at 3:49 PM, Jefferson Heard > <[email protected]> wrote: > > I have the following directory setup: > > /opt/data/gis/rasters/ndfd/ds.sky > > /opt/data/gis/rasters/ndfd/ds.sky/ds.sky.01.tiff > > /opt/data/gis/rasters/ndfd/ds.sky/ds.sky.02.tiff > > /opt/data/gis/rasters/ndfd/ds.sky/ds.sky.03.tiff > > /opt/data/gis/rasters/ndfd/ds.sky/ds.sky.04.tiff > > /opt/data/gis/rasters/ndfd/ds.sky/ds.sky.05.tiff > > /opt/data/gis/rasters/ndfd/ds.sky/ds.sky.06.tiff > > /opt/data/gis/rasters/ndfd/ds.sky/ds.sky.07.tiff > > /opt/data/gis/rasters/ndfd/ds.sky/ds.sky.08.tiff > > /opt/data/gis/rasters/ndfd/ds.sky/ds.sky.09.tiff > > /opt/data/gis/rasters/ndfd/ds.sky/ds.sky.10.tiff > > /opt/data/gis/rasters/ndfd/ds.sky/ds.sky.11.tiff > > /opt/data/gis/rasters/ndfd/ds.sky/ds.sky.12.tiff > > /opt/data/gis/rasters/ndfd/ds.sky/ds.sky.13.tiff > > /opt/data/gis/rasters/ndfd/ds.sky/ds.sky.14.tiff > > /opt/data/gis/rasters/ndfd/ds.sky/ds.sky.15.tiff > > /opt/data/gis/rasters/ndfd/ds.sky/ds.sky.16.tiff > > /opt/data/gis/rasters/ndfd/ds.sky/ds.sky.17.tiff > > /opt/data/gis/rasters/ndfd/ds.sky/ds.sky.18.tiff > > /opt/data/gis/rasters/ndfd/ds.sky/ds.sky.prj > > All the tiles are exactly the same projection and dimensions, but they're > > all different timeseries offsets. Is there a way to treat this as a > > timeseries instead of a mosaic and a way to get the ImageMosaic plugin to > > recognize all the images? Is there a better way to store a timeseries? > > Right now I try to create a new imagemosaic store by pointing at the > > directory and it just whines at me: > > Could not list layers for this store, an error occurred retrieving them: > > Unable to acquire a reader for this coverage with format: ImageMosaic > > > ------------------------------------------------------------------------------ > > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > > David G. Thomson, author of the best-selling book "Blueprint to a > > Billion" shares his insights and actions to help propel your > > business during the next growth cycle. Listen Now! > > http://p.sf.net/sfu/SAP-dev2dev > > _______________________________________________ > > Geoserver-users mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/geoserver-users > > > > > > > ------------------------------------------------------------------------------ > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > _______________________________________________ > Geoserver-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users > >
------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
