Today I learnt that you can see the contents of an app in a Mac's Applications directory via Terminal: $ ls /Applications/GeoServer.app The file holding the GeoServer port number is Contents/Java/start.ini, so it's possible to edit this in admin mode using sudo vi start.ini. Search for the jetty.port section, edit the port number, save the file, and start GeoServer normally. GeoServer is then available at the specified port number (eg ). It may be a little unstable - for example I noticed that the Start/Shutdown options are both unavailable, and the status text always reads 'GeoServer is starting'.

1. Version History For Geoserver For Mac Download

But this is good enough for my testing purposes.

You can subscribe to this list. Attachments: I am running Version 2.8.3 of Geoserver on a Mac I added the Image Pyramid plugin and followed the 'Building and using an image pyramid' guide at. I can get the Blue Marble example to work fine. When I generate my own merged tiles I am able to create the the ImagePyramid store with out a problem.

Attachments: I am applying different styles in GeoServer for specific products like NDVI, RGB, etc. I usually refers to documentation and in this case I found something that is not clear from my understanding. I am talking about ColorMap types in GeoServer, specifically the one below. Type='intervals' value means that each interval defined by two entries is rendered using the color of the first (lowest-value) entry.

No color interpolation is applied across the intervals. Using the example set of color map entries:. The result image is: image: Inline images 1 In my case, if I have the following interval: - 0.2 will give you '#530000' - -0.9 will give you '#530000' And - -1 will give you '#530000' It is only from -1.00001 that you will start to get '#003200' So the specified color applies only to values which are strictly smaller than the “quantity”. My question is if this match the documentation. Thank you, Alberto. Attachments: Hi Jeff, I used cURL command to change the InputTransparentColor for a specific coverage.

Curl -u $user:$pass -v -XPUT -H 'Content-type: text/xml' -d '.InputTransparentColor.000000.true' $ip:$port/geoserver/rest/workspaces/$workspacename/coveragestores/$coveragename/coverages/$coveragename.xml Let us know if works for you too. Best, Alberto On 28 April 2016 at 17:07, Jeff Diamond wrote: I would appreciate if anyone could help me to set the InputTransparentColor via the rest API. I have been using gsconfig.py to access the API but can’t seem to find a way to do this via that module. I’m new to REST API, so am struggling a bit with figuring out how to implement what is in the REST API documentation. Thanks in advanceJeff Diamond - Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR.

Get your free trial! Geoserver-users mailing list Geoserver-users@. So, looking at the GDALINFO output I suggest to retile internally the granules as square tiles (e.g.: 512x512). Somehow I did not send the proper Gdalinfo output. I am using the gdal-default internal tile size of 256x256.

I am now unable to reproduce this issue, and not sure what changed. I will keep an eye out for it. generally speaking, it is not advisable to have overviews with size lower than the internal tiling. You will force the server to do unuseful extra-work other than risk to introduce artifacts. Good tip, I did not know that. be sure that the browser page zoom level is 100% otherwise it may introduce unwanted lines in the middle at client side Also experimented with this to try and reproduce, but no luck. View this message in context: Sent from the GeoServer - User mailing list archive at Nabble.com.

Attachments: GeoServer does not usually shut itself down, Tomcat is running GeoServer so you may wish to check the tomcat logs. (Jetty logs if you are running the standalone geoserver which includes jetty) - Jody Garnett On 25 April 2016 at 12:30, eting123 wrote: Hi We are using Geoserver version 2.2.5.

Attachments: Hi Victor Thanks for your response. I installed JAI for performance. I am using only WFS and WMS- no images to serve. But number of users (400) is large and workspace contain 40 layers (though users have to turn on and less likely one person is using more than 10 layers.

Installing JAI and turning it on showed speed gain in testing phase But i am wondering if I should have gone JVM 64 bit route instead. Is there downside later for production? Not a Java expert! Thanks On Apr 28, 2016 5:26 AM, 'Kirk, Victor (GB)' wrote: If you need JAI your options on windows are as you say limited to the 32 bit JVM. If you want to make more memory available to the JVM then you will require the 64bit version. Without knowing more I suspect you have two options, move to 64 bit linux and JVM or cluster your geoserver instances on 32 bit JVM instance on the same machine and use a load balancer.From:. Deepti Puri mailto:deepti202jais@.Sent:.

27 April 2016 21:02.To:. geoserver-users@.Subject:. Geoserver-users Which JRE to install on production server Hi everyone Oracle has this JRE version for Server (64 bit) installation: But for installing geoserver as service in this link the screenshot recommends 32 bit To optimize the performance on production environment - which JRE should I choose to install? Or does this make any difference.

And also JAI are available only for 32 bit for Window. I wanted to apply these settings to optimize the performance as I have plenty of memory on my server. Please advise. Thanks. Attachments: Labels and tiles together is just an intractable problem. All the ways of dealing with it are going to be unsatisfactory in some way.

Labelling is already a hard problem. It not only requires considering the feature you are labelling, but all the labels of nearby features, which depend on those near them and so on. So potentially the label on only feature could depend on that on any OTHER feature. This also needs to be done across all layers that are being combined. So, one solution is to compute the labels for everything everywhere. This means looking at every single feature.

You could pre-computer all the labels for every zoom level and store them as another layer. This would be a lot of work and would need to be redone for any change, and wouldn't allow for dynamic queries.

Version History For Geoserver For Mac Download

Or you can chunk the map into sections and label within the sections. This is the way we do this by default. Using bigger chunks (metatiles) helps reduce the problem but doesn't fix it. This is the most generally applicable solution, Another solution is to cache tiles for everything except tiles, and then handle labels using non-tiled WMS requests over top.

This obviously looses some of the benefit of caching but can work depending on the use case. The lost option is to turn off label conflict resolution and lock down their placement (Say to the centroid). If labels don't care about nearby labels and will just draw over top of one another, then the problem of needing to know about all the other labels on the map goes away. You just need a big enough gutter to pull in labels that extend past their features. Kevin Michael Smith smithkm@. On Mon, Apr 25, 2016, at 06:13 AM, Jonathan Moules wrote: Hi TommasoI can't think of any 'ideal' solutions (others may have better suggestions), but below are a few ideas:.

I'm guessing you're using the PointPlacement labelling, which with the large metatiling you're using should hopefully ensure only one label in any given large area. You could use the (area) filter function to dynamically calculate the area of a polygon and use this in conjunction with the Priority labelling feature to make sure the largest features are labelled. You could create a few identical styles with different scale thresholds for given labels and then use a filter with the (area) function to decide which of the styles (and thus thresholds) any given feature should go in. There's also the SpaceAround vendor parameter - CheersJonathan - On Mon, 25 Apr 2016 07:38:32 +0100.tommaso. wrote - Hello, I'm trying to avoid duplicate labels with Geoserver/Geowebcache.

Using metatiling 14x14 and gutter=100 helps but does not eliminate ALL duplicates, so I tried the function Centroid(thegeom) in styling. This really eliminates all duplicate labels but has a big disadvantage: the labels of the polygons are shown in all zoom levelsregardless of the size of the polygon, also all labels of all polygons are shown always (this is obvious: using Centroid(thegeom) the geometries are not longer polygons but points). Using normal polygons labeling, the labels of small polygons are only shown after zooming in, when the label fit in the polygon. There is a workaround to avoid this side effect?

Or other tricks to avoid duplicate labels? Thanks, Tommaso - - Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! Geoserver-users mailing list Geoserver-users@.

- - Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial!

Geoserver-users mailing list Geoserver-users@. Attachments: Thanks Ian, this morning I tried using the element in my sld and that is working for me. With the element, you can specify a color for the “bottom” of the dataset, and another to specify a color for the “top” of the dataset. This is working because I choose '0' as the bottom and '300' for the top, so it is excluding my noData values which are something like -3.4e+38. I haven't tested it yet on a non-panchromatic raster. On Thu, Apr 28, 2016 at 10:36 AM, Ian Turton wrote: They are not implemented for 2.7.x (the give away is when you look in the 2,7 manual ) Ian On 28 April 2016 at 14:41, Thomas Gertin wrote: When I upload an raster with high nodata values, the way the raster is displayed makes it so the main area is white and the borders are black. Does anybody know how to fix this?

I am using Geoserver 2.7.4. I looked into the SLDs a little bit. Normalize or histogram is not fixing it. In the 2.8 Users manual for rastersymbolizer is more text that refer to supported algorithms such as.StretchToMinimumMaximum., this appears that it might work, but when I try to use it does not validate my sld. I am thinking these algorithms are not implemented in 2.7.x ThanksTom G - Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR.

Get your free trial! Geoserver-users mailing list Geoserver-users@. - Ian Turton. Attachments: They are not implemented for 2.7.x (the give away is when you look in the 2,7 manual ) Ian On 28 April 2016 at 14:41, Thomas Gertin wrote: When I upload an raster with high nodata values, the way the raster is displayed makes it so the main area is white and the borders are black. Does anybody know how to fix this? I am using Geoserver 2.7.4.

I looked into the SLDs a little bit. Normalize or histogram is not fixing it. In the 2.8 Users manual for rastersymbolizer is more text that refer to supported algorithms such as.StretchToMinimumMaximum., this appears that it might work, but when I try to use it does not validate my sld. I am thinking these algorithms are not implemented in 2.7.x ThanksTom G - Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! Geoserver-users mailing list Geoserver-users@.

- Ian Turton. Attachments: When I upload an raster with high nodata values, the way the raster is displayed makes it so the main area is white and the borders are black. Does anybody know how to fix this? I am using Geoserver 2.7.4.

I looked into the SLDs a little bit. Normalize or histogram is not fixing it. In the 2.8 Users manual for rastersymbolizer. Attachments: If you need JAI your options on windows are as you say limited to the 32 bit JVM. If you want to make more memory available to the JVM then you will require the 64bit version. Without knowing more I suspect you have two options, move to 64 bit linux and JVM or cluster your geoserver instances on 32 bit JVM instance on the same machine and use a load balancer.

From: Deepti Puri mailto:deepti202jais@. Sent: 27 April 2016 21:02 To: geoserver-users@. Subject: Geoserver-users Which JRE to install on production server Hi everyone Oracle has this JRE version for Server (64 bit) installation: But for installing geoserver as service in this link the screenshot recommends 32 bit To optimize the performance on production environment - which JRE should I choose to install? Or does this make any difference. And also JAI are available only for 32 bit for Window. I wanted to apply these settings to optimize the performance as I have plenty of memory on my server. Please advise.

Hi We are using Geoserver version 2.2.5. Hi, As an admin in GeoServer, click on 'Authentication' under 'Security' on the left-hand side. On the page which comes up, under Authentication filters, click the box next to 'remeberme' and then click 'Remove selected'. In terms of documentation, I'd recommend the particular section: and for more background: Cheers, Jim On 08:14 AM, treeflower wrote: Thanks for your answer. Where can I remove the 'Remember me' function?

Thanks in advance - View this message in context: Sent from the GeoServer - User mailing list archive at Nabble.com. - Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! Geoserver-users mailing list Geoserver-users@.

Attachments: Hi Tommaso, I can't think of any 'ideal' solutions (others may have better suggestions), but below are a few ideas:. I'm guessing you're using the PointPlacement labelling, which with the large metatiling you're using should hopefully ensure only one label in any given large area. You could use the (area) filter function to dynamically calculate the area of a polygon and use this in conjunction with the Priority labelling feature to make sure the largest features are labelled. You could create a few identical styles with different scale thresholds for given labels and then use a filter with the (area) function to decide which of the styles (and thus thresholds) any given feature should go in. There's also the SpaceAround vendor parameter - Cheers, Jonathan - On Mon, 25 Apr 2016 07:38:32 +0100 tommaso wrote - Hello, I'm trying to avoid duplicate labels with Geoserver/Geowebcache. Using metatiling 14x14 and gutter=100 helps but does not eliminate ALL duplicates, so I tried the function Centroid(thegeom) in styling.

This really eliminates all duplicate labels but has a big disadvantage: the labels of the polygons are shown in all zoom levels, regardless of the size of the polygon, also all labels of all polygons are shown always (this is obvious: using Centroid(thegeom) the geometries are not longer polygons but points). Using normal polygons labeling, the labels of small polygons are only shown after zooming in, when the label fit in the polygon. There is a workaround to avoid this side effect? Or other tricks to avoid duplicate labels? Thanks, Tommaso - Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR.

Get your free trial! Geoserver-users mailing list Geoserver-users@. Hello, I'm trying to avoid duplicate labels with Geoserver/Geowebcache. Using metatiling 14x14 and gutter=100 helps but does not eliminate ALL duplicates, so I tried the function Centroid(thegeom) in styling.

This really eliminates all duplicate labels but has a big disadvantage: the labels of the polygons are shown in all zoom levels, regardless of the size of the polygon, also all labels of all polygons are shown always (this is obvious: using Centroid(thegeom) the geometries are not longer polygons but points). Using normal polygons labeling, the labels of small polygons are only shown after zooming in, when the label fit in the polygon. There is a workaround to avoid this side effect?

Or other tricks to avoid duplicate labels? Thanks, Tommaso. Epyks23, the namespace URI is the XML namespace for types (layers) defined within a workspace: If you publish a layer globally, choose a namespace that is unique to you. For example, one that is an HTTP URI for a domain you own.

Note that I wrote URI, not URL: the namespace does not have to be resolvable as it is just an identifier (but it might be convenient if it is). Aim for a namespace URI that will never change. Namespaces allow types to be defined with the same name but with different definitions. For example, a government agency might have a type Tree and use it to publish information on who owns a tree and whether it is protected from felling: Namespace URI: Feature Type: Tree A biologist may define a Tree by its species and relationship to other living things around it: Namespace URI: Feature Type: Tree Using different namespaces allow both to publish their own Tree type with different properties without confusion.

Specialist communities agree on namespaces to enable interoperability. For example, GML 3.1, GML 3.2, and WFS 1.1, and WFS 2.0 each have their own namespaces. The workspace name is used as the default XML namespace prefix for that namespace; the prefix is just a short convenient alias.

Strict compliance to OGC Web Service standards requires each namespace prefix to be associated with its namespace URI in every request, but GeoServer lets you use a namespace prefix matching a workspace name without having to define it in a request. XML namespace prefixes are not unique across services and are local to XML instance documents. Kind regards, Ben.

On 25/04/16 04:26, epyks23 wrote: What is Namespace URI when creating a workspace? What is the purpose of them? Would this be correct to use: Is it different if I am hosting my layers globally? Does the URI have to be different? - View this message in context: Sent from the GeoServer - User mailing list archive at Nabble.com. - Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR.

Get your free trial! Geoserver-users mailing list Geoserver-users@. - Ben Caradoc-Davies Director Transient Software Limited.