GeoServer | 易学教程

How to increase Maximum Memory Pool Size? Apache Tomcat 9

阅读更多关于 How to increase Maximum Memory Pool Size? Apache Tomcat 9

问题 I am trying to increase my Maximum memory pool in Apache tomcat config . I am using Geo-server services with the help of Apache, however my memory in Geo-server is filling very fast. All the time I have to free memory from Geo-server Server Status. I have to increase my memory to 2048 maximum by stopping Apache server when I increase from 1024 to 2048 Apache is not starting. Can anyone guide me what to do how I should increase my memory size? 回答1: 32bit programs have a severe memory

Openlayers3: tile grid incorrect with pixelratio=3 using Geoserver/Geowebcache as backend

阅读更多关于 Openlayers3: tile grid incorrect with pixelratio=3 using Geoserver/Geowebcache as backend

问题 I'm developing a small webmap using Openlayers3 and geoserver/geowebcache as backend. My goal is to support browsers/displays with pixelratio=1, pixelratio=2 and pixelratio=3. For that I defined in geoserver backend 3 gridsets with tiles sizes 256x256, 512x512 and 768x768. I assume that: pixelratio=1 requires a gridset with tiles sizes 256x256 pixelratio=2 requires a gridset with tiles sizes 512x512 pixelratio=3 requires a gridset with tiles sizes 768x768 Now, my code is working only for

How make GeoServer and leafLet secure in a web applciation

阅读更多关于 How make GeoServer and leafLet secure in a web applciation

问题 I am developing a website and using leafLet for visualization. Data are coming from a database and everything works fine. I developed something like this: https://maps.gcc.tas.gov.au/dogexerciseareas.html As you can see, if you do a right-click on the page and select ViewSource, you can see the servername, port, and database ( typeName : 'GCC_cc:DogExerciseAreas', ). To me, this is not very secure especially if we host everything (IIS, DB, GeoServer,..), So, Is there any way to hide these

OL3 / Geoserver: Vector tile labels gets cropped

阅读更多关于 OL3 / Geoserver: Vector tile labels gets cropped

问题 I am trying to label vector tile point features but they always gets cropped at the tile border. I have tried (among many other things) using the renderBuffer option with no success. I am using OL 3.19 and the vector tiles are served with Geoserver 2.10RC1 and I get the same errors in my production environment as well as editing an Boundless example (http://suite.opengeo.org/docs/latest/dataadmin/vectortiles/index.html). I think maybe the tiles are served correctly from Geoserver and that

使用GeoServer 发布切图服务

阅读更多关于使用GeoServer 发布切图服务

前一篇文章我们使用了 CesiumLab 2 进行栅格影像的切片，这次我们使用另外一款开源的 Web Server 来发布栅格切片——GeoServer 先贴一张我的GeoServer 的主要信息在这里我们可以看到，我的GeoServer 版本是2.15.0，GeoWebCache 版本是1.15.0。记得看过一篇大佬的博客，说老版本的GeoServer，并不会自带GeoWebCache 。当然，GeoWebCache 也可以自行的下载、安装。在这里就不重复了。前提 Jvm GeoServer 发布栅格数据发布栅格数据没错还是上一篇博客用的那张从LSV下载的16级邯郸影像。原数据（经过投影变换、构建金字塔）有2.03G。直接发布，不仅仅客户端显示很慢，对服务器也会造成很大的影响，CPU 风扇嗡嗡响的那种。在数据存储中，新建一个数据存储选择添加GeoTiff 选择栅格文件路径一般坐标系、边框属性都已经默认计算好了没有坐标系的话，设置下边框的设置需要点击下从数据中计算和 Compute from native bounds 计算下就好了设置好了以后，点击上方的 Tile Caching ，预设值切片（不过好像不用设置也好，并没有测试，本次是在设置的情况下进行的切片），设置框框内的内容，其他的都是默认首先是切片等级，本次是1 - 15 级其次是影像类型

geoserver发布dsm

阅读更多关于 geoserver发布dsm

一，确认数据包含三维信息不是所有的数据都包含三维信息，有些软件（例如pix4d）导出的产品并不一定包含高度点信息，所以首先确定数据的正确如果在发布的过程中出现以下情况，很可能是数据问题：二，发布 2.1 新建数据存储选择栅格数据geotiff 注意数据的坐标系与边框范围：某些可视化框架对坐标系有特殊的限制（cesium支持WGS84无投影），可能会影响到可视化效果数据发布后，进入layer Preview进行预览，会得到类似下图效果： 2.2 设置图层样式与普通的影像数据（如正射影像）最大的区别就是没有明显的色彩渲染，观察刚刚发布的图层，看到Coverage Band Details中，没有关于RGB三通道的数据描述，如下：而普通的正射影像是这样：猜测dsm就不包含三通道数据，只包含地表高度信息，利用geoserver新建style（本例是使用sld 栅格数据离散颜色进行渲染）： <?xml version="1.0" encoding="UTF-8"?> <StyledLayerDescriptor version="1.0.0" xmlns="http://www.opengis.net/sld" xmlns:ogc="http://www.opengis.net/ogc" xmlns:xlink="http://www.w3.org/1999/xlink"

How to render a portion of spatial data depending on user location on map

阅读更多关于 How to render a portion of spatial data depending on user location on map

问题 we have every street for texas in a database.The issue is, there are 2million streets. When the user looks at a simple county on the map, it takes FOREVER to render the streets for the county because the query has to go through EVERY SINGLE STREET in the texas table. Does anyone have any advice on how we can split the data across tables and have geoserver query the table needed depending on the current users location they are viewing? For Example Instead of one giant texas table how about

Problem with a column name contains a colon in PostgreSQL

阅读更多关于 Problem with a column name contains a colon in PostgreSQL

问题 I downloaded the shape data from OSM. I have imported data from Shapefile into PostgreSQL without any problem but I got an error when I do the select statement. Select addr:city From location; Error: syntax error at or near ":" The problem is because of the column name contains a colon. Could anyone help me with this issue? Should I reject this shapefile in the importing process? Is the shapefile normal? 回答1: If you enclose addr:city with quotes it should work: SELECT "addr:city" FROM

GeoServer Issues

阅读更多关于 GeoServer Issues

问题 While running the server, I am unable to view the layers in GeoServer. I checked the Enabled checkbox, and still I am unable to view the map. If I login once again into GeoServer, the Enabled checkbox is unchecked. The below error which I got in logs after starting the Apache Tomcat Server: Caused by: java.lang.RuntimeException: Unable to obtain connection: Cannot create PoolableConnectionFactory (FATAL: password authentication failed for user "postgres") Caused by: org.apache.commons.dbcp

Google Map Tile Provider (GeoServer And WMS)

阅读更多关于 Google Map Tile Provider (GeoServer And WMS)

问题 WMS Webservice GeoServer WMS I try to get Tile Information(I, J , BBOX) on selected Latitude and Longitude with zooming level in Google Map. I used this formula to get I, J , BBOX Formula Source private void getXYFromLatLon(double lat, double lon, final int zoom) { int tileSize = 256; // double initialResolution = 2 * Math.PI * 6378137 / tileSize; double initialResolution = 156543.03392804062; double originShift = 20037508.342789244; // LatLong to Meter double mx = lon * originShift / 180.0;