[Geoserver-users] Geoserver irc logs

GeoServer GeoServer User
1

Where do I get the latest logs because on this site
http://irc.geoserver.org/log/ the last log is of the 6th February.

--
Sent from my mobile device

Sindile Bidla

2

Intengu Technologies wrote:

Where do I get the latest logs because on this site
http://irc.geoserver.org/log/ the last log is of the 6th February.
  
Hi,

unforunately georj (the bot that records) runs on a machine with a faulty memory controller, and it went bye-bye over the weekend, and nobody noticed he was missing. I've restarted it, but there's a hole.

Not sure what happened to the IRC Logs from the meeting, I thought someone said they were going to put them up, but I can only find two instances of the February 3rd logs. It was mainly a run through the development road map.

-Arne

--
Arne Kepp
OpenGeo - http://opengeo.org
Expert service straight from the developers

3

Hi list,
I'm playing with GeoServer time templates and I would like to use ranges for the dates. I've followed this guide:

http://geoserver.org/display/GEOSDOC/02-Time+Templates

The time template works well.

But in the guide there might be a typo in brackets - should it be really
${DATETIME_ATTRIBUTE_NAME.value}?date("M?d%y")
or
{DATETIME_ATTRIBUTE_NAME.value?date("M?d%y")}

The second works for me.

My question is about specifying the date ranges. My features is referenced to whole year (e.g. 2000, 2001, 2002 etc) and I would like to specify the ranges so the proper feature is shown any time when the slider is 'inside' proper year. For example feature with attribute 'year' = 2000 should be shown for the case when the slider is between 1.1.2000 to 31.12.2000. Is it possible to do this using date range?

Thanks a lot for any help.

Best regards,
Jan.

4

Hi Jan,

Responses inline.

Jan Jezek wrote:

Hi list,
I'm playing with GeoServer time templates and I would like to use ranges for the dates. I've followed this guide:

http://geoserver.org/display/GEOSDOC/02-Time+Templates

The time template works well.

But in the guide there might be a typo in brackets - should it be really
${DATETIME_ATTRIBUTE_NAME.value}?date("M?d%y") or {DATETIME_ATTRIBUTE_NAME.value?date("M?d%y")}

The second works for me.

Yup, you are right. Thanks for the catch. Fixed now.

My question is about specifying the date ranges. My features is referenced to whole year (e.g. 2000, 2001, 2002 etc) and I would like to specify the ranges so the proper feature is shown any time when the slider is 'inside' proper year. For example feature with attribute 'year' = 2000 should be shown for the case when the slider is between 1.1.2000 to 31.12.2000. Is it possible to do this using date range?

Freemarker supports arithmetic operations so how about converting the value to a number and incrementing by one, then the conversion to date. Off the top of my head:

${(DATETIME_ATTRIBUTE_NAME.value?number+1)?datetime('...')}

Let us know if that works.

-Justin

Thanks a lot for any help.

Best regards,
Jan.

------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

5

Thanks - now I understand....
It works by using this in time.ftl:

${year.value?date('yyyy')}||${(year.value?number+1)?date('yyyy')}

Cheers,
Jan.
______________________________________________________________

Od: jdeolive@anonymised.com
Komu: Jan Jezek <h.jezek@anonymised.com>
CC: Geoserver-users@lists.sourceforge.net
Datum: 11.02.2009 17:30
Předmět: Re: [Geoserver-users] time template and date range

Hi Jan,

Responses inline.

Jan Jezek wrote:

Hi list,
I'm playing with GeoServer time templates and I would like to use ranges for the dates. I've followed this guide:
> http://geoserver.org/display/GEOSDOC/02-Time+Templates
> The time template works well.
> But in the guide there might be a typo in brackets - should it be really
${DATETIME_ATTRIBUTE_NAME.value}?date("M?d%y") > or > {DATETIME_ATTRIBUTE_NAME.value?date("M?d%y")}
> The second works for me.

Yup, you are right. Thanks for the catch. Fixed now.

> My question is about specifying the date ranges. My features is referenced to whole year (e.g. 2000, 2001, 2002 etc) and I would like to specify the ranges so the proper feature is shown any time when the slider is 'inside' proper year. For example feature with attribute 'year' = 2000 should be shown for the case when the slider is between 1.1.2000 to 31.12.2000. Is it possible to do this using date range?
Freemarker supports arithmetic operations so how about converting the value to a number and incrementing by one, then the conversion to date. Off the top of my head:

${(DATETIME_ATTRIBUTE_NAME.value?number+1)?datetime('...')}

Let us know if that works.

-Justin

Thanks a lot for any help.
> Best regards,
Jan.
> > > ------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

-- Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.