Tag Info

Hot answers tagged

3

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


3

The same max render time is applied to any WMS request. When doing meta-tiling the internal GeoWebCache makes a single WMS request, which is subject to the max render time. So, if you want to render larger meta-tiles, you will have to increase the max render time accordingly.


3

Your Insert request contains an feature that doesn't match your Schema which is expecting the Point attribute to be called the_geom. You don't get an error because you have marked that feature as Nillable (or optional). <xsd:schema xmlns:gml="http://www.opengis.net/gml" xmlns:opengeo="http://opengeo.org" xmlns:xsd="http://www.w3.org/2001/XMLSchema" ...


2

Ciao, a few things: It looks to me you are mostly rendering vector data, hence JAI does not helpat all If you are mostly serving vector data with complex styling rules, I am hoping you are using a DBMS rather than shapefiles especially for OSM. If not at global scale GeoServer will have to load all the shapefile into memory and then filters as we only ...


2

function getStyle(feature, resolution){ var style; if (feature.get('field_6') === '4') style = new ol.style.Style({ image: new ol.style.Circle({ radius: 6, fill: new ol.style.Fill({ color: 'rgba(20,150,200,0.6)' }), stroke: new ol.style.Stroke({ ...


2

You can do this using a style function (see also the OL3 Example on Earthquake Clusters for a more detailed example of a style function - or search this site!). In your case, partial code would be along the lines of: var myStyleFunction = function(feature, resolution){ var field_1 = feature.get('field_1'); if (field_1 == "PENYEDIA AKOMODASI"){ ...


2

GeoServer indeed tends to swap coordinates on several occasions when using WFS. I couldn't backtrack this phenomenon to its exact origin, only to this post, where it is assumed, this confusion is created by the different axis orientation of EPSG:4326, and CRS:84, which are otherwise identical projections. A possible workaround could be implemented on the ...


2

As user30184 said, the importer extension has been designed exactly for this job, and will convert the data into the format of the chosen target store (e.g., will import the data into postgis or oracle for you). WFS-T is more geared towards single feature editing than "mass import" and can only handle GML anyways.


2

GeoServer supports the WMS GetLegendGraphics request. See: http://docs.geoserver.org/latest/en/user/services/wms/get_legend_graphic/legendgraphic.html


1

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 ...


1

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 ...


1

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.


1

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: ...


1

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 ...


1

I found out the answer, it was human error. I was using the incorrect "name". Once 'postgis:' was removed the layer was found!


1

Ok, I've figured it out. It is possible to apply an affine transform onto some existing CRS using FITTED_CS. Below is an example of rotation of 60 degrees counterclockwise and movement: FITTED_CS["BPAF", PARAM_MT["Affine", PARAMETER["num_row", 3], PARAMETER["num_col", 3], PARAMETER["elt_0_0", -0.5], PARAMETER["elt_0_1", ...


1

You can define a local rotated coordinate sytem as I explained here: Using customized Coordinate System for Archaeological site data Center point and rotation have to be defined in degrees. Your idea of wrapping one projection with another is not defined in PROJ.4. You can try it out, but don't expect it to work.


1

Openlayers 3 does not yet have an SLD parser There's an open issue at https://github.com/openlayers/ol3/issues/2954 that you may +1


1

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 ...


1

Found a solution. As the java.lang.NoClassDefFoundError indicates, classes where missing. I had to add Apache Commons VFS and Logging (downloaded them here), and now i managed to successfully upload a zipped Shapefile with REST Importer.


1

GeoServer can deliver XYZ coordinates if the source data contains Z values. You can make a try by converting the demo shapefile "states.shp" into XYZ shapefile with GDAL: ogr2ogr -f "ESRI Shapefile" states_3d.shp states.shp -nlt MULTIPOLYGONZ Next make a new store and layer from this states_3d shapefile and make test request with WFS ...


1

If you read the WMS Spec you will see how to set the format of the error messages that the server sends you. In this case it is clearly saying that the number 256: is invalid. Somewhere you are sending a request with that number in it, check the URL. For more information turn up the logging verbosity in GeoServer and it will send you back more details, or ...


1

OL3.8.2 only supports WFS 1.1.0. See docs: ol.format.WFS Feature format for reading and writing data in the WFS format. By default, supports WFS version 1.1.0. You can pass a GML format as option if you want to read a WFS that contains GML2 (WFS 1.0.0). Also see ol.format.GMLBase which is used by this format.


1

Geoserver is not mandatory. If you need a WFS or WMS or WMTS or WPS or CSW or WCS server for your application needs, it is an option, but there are other options for all of those, in open source and proprietary forms. If you are looking for open source options, many are listed at OSGeo - see the project links under Web Mapping and Metadata Catalog headings. ...


1

The quickest and easiest solution is to not tile your labels layer. However if this is not an option for you then read on. In general GeoServer tries very hard not to draw labels that won't look good (for some value of good) - i.e. where they overlap, or fall off the side of the map as for most people these look ugly. However because the developers' idea of ...


1

The reason that I could not find any errors in the data in PostGIS appears to be because there are none. So why did GWC fail to seed the cache and report a topology error? The answer is because I was using a style which involved an internal buffer of some polygons to get a graduated 'fade in' effect with a colour transition on the stroke. Since you can't ...


1

GeoServer supports neither, there is a discussion ongoing on how to implement support for HSTORE here: http://osgeo-org.1560.x6.nabble.com/Re-Geoserver-Question-about-PostgreSQL-and-JSON-or-HStore-td5218145.html Supporting JSON columns would be quite a bit more complicated.



Only top voted, non community-wiki answers of a minimum length are eligible