Hi Wayne,
While deprecated, the wms.servlets.KMLReflector is still used
unfortunatly. Its a bit of a mess. But the non-servlet reflector should
be reachable via "/kml/wms". Example:
http://localhost:8080/geoserver/kml/wms?layers=topp:states
wheras the servlet based reflector is at:
localhost:
Wow, a lot to digest ;).
But I think in the end I agree with you. It does not seem to be a huge
win to spend a lot of time getting REST working on 1.7.x if we just have
to redo a lot of it for 2.0 anyways. Especially since its just going to
be something that ties us down as the api will be chan
Specifying Inline Features in an SLD throws an exception
Key: GEOS-2007
URL: http://jira.codehaus.org/browse/GEOS-2007
Project: GeoServer
Issue Type: Bug
Components: WMS
Hi Dave,
Which FAQ entry are you referring to? I only see one about Logging in
Jboss...
Aside, would you perhaps be interested in updating the FAQ directly on
the wiki?
Dave Potts wrote:
> The FAQ entires for Jboss seem to be a little out of date.
>
> This is how to get it to work under linux
Hi John,
This is a cool idea, and I think quite useful. I could see this perhaps
being rolled into the regular datastore once its working. However I
suspect it will require some major changes as the current datastore
makes a lot of assumptions about the shapefile actually being on disk. I
coul
Okay, I had that chat with Rolando and got an exhaustive list of what
pages we'd like to have for 2.0.0. They're listed on the same wiki page
now (http://geoserver.org/display/GEOS/Wicket+UI+TODOs for those of you
who don't like scrolling). I was lazy and just filled in the chart from
memory,
Hi all,
As I'd like to be able to include RESTConfig in 1.7.0 when it comes out
I am trying to assess its current state and work out how much needs to
happen before it makes sense to consider it for inclusion. Right now it
provides configuration for datastores, coveragestores, featuretypes,
c
The FAQ entires for Jboss seem to be a little out of date.
This is how to get it to work under linux
copy geoserver.war to the deploy directory eg server/default/deploy
Define the envronmental varible JAVA_OPTS to be
JAVA_OPTS="-DGEOSERVER_DATA_DIR=path/name"
export JAVA_OPTS
then use run.sh t
Hi all,
I'm working on a feature that will add an optional format_options item
and have been digging around the code. I can recognize a new item when
using a full wms request by adding stuff to the FormatOptionsKvpParser
and the applicationContext.xml. The problem comes when I try to use a
k
Justin Deoliveira ha scritto:
> I have not had much time to work on the simple feature speed up. I got
> an initial implementation turning over but it still needs work. There is
> also a lot of code that will have to be updated to use it.
>
> But yes, I agree we should definitely try to branch t
I have some shape files that I want to use in geoserver (read only), but
they are stored within zip files, and I don't want to have to unzip them to
other directories. I was thinking of writing my own datastore based on the
existing one for shape files, and just changing the I/O methods to access
t
Alessio Fabiani ha scritto:
> Ok David also sorry for the tabs, I always forget to setup the
> formatter when creating a new workspace.
Yep, I used to stumble into that as well. That's why I created
a "template" workspace to solve that issue. Basically I created
an empty workspace, set the fo
Ok David also sorry for the tabs, I always forget to setup the formatter
when creating a new workspace.
On Wed, Jun 25, 2008 at 5:01 PM, David Winslow <[EMAIL PROTECTED]>
wrote:
> Hi Alessio,
>
> I noticed that you have added sldService to the RESTConfig profile in web,
> but to its own profi
Hi Alessio,
I noticed that you have added sldService to the RESTConfig profile in
web, but to its own profile in community. The two are independent and
mostly unrelated, so I would prefer to keep them as separate modules
activated by independent profiles. I'm going ahead and making this
cha
Hi all (hello Arne),
I would like to include the wfsv online tests into
the build process. The instructions to enable
the online tests contained in the wfsv module
can be found in the wfsv module, direct link
follows:
https://svn.codehaus.org/geoserver/trunk/geoserver/wfsv/testing.txt
Cheers
Andre
Andrea Aime wrote:
> Justin Deoliveira ha scritto:
>> David Winslow wrote:
>>> Okay, I thought the decision about the layer preview list was that it
>>> would be broken up into a list of previews on each layer's
>>> configuration page. ie, the links you would click to see each would be
>>> old:
Justin Deoliveira ha scritto:
> David Winslow wrote:
>> Okay, I thought the decision about the layer preview list was that it
>> would be broken up into a list of previews on each layer's configuration
>> page. ie, the links you would click to see each would be
>> old: welcome->demo->map preview
David Winslow wrote:
> It does seem like having 'dump entire catalog' functionality would be
> useful (for migrating between different persistence mechanisms) so (for
> another compromises solution) maybe we could just have a button to
> download/snapshot the catalog and leave it up to the admin
>
> For what it's worth, I'd just go to the direct save route. People
> are working directly against databases with a lot of software, and
> none of it give you the "undo/redo" ability of a desktop app without
> much complaints.
Good point.
>
> Wait... what did I just say? Undo/redo huh? We _co
It does seem like having 'dump entire catalog' functionality would be
useful (for migrating between different persistence mechanisms) so (for
another compromises solution) maybe we could just have a button to
download/snapshot the catalog and leave it up to the admin to handle
backup policy.
-
David Winslow wrote:
> Okay, I thought the decision about the layer preview list was that it
> would be broken up into a list of previews on each layer's configuration
> page. ie, the links you would click to see each would be
> old: welcome->demo->map preview->{some layer + format}
> new: welco
Justin Deoliveira ha scritto:
>
>> I share the same concern. We do want to save along the way since we
>> cannot be sure there will be a clean shutdown (jvm segfaults anybody?),
>> so eventually on shutdown we'd just be saving whatever was already
>> saved the last time the config did change?
>
>
I have not had much time to work on the simple feature speed up. I got
an initial implementation turning over but it still needs work. There is
also a lot of code that will have to be updated to use it.
But yes, I agree we should definitely try to branch trunk to 2.5.x
before the style work lan
> I share the same concern. We do want to save along the way since we
> cannot be sure there will be a clean shutdown (jvm segfaults anybody?),
> so eventually on shutdown we'd just be saving whatever was already
> saved the last time the config did change?
Yeah its a darned if you do darned if y
Okay, I thought the decision about the layer preview list was that it
would be broken up into a list of previews on each layer's configuration
page. ie, the links you would click to see each would be
old: welcome->demo->map preview->{some layer + format}
new: welcome->layers->{some layer}->{some
Data stored in Oracle with a projection already assigned can not be shown
properly
--
Key: GEOS-2006
URL: http://jira.codehaus.org/browse/GEOS-2006
Project: GeoServer
Dispatcher breaks on kvp parse when strict=true is used
---
Key: GEOS-2005
URL: http://jira.codehaus.org/browse/GEOS-2005
Project: GeoServer
Issue Type: Bug
Affects Versions: 1.7.0-beta
Andrea Aime ha scritto:
> Hi people,
> on gt2 a proposal that _might_ change lots of code is about
> to be voted
> (http://docs.codehaus.org/display/GEOTOOLS/Upgrading+styles).
>
> The proposal is going to provide us quite some goodness
> in the long term (once we have xml parsers/readers for
> it
Hi people,
on gt2 a proposal that _might_ change lots of code is about
to be voted
(http://docs.codehaus.org/display/GEOTOOLS/Upgrading+styles).
The proposal is going to provide us quite some goodness
in the long term (once we have xml parsers/readers for
it and we implement the extensions in the
Alessio Fabiani ha scritto:
> I fully agree with Andrea ... not only we should replicate demo screens,
> but also we should improve them in order to make them more usable in
> case of large amount of layers (I'm thinking on a preview page
> structured like a tree of nested layers).
What about a
I fully agree with Andrea ... not only we should replicate demo screens, but
also we should improve them in order to make them more usable in case of
large amount of layers (I'm thinking on a preview page structured like a
tree of nested layers).
On Wed, Jun 25, 2008 at 8:38 AM, Andrea Aime <[EMAI
31 matches
Mail list logo
