[Geoserver-devel] Patch incoming for arcs support

Hi,

I have one last minute patch needed to control linearization of arcs in GeoServer.

Basically, the layer page will have a new configurable entry for curve linearization,
that will parse into a geotools Measure object.

The reason for Measure is that normally even if you have data in geographic coordinates,
you want to control the linearization accuracy in meters or feet, so the editor will allow

both raw numbers (and will use the layer native unit of measure) or something like

3m, 5ft

Internally the code will translate it to the native UOM, using the OGC (in)famous

“meters per deegree” coefficient in case the data is geographic (which is rough yes,

we can maybe make it better later by using an average value in the layer bbox
later, right now it’s not a big problem either since you cannot do curves in geodetic

coordinates in Oracle, which is the only data source supporting curves besides the
property data store)

I hope to make a pull request today, at worst tomorrow

Cheers
Andrea

==

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.

==

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it


Sounds good Andrea, and if needed I don’t mind waiting a few days in order to test this last minuet integration party.

···

Jody Garnett

On Wed, Jul 16, 2014 at 12:37 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:

Hi,

I have one last minute patch needed to control linearization of arcs in GeoServer.

Basically, the layer page will have a new configurable entry for curve linearization,
that will parse into a geotools Measure object.

The reason for Measure is that normally even if you have data in geographic coordinates,
you want to control the linearization accuracy in meters or feet, so the editor will allow

both raw numbers (and will use the layer native unit of measure) or something like

3m, 5ft

Internally the code will translate it to the native UOM, using the OGC (in)famous

“meters per deegree” coefficient in case the data is geographic (which is rough yes,

we can maybe make it better later by using an average value in the layer bbox
later, right now it’s not a big problem either since you cannot do curves in geodetic

coordinates in Oracle, which is the only data source supporting curves besides the
property data store)

I hope to make a pull request today, at worst tomorrow

Cheers
Andrea

==

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.

==

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it



Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world’s largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds


Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel