Hi Graham, thanks the encoding added the + but it still returns an error
'Invalid graphic format: image/svg+xml'
On Thu, Mar 14, 2019 at 12:12 PM Humphries, Graham (StateGrowth) <
graham.humphr...@stategrowth.tas.gov.au> wrote:
> I think you will need to encode the URL as most browsers will
I think you will need to encode the URL as most browsers will treat a + as a
space
From: Chris Brown [mailto:chrisinca...@gmail.com]
Sent: Thursday, 14 March 2019 3:47 PM
To: Humphries, Graham (StateGrowth)
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users]
No just entering it into a browser. Is GetLegendGraphic as SVG working for
you? If so which version are you using?
On Thu, Mar 14, 2019 at 11:43 AM Humphries, Graham (StateGrowth) <
graham.humphr...@stategrowth.tas.gov.au> wrote:
> Are you encoding the URL?
>
>
>
> *From:* Chris Brown
Are you encoding the URL?
From: Chris Brown [mailto:chrisinca...@gmail.com]
Sent: Thursday, 14 March 2019 3:20 PM
To: Humphries, Graham (StateGrowth)
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] GetLegendGraphic as SVG
Hi Graham, thanks for you input, I just tried
Try the format as this:
image/svg+xml
-Original Message-
From: ChrisInCambo [mailto:chrisinca...@gmail.com]
Sent: Thursday, 14 March 2019 2:38 PM
To: geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] GetLegendGraphic as SVG
In the GeoServer docs is says that for
Please do not repost messages, the one you sent yesterday reached the list
fine.
As you say support is volunteer, which often also implies less than stellar
response times.
The mbtiles module is a community one, hence not part of the official
releases, and unsupported.
As far as I know, the
Hi everyone,
I have been researching this issue for some time off an on, and have not been
able to find a solution. I thought perhaps mentioning the issue here might help
shed some light on what I’m doing wrong. :)
I have created a MBTiles package (using MapTiler Desktop), and the import
On Wed, Mar 13, 2019 at 1:30 AM Matt Hakim wrote:
> Hi,
> In the GML WFS response the boundedBy element is null unless the 'Return
> bounding box with every feature' check box is ticked in the web console.
> We require the bounding box for the feature geometry (but not the geometry
> itself).
>
On 3/13/19 1:23 AM, Matt Hakim wrote:
Hi,
In the GML WFS response the boundedBy element is null unless the
'Return bounding box with every feature' check box is ticked in the
web console.
We require the bounding box for the feature geometry (but not the
geometry itself).
I would look into
