Im not sure, but I suspect that this option has been removed. It previously existed to prevent out of memory errors since the old geoserver would read all the features into memory then return then as GML. The new Geoserver only reads one feature at a time before writing its GML so Out of memory errors are not an issue. Chris or Jody may correct me on this though.
You can still limit the number of returned features in a client request though.
Sean
-----Original Message-----
From: Bronwyn Cook [mailto:bronwyn.cook@anonymised.com]
Sent: Monday, 19 January 2004 9:15 AM
To: Geoserver List
Subject: [Geoserver-devel] How do you set the MaxFeatures
limit in Geoserver 1.1?
Hello,
In geoserver 1.0 there was a 'MaxFeatures' tag in the
configuration.xml file which allowed you to specify the max
number of Features returned by GetFeature. What is its
equivalent in Geoserver 1.1? I can't seem to find anything
similar in its config files.
Cheers
Bronwyn
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004 Premiere
Conference on Open Tools Development and Integration See the
breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Exactly correct. The proper way to limit the number of features is in
the client request. The user config option was to prevent out of
memory errors, so that the admin could limit the number returned to
one that would not crash the server. With out of memory errors no
longer an issue it seemed like time to remove it, since it's a bit
inconsistent to not return a max number of features if they client
doesn't specify a number of limit. Though I guess it could still be a
way for admins to not overload clients who naively ask for all
features. If you or anyone wants the option back in I'm more than
happy to do, I'm pretty sure it's trivial to put back (and actually it
may currently be in the 1.2 branch, as I think I might have removed it
after they branch). I just thought it wouldn't be useful any more.
Chris
Quoting "Geoghegan, Sean" <Sean.Geoghegan@anonymised.com>:
Im not sure, but I suspect that this option has been removed. It
previously existed to prevent out of memory errors since the old
geoserver would read all the features into memory then return then as
GML. The new Geoserver only reads one feature at a time before
writing its GML so Out of memory errors are not an issue. Chris or
Jody may correct me on this though.
You can still limit the number of returned features in a client
request though.
Sean
> -----Original Message-----
> From: Bronwyn Cook [mailto:bronwyn.cook@anonymised.com]
> Sent: Monday, 19 January 2004 9:15 AM
> To: Geoserver List
> Subject: [Geoserver-devel] How do you set the MaxFeatures
> limit in Geoserver 1.1?
>
> Hello,
>
> In geoserver 1.0 there was a 'MaxFeatures' tag in the
> configuration.xml file which allowed you to specify the max
> number of Features returned by GetFeature. What is its
> equivalent in Geoserver 1.1? I can't seem to find anything
> similar in its config files.
>
> Cheers
> Bronwyn
>
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004 Premiere
> Conference on Open Tools Development and Integration See the
> breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/
On Mon, 2004-01-19 at 07:26, cholmes@anonymised.com wrote:
If you or anyone wants the option back in I'm more than
happy to do, I'm pretty sure it's trivial to put back (and actually it
may currently be in the 1.2 branch, as I think I might have removed it
after they branch). I just thought it wouldn't be useful any more.
I'd vote for putting it back in.
Doug
> If you or anyone wants the option back in I'm more than
> happy to do, I'm pretty sure it's trivial to put back (and actually it
> may currently be in the 1.2 branch, as I think I might have removed it
> after they branch). I just thought it wouldn't be useful any more.
I'd vote for putting it back in.
Well I've learned a lesson - never remove configuration options without
asking your users first! 
It's back in on head, will be in 1.2alpha,
beta and .0. If I do a 1.1.1 I'll be sure to get in there as well.
thanks for the feedback,
Chris
Hello,
Well, does anybody know a tool or a way or some documents that explain how
to export a ESRI shapefile (SHP, DBF, SHX) into a relational database, such
as MS-SQL Server?
Thanks a lot
Calegari San
Well, does anybody know a tool or a way or some documents that explain how
to export a ESRI shapefile (SHP, DBF, SHX) into a relational database, such
as MS-SQL Server?
It's quite easy if you want to export it to PostGIS (the most widely used
GeoServer datastore). The installation of PostGIS creates a shp2pgsql
tool, which takes a shapefile as input and outputs the statements needed
to create and populate the postgis tables. More information is available
at http://postgis.refractions.net, and on shp2pgsql at
http://postgis.refractions.net/docs/x405.html#AEN416. We recommend
installing postgis with GEOS support, as its spatial functions greatly
enhance PostGIS, substantially speeding up spatial queries on GeoServer.
Thanks a lot
Calegari San
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
ogr2ogr, by Frank Warmerdam, is part of the gdal tools and can convert
shapefiles to Postgres or into GML which you could parse.
It is at:
http://www.remotesensing.org/gdal/
If you just want the catagories, labels, and other attributes (ie.
everything except the geometry) then just open the .dbf file. It is a
standard old skool dBase file that will open fine in Gnumeric or Excel or
use the perl XBase module.
http://search.cpan.org/~janpaz/DBD-XBase-0.241/lib/XBase.pm
Cheers,
Rich
On Sat, 31 Jan 2004, Aurélio Calegari wrote:
Hello,
Well, does anybody know a tool or a way or some documents that explain how
to export a ESRI shapefile (SHP, DBF, SHX) into a relational database, such
as MS-SQL Server?
Thanks a lot
Calegari San
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel