Hot answers tagged geoserver
POLYGON((-90.89 46.67,-90.89 46.67,-90.89 46.67,-90.89 46.67,-90.89 46.67)) Looks like WKT. If it is, you can convert features/layers/geojson to WKT using Wellknown or Wicket-Leaflet
GeoServer supports the WMS GetLegendGraphics request. See: http://docs.geoserver.org/latest/en/user/services/wms/get_legend_graphic/legendgraphic.html
Finally, iant's answer led me to the goal. For completeness I post what I have done: After creating the datasource, main information on the WFS layers are known to geoserver. So I only had to do POST /geoserver/rest/workspaces/my_workspace/datastores/my_datastore/featuretypes with the name of the WFS layer, I wanted to publish ...
You have to create a FeatureType before you can create a Layer (i.e. publish it). If you have already created a test layer then fetch the feature type of that one (like http://geoserver.ianturton.com/rest/workspaces/topp/datastores/bgs/featuretypes/test_uk_625k_mapped_feature.xml) but you should be able to delete quite a lot of that and leave it for ...
Finally I managed to run ecw plugin inside geoserver version 2.7.2 Downloaded libecw source from http://meuk.technokrat.nl/libecwj2-3.3-2006-09-06.zip Applied this patch https://github.com/makinacorpus/libecw/blob/master/Source/C/NCSUtil/NCSPrefsXML.cpp.rej Ran ./configure, make and sudo make install commands to build. Override generated libs over ...
One of your datastores (cresh:datazones_totkm2sc7) has failed for some reason (it's off the end of the log you've included) - which may be that you've run out of connections, the network blipped... try restarting geoserver and see what happens if you can't see an obvious reason that that datastore is off line.
A simpler approach that might not be giving you exact control is to use the "unit of measure" support. While I haven't tried, give this one a kick (GeoServer specific, OGC way would be quite a bit more verbose): <CssParameter name="font-size">100m</CssParameter> See also the docs for the OGC way: ...
From the answer at http://gis.stackexchange.com/a/72016/7515 I found out that a wms environment parameter can be used to get the actual scale denominator: <ogc:Function name="env"> <ogc:Literal>wms_scale_denominator</ogc:Literal> </ogc:Function> Now, the matter is to define a function that maps it to the desired range: map ...
Only top voted, non community-wiki answers of a minimum length are eligible