Re: [Geoserver-devel] 1.7.6 Release

[Mark Leslie]

To be honest, I haven't found most things in the new docs... Now that 
I'm looking again, it seems that I only searched the developer docs. 
That separation is going to get me alot :(  I will update the links.

--
Mark


Mike Pumphrey wrote:
> Hi Mark.  Thanks for the post!  My only wish was that the links were to the 
> new docs instead of the old docs.  :/   (Unless you were linking to things 
> that didn't exist in the new docs, in which case we should JIRA those.)
> 
> Thanks,
> Mike Pumphrey
> OpenGeo - http://opengeo.org
> 
> 
> Mark Leslie wrote:
>> I've saved a short blog post for review.  If there's anything I should 
>> mention that I've left out, let me know.
>>
>> --
>> Mark
>>
>>
>> Mark Leslie wrote:
>>> Damn,  I didn't realise you were gone or I would have gotten something 
>>> drafted last night.  I'll put something together this morning.
>>>
>>> --
>>> Mark
>>>
>>> Mike Pumphrey wrote:
 I edited the template and the 1.7.6 page to reflect the two different 
 Winstallers we have.  I also fixed a typo in the template that prevented 
 the pregen features plugin from downloading properly.

 I don't see any draft on the GeoServer Blog, otherwise I would put on my 
 editor's cap.  Since I'm out for the rest of the week, someone else may 
 have to wear that cap for this post.


 Thanks,
 Mike Pumphrey
 OpenGeo - http://opengeo.org


 Andrea Aime wrote:
> Justin Deoliveira ha scritto:
>> Great work on the release Mark! Congrats.
>>
>> I will happily build the OSX installer and upload it shortly.
>>
>> As for freshmeat, i think Chris (CC'd) might be the only admin, so 
>> hopefully we can either pass the reigns off to one of us, or add you 
>> himself.
> I think in the end Mark managed to make the release announcement
> go there too, it seems you don't need to be a manager to post those
> (the news gets into a queue for some human checking before public
>   consumption, or something like that).
>
>  From IRC conversation:
>
> (09:09:30) aaime: I do have access but not sure how I got to be able and 
> announce a release
> (09:09:48) mleslie: Excellent, thanks.
> (09:10:04) mleslie: I could be mistaken about freshmeat.  Couldn't see 
> the links the docs describe though.
> (09:10:50) mleslie: Ahh, there's a 'manage roles' link in an 
> 'Administration' box on the right of the page.
> (09:10:56) mleslie: I'm not allowed to manage roles :)
> (09:11:40) aaime: mleslie, I don't have access either
> (09:11:47) aaime: probably in the past it was not necessary
> (09:11:47) mleslie: A.  I can submit a release.  They must have 
> redesigned the page.  So... no worries.
> (09:12:16) arneke: ah, was so busy writing up the email I didnt see this 
> conversation. Oh well.
> (09:12:34) mleslie: Someone may need to approve, but they'll get an 
> email I'm sure.
>
> Cheers
> Andrea
>
 --
 Let Crystal Reports handle the reporting - Free Crystal Reports 2008 
 30-Day 
 trial. Simplify your report design, integration and deployment - and focus 
 on 
 what you do best, core application coding. Discover what's new with 
 Crystal Reports now.  http://p.sf.net/sfu/bobj-july
 ___
 Geoserver-devel mailing list
 Geoserver-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>> --
>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
>>> trial. Simplify your report design, integration and deployment - and focus 
>>> on 
>>> what you do best, core application coding. Discover what's new with 
>>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>>> ___
>>> Geoserver-devel mailing list
>>> Geoserver-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>> --
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
>> trial. Simplify your report design, integration and deployment - and focus 
>> on 
>> what you do best, core application coding. Discover what's new with 
>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you d

Re: [Geoserver-devel] numDecimals setting for query with multiple feature types

[Justin Deoliveira]

Gabriel Roldan wrote:
> Given the options I would say Use the maximum, using global only if at 
> least one of the queried types has no numDecimals configured (is it 
> Integer.MAX_VALUE in that case?). Rationale being it's the one going to 
> cause least damage (ie, you may get some more decimals for a type, but 
> won't loose precision for the ones with a higher numdecimals), and still 
> respect the setting as much as possible?

That is a good point, i never thought about it like that. Maximum number 
does make more sense in that light.
> 
> I'm not sure what would be involved in making the encoder respect the 
> settings for each one though...
Not that much work i suppose, just add a map of feature type to number 
of decimals...
> 
> my 2c.-
> 
> Cheers,
> Gabriel
> 
> Justin Deoliveira wrote:
>> Hi all,
>>
>> On trunk max number of decimals is stored on a per feature type basis, 
>> however its not hooked up to any of the encoders, only the global one 
>> is respected.
>>
>> http://jira.codehaus.org/browse/GEOS-3332
>>
>> Fixing is easy, however I began to think of what the behavior should 
>> be when the wfs query contains multiple types since the encoders only 
>> accept a single value for all features, not one per feature type.
>>
>> I can think of a couple of different options:
>>
>> 1. use the minimum of all the per feature type values and the global
>> 2. use the maximum ""
>> 3. ignore the per feature type settings when multiple types are being 
>> queried and just use the global
>>
>> Thoughts? Using maxFeatures as a guide it would seem #1 would be the 
>> most consistent. But I could also see a case made for #3 as well.
>>
>> -Justin
>>
> 


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

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Translating GeoServer 2.0 UI

[Gabriel Roldan]

Just to add to Dave's explanation, I would like to recommend the use of 
ResourceBundleEditor  
plugin for eclipse when creating a new UI translation.

It allows to work on various languages at a time and to quickly locate 
any missing resource, at the cost of leaving it take control of the 
.properties file organization, which is a price I'm glad to pay after 
having translated the whole udig 1.1 resources some years ago (that is, 
the resources inside the file may end up in a different order than in 
the english one).

Cheers,
Gabriel

David Winslow wrote:
> In the source tree (mostly under src/web/, but in any module that
> contributes Wicket pages.  Please don't forget the GeoSearch module ;) )
> each module's src/main/java/ directory contains a file called
> GeoServerApplication.properties.  These files contain the
> English/default translations for the i18n'ized strings in the UI.  Other
> languages can be added by copying the files and suffixing an underscore
> and the language code to the main part of the filename (ie, the de
> translation lives in a set of GeoServerApplication_de.properties files.)
> 
> The translations should preserve the keys exactly (everything before the
> = sign; case-sensitive) and replace the English text on each line with
> the translation.  Translations can include positional parameters; these
> are identified by number starting at zero.  So, if we are translating a
> phrase that talks about some table, like this:
> foo.bar.tablename=The table's name is {0}
> 
> then the corresponding Spanish translation might (please don't hurt me,
> native speakers!) go like this:
> foo.bar.tablename={0} es el nombre de la tabla.
> 
> These parameters do not have to appear in the same order in different
> translations.
> 
> Hope this helps.
> 
> --
> David Winslow
> OpenGeo - http://opengeo.org/
> 
> On Mon, 2009-08-10 at 18:06 -0400, Mike Pumphrey wrote:
>> In 1.7.x, we have a number of different languages set up in the UI.  It 
>> sounds like we don't have the same for 2.0.x.  Is this true?  How does one 
>> create a new language pack for 2.0?  If there are no instructions yet, I'm 
>> happy to write them.
>>
>>
>> Thanks,
>> Mike Pumphrey
>> OpenGeo - http://opengeo.org
>>
>> --
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
>> trial. Simplify your report design, integration and deployment - and focus 
>> on 
>> what you do best, core application coding. Discover what's new with 
>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
> 
> 
> --
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with 
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Translating GeoServer 2.0 UI

[David Winslow]

Oops, almost forgot: there is also an XML encoding available for those
who need to specify the character set for their translations.  This
should work in theory, but hasn't been tested (and indeed, I seem to
recall some issues when we tried it out the first time.)  (at least) If
we get a volunteer to provide translations in a non-latin-ish character
set, someone should probably double-check that all the pieces are in
place for that to happen.  For the record, the format is described in
the documentation for the Java Properties class:

http://java.sun.com/j2se/1.5.0/docs/api/java/util/Properties.html

--
David Winslow
OpenGeo -- http://opengeo.org/

On Mon, 2009-08-10 at 18:25 -0400, David Winslow wrote:
> In the source tree (mostly under src/web/, but in any module that
> contributes Wicket pages.  Please don't forget the GeoSearch module ;) )
> each module's src/main/java/ directory contains a file called
> GeoServerApplication.properties.  These files contain the
> English/default translations for the i18n'ized strings in the UI.  Other
> languages can be added by copying the files and suffixing an underscore
> and the language code to the main part of the filename (ie, the de
> translation lives in a set of GeoServerApplication_de.properties files.)
> 
> The translations should preserve the keys exactly (everything before the
> = sign; case-sensitive) and replace the English text on each line with
> the translation.  Translations can include positional parameters; these
> are identified by number starting at zero.  So, if we are translating a
> phrase that talks about some table, like this:
> foo.bar.tablename=The table's name is {0}
> 
> then the corresponding Spanish translation might (please don't hurt me,
> native speakers!) go like this:
> foo.bar.tablename={0} es el nombre de la tabla.
> 
> These parameters do not have to appear in the same order in different
> translations.
> 
> Hope this helps.
> 
> --
> David Winslow
> OpenGeo - http://opengeo.org/
> 
> On Mon, 2009-08-10 at 18:06 -0400, Mike Pumphrey wrote:
> > In 1.7.x, we have a number of different languages set up in the UI.  It 
> > sounds like we don't have the same for 2.0.x.  Is this true?  How does one 
> > create a new language pack for 2.0?  If there are no instructions yet, I'm 
> > happy to write them.
> > 
> > 
> > Thanks,
> > Mike Pumphrey
> > OpenGeo - http://opengeo.org
> > 
> > --
> > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> > trial. Simplify your report design, integration and deployment - and focus 
> > on 
> > what you do best, core application coding. Discover what's new with 
> > Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> > ___
> > Geoserver-devel mailing list
> > Geoserver-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/geoserver-devel
> 
> 
> --
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with 
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Translating GeoServer 2.0 UI

[David Winslow]

In the source tree (mostly under src/web/, but in any module that
contributes Wicket pages.  Please don't forget the GeoSearch module ;) )
each module's src/main/java/ directory contains a file called
GeoServerApplication.properties.  These files contain the
English/default translations for the i18n'ized strings in the UI.  Other
languages can be added by copying the files and suffixing an underscore
and the language code to the main part of the filename (ie, the de
translation lives in a set of GeoServerApplication_de.properties files.)

The translations should preserve the keys exactly (everything before the
= sign; case-sensitive) and replace the English text on each line with
the translation.  Translations can include positional parameters; these
are identified by number starting at zero.  So, if we are translating a
phrase that talks about some table, like this:
foo.bar.tablename=The table's name is {0}

then the corresponding Spanish translation might (please don't hurt me,
native speakers!) go like this:
foo.bar.tablename={0} es el nombre de la tabla.

These parameters do not have to appear in the same order in different
translations.

Hope this helps.

--
David Winslow
OpenGeo - http://opengeo.org/

On Mon, 2009-08-10 at 18:06 -0400, Mike Pumphrey wrote:
> In 1.7.x, we have a number of different languages set up in the UI.  It 
> sounds like we don't have the same for 2.0.x.  Is this true?  How does one 
> create a new language pack for 2.0?  If there are no instructions yet, I'm 
> happy to write them.
> 
> 
> Thanks,
> Mike Pumphrey
> OpenGeo - http://opengeo.org
> 
> --
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with 
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Translating GeoServer 2.0 UI

[Mike Pumphrey]

In 1.7.x, we have a number of different languages set up in the UI.  It sounds 
like we don't have the same for 2.0.x.  Is this true?  How does one create a 
new language pack for 2.0?  If there are no instructions yet, I'm happy to 
write them.


Thanks,
Mike Pumphrey
OpenGeo - http://opengeo.org

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] numDecimals setting for query with multiple feature types

[Gabriel Roldan]

Given the options I would say Use the maximum, using global only if at 
least one of the queried types has no numDecimals configured (is it 
Integer.MAX_VALUE in that case?). Rationale being it's the one going to 
cause least damage (ie, you may get some more decimals for a type, but 
won't loose precision for the ones with a higher numdecimals), and still 
respect the setting as much as possible?

I'm not sure what would be involved in making the encoder respect the 
settings for each one though...

my 2c.-

Cheers,
Gabriel

Justin Deoliveira wrote:
> Hi all,
> 
> On trunk max number of decimals is stored on a per feature type basis, 
> however its not hooked up to any of the encoders, only the global one is 
> respected.
> 
> http://jira.codehaus.org/browse/GEOS-3332
> 
> Fixing is easy, however I began to think of what the behavior should be 
> when the wfs query contains multiple types since the encoders only 
> accept a single value for all features, not one per feature type.
> 
> I can think of a couple of different options:
> 
> 1. use the minimum of all the per feature type values and the global
> 2. use the maximum ""
> 3. ignore the per feature type settings when multiple types are being 
> queried and just use the global
> 
> Thoughts? Using maxFeatures as a guide it would seem #1 would be the 
> most consistent. But I could also see a case made for #3 as well.
> 
> -Justin
> 


--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] numDecimals setting for query with multiple feature types

[Justin Deoliveira]

Hi all,

On trunk max number of decimals is stored on a per feature type basis, 
however its not hooked up to any of the encoders, only the global one is 
respected.

http://jira.codehaus.org/browse/GEOS-3332

Fixing is easy, however I began to think of what the behavior should be 
when the wfs query contains multiple types since the encoders only 
accept a single value for all features, not one per feature type.

I can think of a couple of different options:

1. use the minimum of all the per feature type values and the global
2. use the maximum ""
3. ignore the per feature type settings when multiple types are being 
queried and just use the global

Thoughts? Using maxFeatures as a guide it would seem #1 would be the 
most consistent. But I could also see a case made for #3 as well.

-Justin

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

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] 1.7.6 Release

[Mike Pumphrey]

Hi Mark.  Thanks for the post!  My only wish was that the links were to the new 
docs instead of the old docs.  :/   (Unless you were linking to things that 
didn't exist in the new docs, in which case we should JIRA those.)

Thanks,
Mike Pumphrey
OpenGeo - http://opengeo.org


Mark Leslie wrote:
> I've saved a short blog post for review.  If there's anything I should 
> mention that I've left out, let me know.
> 
> --
> Mark
> 
> 
> Mark Leslie wrote:
>> Damn,  I didn't realise you were gone or I would have gotten something 
>> drafted last night.  I'll put something together this morning.
>>
>> --
>> Mark
>>
>> Mike Pumphrey wrote:
>>> I edited the template and the 1.7.6 page to reflect the two different 
>>> Winstallers we have.  I also fixed a typo in the template that prevented 
>>> the pregen features plugin from downloading properly.
>>>
>>> I don't see any draft on the GeoServer Blog, otherwise I would put on my 
>>> editor's cap.  Since I'm out for the rest of the week, someone else may 
>>> have to wear that cap for this post.
>>>
>>>
>>> Thanks,
>>> Mike Pumphrey
>>> OpenGeo - http://opengeo.org
>>>
>>>
>>> Andrea Aime wrote:
 Justin Deoliveira ha scritto:
> Great work on the release Mark! Congrats.
>
> I will happily build the OSX installer and upload it shortly.
>
> As for freshmeat, i think Chris (CC'd) might be the only admin, so 
> hopefully we can either pass the reigns off to one of us, or add you 
> himself.
 I think in the end Mark managed to make the release announcement
 go there too, it seems you don't need to be a manager to post those
 (the news gets into a queue for some human checking before public
   consumption, or something like that).

  From IRC conversation:

 (09:09:30) aaime: I do have access but not sure how I got to be able and 
 announce a release
 (09:09:48) mleslie: Excellent, thanks.
 (09:10:04) mleslie: I could be mistaken about freshmeat.  Couldn't see 
 the links the docs describe though.
 (09:10:50) mleslie: Ahh, there's a 'manage roles' link in an 
 'Administration' box on the right of the page.
 (09:10:56) mleslie: I'm not allowed to manage roles :)
 (09:11:40) aaime: mleslie, I don't have access either
 (09:11:47) aaime: probably in the past it was not necessary
 (09:11:47) mleslie: A.  I can submit a release.  They must have 
 redesigned the page.  So... no worries.
 (09:12:16) arneke: ah, was so busy writing up the email I didnt see this 
 conversation. Oh well.
 (09:12:34) mleslie: Someone may need to approve, but they'll get an 
 email I'm sure.

 Cheers
 Andrea

>>> --
>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
>>> trial. Simplify your report design, integration and deployment - and focus 
>>> on 
>>> what you do best, core application coding. Discover what's new with 
>>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>>> ___
>>> Geoserver-devel mailing list
>>> Geoserver-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>> --
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
>> trial. Simplify your report design, integration and deployment - and focus 
>> on 
>> what you do best, core application coding. Discover what's new with 
>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
> 
> --
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with 
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [jira] Created: (GEOS-3332) WFS output ignores numDecimals on a feature type

[Justin Deoliveira (JIRA)]

WFS output ignores numDecimals on a feature type


 Key: GEOS-3332
 URL: http://jira.codehaus.org/browse/GEOS-3332
 Project: GeoServer
  Issue Type: Bug
Affects Versions: 2.0-beta2
Reporter: Justin Deoliveira
Assignee: Justin Deoliveira
 Fix For: 2.0-RC1


Seems that only the global numDecimals setting has an affect.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] EPSG:900913 -> EPSG:3785 ?

[Justin Deoliveira]

Well I think it would be easy enough to add a entry to the user 
projections file that we ship with the data directory. We would have to 
add some notes to people upgrading though using a previous data dir, 
that they should update the file.

Another alternative might be to add the definition directly in code in 
during the initialization of the referencing sub system.

Arne Kepp wrote:
> //I am aware that a proper EPSG database upgrade hinges on a new db 
> engine for GeoTools etc etc...[1]
> 
> But I am wondering whether we, in time for GS 2.0, should create an 
> alias (EPSG:3785) for EPSG:900913 ?
> 
> Just so that we can update our docs with the correct code and not 
> encourage further use of EPSG:900913.
> 
> -Arne
> ///
> 1: http://jira.codehaus.org/browse/GEOT-2493
> 
> /
> 


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

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [jira] Created: (GEOS-3331) Unhandled IndexOutOfBoundsException in KML reflector

[David Winslow (JIRA)]

Unhandled IndexOutOfBoundsException in KML reflector


 Key: GEOS-3331
 URL: http://jira.codehaus.org/browse/GEOS-3331
 Project: GeoServer
  Issue Type: Bug
  Components: Google Earth KML Output
Affects Versions: 2.0-beta2
Reporter: David Winslow
Assignee: David Winslow


If you don't provide a layers attribute in requests to the KML reflector, you 
get a raw exception rather than an error message explaining that this field is 
required.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [jira] Created: (GEOS-3330) Generic WFS DescribeFeatureType responds with 1.1.0 response to a 1.0.0 request

[Roger Bedell (JIRA)]

Generic WFS DescribeFeatureType responds with 1.1.0 response to a 1.0.0 request
---

 Key: GEOS-3330
 URL: http://jira.codehaus.org/browse/GEOS-3330
 Project: GeoServer
  Issue Type: Bug
  Components: WFS
Affects Versions: 1.7.6
 Environment: AutoCAD Map 2010 uses OSGeo FDO 3.4 to access WFS. 
Client: AutoCAD Map 2010. Server GeoServer 1.7.4 - 1.7.6
Reporter: Roger Bedell
Assignee: Andrea Aime
 Fix For: 1.7.7


http://ogi.state.ok.us:80/geoserver/wfs?request=DescribeFeatureType&version=1.0.0&service=WFS&REQUEST=DescribeFeatureType
 
 is different in 1.7.3 and 1.7.6
 
 1.7.3 giving back:
 
 
 http://ogi.state.ok.us"; 
 
schemaLocation="http://ogi.state.ok.us:80/geoserver/wfs?request=DescribeFeatureType&service=wfs&version=1.0.0&typeName=...
 
 and 1.7.6 giving back:
 
 
 http://ogi.state.ok.us"; 
 
schemaLocation="http://ogi.state.ok.us:80/geoserver/wfs?service=WFS&request=DescribeFeatureType&version=1.1.0&typeName=...
 
A request to 1.0.0 should give  back a 1.0.0 reply, not a 1.1.0 reply. Breaks 
FDO, and thereby AutoCAD Map 2010

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [jira] Created: (GEOS-3329) Exception to add this geotif

[Alfonso Fraguas Bravo (JIRA)]

Exception to add this geotif


 Key: GEOS-3329
 URL: http://jira.codehaus.org/browse/GEOS-3329
 Project: GeoServer
  Issue Type: Bug
Affects Versions: 1.7.6, 1.7.5
 Environment: - 2.6.24-24-generic i686 GNU/Linux
- apache-tomcat-6.0
Reporter: Alfonso Fraguas Bravo
Assignee: Andrea Aime
 Attachments: pnoa_etrs89_recorte.tif

I get "Could not obtain a reader for the CoverageDataSet. Please check
the CoverageDataSet configuration!" when I press Submit for the new
Coverage Store. I try reproject TIF to WGS84 UTM 30 (EPSG:32630) and work fine. 
I try put the epsg
definition in epsg.properties file and I get the same error. Why crash with 
ETRS89 UTM30 (EPSG:25830)?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel