Yes, very good. That has solved that performance problem.
My projection is EPSG:27700 which is most definitely part of the official
EPSG database, so unsure if that fix has helped much.
Anyway, option added and all working fine.
Thanks for your help,
Toby
On 20 July 2016 at 15:17, Diego Nieto Cid <[email protected]> wrote:
> Hi
>
> El 20 jul 2016, a las 06:57, Tobias Reinicke <[email protected]>
> escribió:
>
> 4. A shapefile store and info_format application/json = ~ 3000ms !!!!!
>
>
> Yes I've seen that performance issue with a Shapefile in the Sinusoidal
> projection.
>
> I've found this related issue
>
> https://osgeo-org.atlassian.net/browse/GEOS-6923
>
> and, as one comment says, setting '-DGEOSERVER_GEOJSON_LEGACY_CRS=true'
> fixed the performance of JSON requests.
>
> The issue is marked as fixed so I'm not sure why it was happening. May
> it's something that must be fixed per projection.
>
> Hope this workaround helps you in the meanwhile.
>
> Cheers
>
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
