[Geoserver-users] Recognizing the 'Native SRS' issue. ( gdalinfo vs geoserver )

GeoServer GeoServer User
1

When i check the SRS using ‘gdalinfo’ the WKT have all informations but when i submit a raster to geoserver some fields values are “unknown”?
How can i config my server to recognizes all the SRS that gdal does. Someone have a clue or a tutorial to help?

Thanks

2

Hi Danilo,
What SRS are we talking about here? Geoserver has nearly 5,000 built in.
If you go to the demos → SRS List page, you’ll see the full list.

There’s also some stuff about customer CRS’s here:
http://docs.geoserver.org/stable/en/user/advanced/crshandling/customcrs.html?highlight=projection

Jonathan

On 22 August 2013 14:38, Danilo da Silveira Figueira <danilomalzao@anonymised.com> wrote:

When i check the SRS using ‘gdalinfo’ the WKT have all informations but when i submit a raster to geoserver some fields values are “unknown”?
How can i config my server to recognizes all the SRS that gdal does. Someone have a clue or a tutorial to help?

Thanks

Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk

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

This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.

3

On Thu, Aug 22, 2013 at 3:38 PM, Danilo da Silveira Figueira <
danilomalzao@anonymised.com> wrote:

When i check the SRS using 'gdalinfo' the WKT have all informations but
when i submit a raster to geoserver some fields values are "unknown"?

A WKT does not make a EPSG code automatically. It may be that the data in
question has a user made CRS
instead of an official EPSG code, in that case, you get uknown

How can i config my server to recognizes all the SRS that gdal does.
Someone have a clue or a tutorial to help?

Does not work like that, OGC codes need an official EPSG code, not a WKT

Cheers
Andrea

--

Our support, Your Success! Visit http://opensdi.geo-solutions.it 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

-------------------------------------------------------

4

I guess that the problem is the difference in the WKT output because gdal recognizes this SRS as EPSG:9001 but geoserver doesn´t. And i cant create a EPSG code for a unrecognized projection.

The both generated WKT are below.

For instance :

gdalinfo:

Full Projection (WKT) : PROJCS[“SAD_1969_Albers”,
GEOGCS[“GCS_South_American_1969”,
DATUM[“South_American_Datum_1969”,
SPHEROID[“GRS_1967”,6378160,298.249999999996,
AUTHORITY[“EPSG”,“7036”]],
AUTHORITY[“EPSG”,“6291”]],
PRIMEM[“Greenwich”,0],
UNIT[“degree”,0.0174532925199433]],
PROJECTION[“Albers_Conic_Equal_Area”],
PARAMETER[“standard_parallel_1”,-5],
PARAMETER[“standard_parallel_2”,-42],
PARAMETER[“latitude_of_center”,-32],
PARAMETER[“longitude_of_center”,-51],
PARAMETER[“false_easting”,0],
PARAMETER[“false_northing”,0],
UNIT[“metre”,1,
AUTHORITY[“EPSG”,“9001”]]]

Geoserver:

PROJCS[“unnamed”,
GEOGCS[“GCS Name = GCS_South_American_1969”,
DATUM[“South American Datum 1969”,
SPHEROID[“GRS 1967”, 6378160.0, 298.247167427, AUTHORITY[“EPSG”,“7036”]],
TOWGS84[-57.0, 1.0, -41.0, 0.0, 0.0, 0.0, 0.0],
AUTHORITY[“EPSG”,“6291”]],
PRIMEM[“Greenwich”, 0.0, AUTHORITY[“EPSG”,“8901”]],
UNIT[“degree”, 0.017453292519943295],
AXIS[“Geodetic longitude”, EAST],
AXIS[“Geodetic latitude”, NORTH]],
PROJECTION[“Albers_Conic_Equal_Area”],
PARAMETER[“central_meridian”, -51.0],
PARAMETER[“latitude_of_origin”, -32.0],
PARAMETER[“standard_parallel_1”, -5.0],
PARAMETER[“false_easting”, 0.0],
PARAMETER[“false_northing”, 0.0],
PARAMETER[“standard_parallel_2”, -42.0],
UNIT[“m”, 1.0],
AXIS[“Easting”, EAST],
AXIS[“Northing”, NORTH]]

···

2013/8/22 Jonathan Moules <jonathanmoules@anonymised.com>

Hi Danilo,
What SRS are we talking about here? Geoserver has nearly 5,000 built in.
If you go to the demos → SRS List page, you’ll see the full list.

There’s also some stuff about customer CRS’s here:
http://docs.geoserver.org/stable/en/user/advanced/crshandling/customcrs.html?highlight=projection

Jonathan

On 22 August 2013 14:38, Danilo da Silveira Figueira <danilomalzao@anonymised.com> wrote:

When i check the SRS using ‘gdalinfo’ the WKT have all informations but when i submit a raster to geoserver some fields values are “unknown”?
How can i config my server to recognizes all the SRS that gdal does. Someone have a clue or a tutorial to help?

Thanks

Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk

Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.

5

Hi,

EPSG:9001 is not SRS, it is unit (metre)

http://www.epsg-registry.org/report.htm?type=selection&entity=urn:ogc:def:uom:EPSG::9001&reportDetail=short&style=urn:uuid:report-style:default-with-code&style_name=OGP%20Default%20With%20Code&title=EPSG:9001

-Jukka Rahkonen-

________________________________
Danilo da Silveira Figueira wrote:

I guess that the problem is the difference in the WKT output because gdal recognizes this SRS as EPSG:9001 but geoserver doesn´t. And i cant create a EPSG code for a unrecognized projection.

The both generated WKT are below.

For instance :

gdalinfo:

Full Projection (WKT) : PROJCS["SAD_1969_Albers",
    GEOGCS["GCS_South_American_1969",
        DATUM["South_American_Datum_1969",
            SPHEROID["GRS_1967",6378160,298.249999999996,
                AUTHORITY["EPSG","7036"]],
            AUTHORITY["EPSG","6291"]],
        PRIMEM["Greenwich",0],
        UNIT["degree",0.0174532925199433]],
    PROJECTION["Albers_Conic_Equal_Area"],
    PARAMETER["standard_parallel_1",-5],
    PARAMETER["standard_parallel_2",-42],
    PARAMETER["latitude_of_center",-32],
    PARAMETER["longitude_of_center",-51],
    PARAMETER["false_easting",0],
    PARAMETER["false_northing",0],
    UNIT["metre",1,
        AUTHORITY["EPSG","9001"]]]

Geoserver:

PROJCS["unnamed",
  GEOGCS["GCS Name = GCS_South_American_1969",
    DATUM["South American Datum 1969",
      SPHEROID["GRS 1967", 6378160.0, 298.247167427, AUTHORITY["EPSG","7036"]],
      TOWGS84[-57.0, 1.0, -41.0, 0.0, 0.0, 0.0, 0.0],
      AUTHORITY["EPSG","6291"]],
    PRIMEM["Greenwich", 0.0, AUTHORITY["EPSG","8901"]],
    UNIT["degree", 0.017453292519943295],
    AXIS["Geodetic longitude", EAST],
    AXIS["Geodetic latitude", NORTH]],
  PROJECTION["Albers_Conic_Equal_Area"],
  PARAMETER["central_meridian", -51.0],
  PARAMETER["latitude_of_origin", -32.0],
  PARAMETER["standard_parallel_1", -5.0],
  PARAMETER["false_easting", 0.0],
  PARAMETER["false_northing", 0.0],
  PARAMETER["standard_parallel_2", -42.0],
  UNIT["m", 1.0],
  AXIS["Easting", EAST],
  AXIS["Northing", NORTH]]

2013/8/22 Jonathan Moules <jonathanmoules@anonymised.com<mailto:jonathanmoules@…4942…>>
Hi Danilo,
What SRS are we talking about here? Geoserver has nearly 5,000 built in.
If you go to the demos -> SRS List page, you'll see the full list.

There's also some stuff about customer CRS's here:
http://docs.geoserver.org/stable/en/user/advanced/crshandling/customcrs.html?highlight=projection

Jonathan

On 22 August 2013 14:38, Danilo da Silveira Figueira <danilomalzao@anonymised.com<mailto:danilomalzao@anonymised.com>> wrote:
When i check the SRS using 'gdalinfo' the WKT have all informations but when i submit a raster to geoserver some fields values are "unknown"?
How can i config my server to recognizes all the SRS that gdal does. Someone have a clue or a tutorial to help?

Thanks

------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net<mailto:Geoserver-users@anonymised.comrge.net>
https://lists.sourceforge.net/lists/listinfo/geoserver-users

This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.

6

So, the problem is not about the EPSG:9001, but i still can’t figure out why the projection is ‘unnamed’ in the geoserver:
gdal: PROJCS[“SAD_1969_Albers”,
geoserver: PROJCS[“unnamed”,

And i need equal WKT code to define a custom EPSG associated with this SRS.

7

Hi,

I have never done anything like this, but because this is not a standard EPSG projection then you must use the WKT and create your own custom projection somehow like in these documents

http://docs.geoserver.org/latest/en/user/advanced/crshandling/customcrs.html
http://spatialreference.org/ref/sr-org/north-pacific-albers-conic-equal-area/geoserver/

-Jukka Rahkonen-

________________________________
Lähettäjä: danilosfigueira@anonymised.com [danilosfigueira@anonymised.com] käyttäjän Danilo da Silveira Figueira [danilomalzao@anonymised.com] puolesta
Lähetetty: 22. elokuuta 2013 19:35
Vastaanottaja: Rahkonen Jukka
Cc: geoserver-users
Aihe: Re: [Geoserver-users] Recognizing the 'Native SRS' issue. ( gdalinfo vs geoserver )

So, the problem is not about the EPSG:9001, but i still can't figure out why the projection is 'unnamed' in the geoserver:
gdal: PROJCS["SAD_1969_Albers",
geoserver: PROJCS["unnamed",

And i need equal WKT code to define a custom EPSG associated with this SRS.

8

I already defined this in my ‘epsg.properties’ and i am able to use the “Declared SRS” field to specify my custom SRS code, but i need to make my code be a “Native SRS”.

···

2013/8/22 Rahkonen Jukka <jukka.rahkonen@anonymised.com>

Hi,

I have never done anything like this, but because this is not a standard EPSG projection then you must use the WKT and create your own custom projection somehow like in these documents

http://docs.geoserver.org/latest/en/user/advanced/crshandling/customcrs.html
http://spatialreference.org/ref/sr-org/north-pacific-albers-conic-equal-area/geoserver/

-Jukka Rahkonen-

Lähettäjä: danilosfigueira@anonymised.com [danilosfigueira@anonymised.com] käyttäjän Danilo da Silveira Figueira [danilomalzao@anonymised.com] puolesta
Lähetetty: 22. elokuuta 2013 19:35
Vastaanottaja: Rahkonen Jukka
Cc: geoserver-users
Aihe: Re: [Geoserver-users] Recognizing the ‘Native SRS’ issue. ( gdalinfo vs geoserver )

So, the problem is not about the EPSG:9001, but i still can’t figure out why the projection is ‘unnamed’ in the geoserver:
gdal: PROJCS[“SAD_1969_Albers”,
geoserver: PROJCS[“unnamed”,

And i need equal WKT code to define a custom EPSG associated with this SRS.

Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk

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

9

I don't understand this sentence "but i need to make my code be a "Native SRS"".
Generally speaking you don't need to do that:

-1- if you want to override the native CRS you oviously don't need to do that
-2- if you want to reproject from the native CRS you only need
GeoServer to parse correctly the native CRS and then find a suitable
EPSG code or define your own.

Since you said you have defined your own EPSG already, I don't
understand where the problem is.

Regards,
Simone Giannecchini

Our support, Your Success! Visit http://opensdi.geo-solutions.it for
more information.

Ing. Simone Giannecchini
@simogeo
Founder/Director

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

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

-------------------------------------------------------

On Thu, Aug 22, 2013 at 7:44 PM, Danilo da Silveira Figueira
<danilomalzao@anonymised.com> wrote:

I already defined this in my 'epsg.properties' and i am able to use the
"Declared SRS" field to specify my custom SRS code, but i need to make my
code be a "Native SRS".

2013/8/22 Rahkonen Jukka <jukka.rahkonen@anonymised.com>

Hi,

I have never done anything like this, but because this is not a standard
EPSG projection then you must use the WKT and create your own custom
projection somehow like in these documents

http://docs.geoserver.org/latest/en/user/advanced/crshandling/customcrs.html

http://spatialreference.org/ref/sr-org/north-pacific-albers-conic-equal-area/geoserver/

-Jukka Rahkonen-

________________________________
Lähettäjä: danilosfigueira@anonymised.com [danilosfigueira@anonymised.com] käyttäjän
Danilo da Silveira Figueira [danilomalzao@anonymised.com] puolesta
Lähetetty: 22. elokuuta 2013 19:35
Vastaanottaja: Rahkonen Jukka
Cc: geoserver-users
Aihe: Re: [Geoserver-users] Recognizing the 'Native SRS' issue. ( gdalinfo
vs geoserver )

So, the problem is not about the EPSG:9001, but i still can't figure out
why the projection is 'unnamed' in the geoserver:
gdal: PROJCS["SAD_1969_Albers",
geoserver: PROJCS["unnamed",

And i need equal WKT code to define a custom EPSG associated with this
SRS.

------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!

http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

10

My problem is that even after defining a custom CRS, this rule is not automatically applyed to a new layer and the geoserver still recognizing as an “UNKNOWN” Native SRS. I can use a custom SRS in the declared field, but to fill this field the publisher have to know my custom EPSG number.

There is any way to make the system fill automatically one these fields (‘Native SRS’/'‘Declared SRS’) with my custom EPSG based on the WKT CRS?

Thanks.

11

Ciao Danilo,
the native one is the one that is advertised by the underlying source,
as such it what it is you can only override or reproject it
afterwards.
I mean the mechanism you are using has been put in place just because
the underlying source has a strange or incorrect or without a valid
EPSG code CRS.
Regards,
Simone Giannecchini

Our support, Your Success! Visit http://opensdi.geo-solutions.it for
more information.

Ing. Simone Giannecchini
@simogeo
Founder/Director

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

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

-------------------------------------------------------

On Fri, Aug 30, 2013 at 7:43 PM, Danilo da Silveira Figueira
<danilomalzao@anonymised.com> wrote:

My problem is that even after defining a custom CRS, this rule is not
automatically applyed to a new layer and the geoserver still recognizing as
an "UNKNOWN" Native SRS. I can use a custom SRS in the declared field, but
to fill this field the publisher have to know my custom EPSG number.

There is any way to make the system fill automatically one these fields
('Native SRS'/''Declared SRS') with my custom EPSG based on the WKT CRS?

Thanks.

12

Hi again,

Ok then, i got it now ( the field ‘Native SRS’ must be UNKOWN because there is no one oficial SRS that match the projection information ).
But there is a way to automatically fill the ‘Declared SRS’ using my custom defined EPSG codes?

···

2013/8/30 Simone Giannecchini <simone.giannecchini@anonymised.com>

Ciao Danilo,
the native one is the one that is advertised by the underlying source,
as such it what it is you can only override or reproject it
afterwards.
I mean the mechanism you are using has been put in place just because
the underlying source has a strange or incorrect or without a valid
EPSG code CRS.

Regards,
Simone Giannecchini

Our support, Your Success! Visit http://opensdi.geo-solutions.it for
more information.

Ing. Simone Giannecchini
@simogeo
Founder/Director

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

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

On Fri, Aug 30, 2013 at 7:43 PM, Danilo da Silveira Figueira
<danilomalzao@anonymised.com> wrote:

My problem is that even after defining a custom CRS, this rule is not
automatically applyed to a new layer and the geoserver still recognizing as
an “UNKNOWN” Native SRS. I can use a custom SRS in the declared field, but
to fill this field the publisher have to know my custom EPSG number.

There is any way to make the system fill automatically one these fields
(‘Native SRS’/'‘Declared SRS’) with my custom EPSG based on the WKT CRS?

Thanks.

13

You can do that by creating the layer via REST I believe.
Regards,
Simone Giannecchini

Our support, Your Success! Visit http://opensdi.geo-solutions.it for
more information.

Ing. Simone Giannecchini
@simogeo
Founder/Director

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

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

-------------------------------------------------------

On Fri, Aug 30, 2013 at 9:33 PM, Danilo da Silveira Figueira
<danilomalzao@anonymised.com> wrote:

Hi again,

Ok then, i got it now ( the field 'Native SRS' must be UNKOWN because there
is no one oficial SRS that match the projection information ).
But there is a way to automatically fill the 'Declared SRS' using my custom
defined EPSG codes?

2013/8/30 Simone Giannecchini <simone.giannecchini@anonymised.com>

Ciao Danilo,
the native one is the one that is advertised by the underlying source,
as such it what it is you can only override or reproject it
afterwards.
I mean the mechanism you are using has been put in place just because
the underlying source has a strange or incorrect or without a valid
EPSG code CRS.
Regards,
Simone Giannecchini

Our support, Your Success! Visit http://opensdi.geo-solutions.it for
more information.

Ing. Simone Giannecchini
@simogeo
Founder/Director

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

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

-------------------------------------------------------

On Fri, Aug 30, 2013 at 7:43 PM, Danilo da Silveira Figueira
<danilomalzao@anonymised.com> wrote:
> My problem is that even after defining a custom CRS, this rule is not
> automatically applyed to a new layer and the geoserver still recognizing
> as
> an "UNKNOWN" Native SRS. I can use a custom SRS in the declared field,
> but
> to fill this field the publisher have to know my custom EPSG number.
>
> There is any way to make the system fill automatically one these fields
> ('Native SRS'/''Declared SRS') with my custom EPSG based on the WKT CRS?
>
> Thanks.

14

Hi Simone,

Thanks for the tip, i guess that using REST API will solve everything that i need!

Thanks again!

···

2013/9/1 Simone Giannecchini <simone.giannecchini@anonymised.com>

You can do that by creating the layer via REST I believe.

Regards,
Simone Giannecchini

Our support, Your Success! Visit http://opensdi.geo-solutions.it for
more information.

Ing. Simone Giannecchini
@simogeo
Founder/Director

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

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

On Fri, Aug 30, 2013 at 9:33 PM, Danilo da Silveira Figueira

<danilomalzao@anonymised.com> wrote:

Hi again,

Ok then, i got it now ( the field ‘Native SRS’ must be UNKOWN because there
is no one oficial SRS that match the projection information ).
But there is a way to automatically fill the ‘Declared SRS’ using my custom
defined EPSG codes?

2013/8/30 Simone Giannecchini <simone.giannecchini@anonymised.com>

Ciao Danilo,
the native one is the one that is advertised by the underlying source,
as such it what it is you can only override or reproject it
afterwards.
I mean the mechanism you are using has been put in place just because
the underlying source has a strange or incorrect or without a valid
EPSG code CRS.
Regards,
Simone Giannecchini

Our support, Your Success! Visit http://opensdi.geo-solutions.it for
more information.

Ing. Simone Giannecchini
@simogeo
Founder/Director

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

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

On Fri, Aug 30, 2013 at 7:43 PM, Danilo da Silveira Figueira
<danilomalzao@anonymised.com> wrote:

My problem is that even after defining a custom CRS, this rule is not
automatically applyed to a new layer and the geoserver still recognizing
as
an “UNKNOWN” Native SRS. I can use a custom SRS in the declared field,
but
to fill this field the publisher have to know my custom EPSG number.

There is any way to make the system fill automatically one these fields
(‘Native SRS’/'‘Declared SRS’) with my custom EPSG based on the WKT CRS?

Thanks.