Hi List,
Just a curiousity - why are.
true
false
Both declared in both the featuretype.xml file and the layer.xml file for each layer? Shouldn’t it just be declared in one fo them? Changing the featureType advertised did nothing which left me scratching my head for a while.
Thanks,
Jonathan
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.
Hello Jonathan,
I’m scratching my head. How did you get advertised to change? I’m trying to do this via Rest API.
Thanks,
Roger
···
On Mon, Oct 7, 2013 at 12:41 PM, Jonathan Moules <jonathanmoules@anonymised.com> wrote:
Hi List,
Just a curiousity - why are.
true
false
Both declared in both the featuretype.xml file and the layer.xml file for each layer? Shouldn’t it just be declared in one fo them? Changing the featureType advertised did nothing which left me scratching my head for a while.
Thanks,
Jonathan
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.
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Hi Roger,
I’m using the web-interface. I’m afraid I’m not sure about doing it through the REST API.
Alternately you can also alter the XML files yourself manually.
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.
···
Cheers,
Jonathan
On 31 January 2014 21:07, Roger Bedell <sylvanascent@anonymised.com> wrote:
Hello Jonathan,
I’m scratching my head. How did you get advertised to change? I’m trying to do this via Rest API.
Thanks,
Roger
On Mon, Oct 7, 2013 at 12:41 PM, Jonathan Moules <jonathanmoules@anonymised.com> wrote:
Hi List,
Just a curiousity - why are.
true
false
Both declared in both the featuretype.xml file and the layer.xml file for each layer? Shouldn’t it just be declared in one fo them? Changing the featureType advertised did nothing which left me scratching my head for a while.
Thanks,
Jonathan
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.
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Thanks Jonathan.
Anyone else care to comment how to change the “advertised” for a layer via the REST API?
Thanks!
Roger
···
On Mon, Feb 3, 2014 at 6:25 PM, Jonathan Moules <jonathanmoules@anonymised.com> wrote:
Hi Roger,
I’m using the web-interface. I’m afraid I’m not sure about doing it through the REST API.
Alternately you can also alter the XML files yourself manually.
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.
Cheers,
Jonathan
On 31 January 2014 21:07, Roger Bedell <sylvanascent@anonymised.com> wrote:
Hello Jonathan,
I’m scratching my head. How did you get advertised to change? I’m trying to do this via Rest API.
Thanks,
Roger
On Mon, Oct 7, 2013 at 12:41 PM, Jonathan Moules <jonathanmoules@anonymised.com> wrote:
Hi List,
Just a curiousity - why are.
true
false
Both declared in both the featuretype.xml file and the layer.xml file for each layer? Shouldn’t it just be declared in one fo them? Changing the featureType advertised did nothing which left me scratching my head for a while.
Thanks,
Jonathan
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.
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Hi Roger,
I believe this can be done via a PUT request with the layer or featureType description (depending on what you want to change).
I only changed this way, but the description is something like:
featureTypeName
nativeName
true|false
[...]
You should choose between true or false, and change name and nativeName to the defined in your featureType.
To change advertised, only add: true (or false)
I don’t know if it is necessary to put the whole featureType description (I’m putting the whole description).
Regards,
···
Rodrigo C. Antonialli
Rio Claro - SP - Brasil
LinkedIn: http://www.linkedin.com/in/rcantonialli
Contato: (19) 98136-2347
rcantonialli@anonymised.com
Skype: rc_antonialli
On Tue, Feb 4, 2014 at 11:53 AM, Roger Bedell <sylvanascent@anonymised.com> wrote:
Thanks Jonathan.
Anyone else care to comment how to change the “advertised” for a layer via the REST API?
Thanks!
Roger
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
On Mon, Feb 3, 2014 at 6:25 PM, Jonathan Moules <jonathanmoules@anonymised.com> wrote:
Hi Roger,
I’m using the web-interface. I’m afraid I’m not sure about doing it through the REST API.
Alternately you can also alter the XML files yourself manually.
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.
Cheers,
Jonathan
On 31 January 2014 21:07, Roger Bedell <sylvanascent@anonymised.com> wrote:
Hello Jonathan,
I’m scratching my head. How did you get advertised to change? I’m trying to do this via Rest API.
Thanks,
Roger
On Mon, Oct 7, 2013 at 12:41 PM, Jonathan Moules <jonathanmoules@anonymised.com> wrote:
Hi List,
Just a curiousity - why are.
true
false
Both declared in both the featuretype.xml file and the layer.xml file for each layer? Shouldn’t it just be declared in one fo them? Changing the featureType advertised did nothing which left me scratching my head for a while.
Thanks,
Jonathan
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.
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Many thanks Rodrigo,
Indeed, you have to PUT to the featureType, not the layer. And you just have to set the single attribute. For some reason I also had to set the enabled, otherwise it gets set to false.
URL: “http://” & GSServer & “/geoserver/rest/workspaces/ogi_user/datastores/” & DSName & “/featuretypes/” & LayerName,
Payload: “falsetrue”
Roger
···
On Tue, Feb 4, 2014 at 3:07 PM, Rodrigo Antonialli <rcantonialli@anonymised.com> wrote:
Hi Roger,
I believe this can be done via a PUT request with the layer or featureType description (depending on what you want to change).
I only changed this way, but the description is something like:
featureTypeName
nativeName
true|false
[...]
You should choose between true or false, and change name and nativeName to the defined in your featureType.
To change advertised, only add: true (or false)
I don’t know if it is necessary to put the whole featureType description (I’m putting the whole description).
Regards,
Rodrigo C. Antonialli
Rio Claro - SP - Brasil
LinkedIn: http://www.linkedin.com/in/rcantonialli
Contato: (19) 98136-2347
rcantonialli@anonymised.com
Skype: rc_antonialli
On Tue, Feb 4, 2014 at 11:53 AM, Roger Bedell <sylvanascent@anonymised.com> wrote:
Thanks Jonathan.
Anyone else care to comment how to change the “advertised” for a layer via the REST API?
Thanks!
Roger
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
On Mon, Feb 3, 2014 at 6:25 PM, Jonathan Moules <jonathanmoules@anonymised.com> wrote:
Hi Roger,
I’m using the web-interface. I’m afraid I’m not sure about doing it through the REST API.
Alternately you can also alter the XML files yourself manually.
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.
Cheers,
Jonathan
On 31 January 2014 21:07, Roger Bedell <sylvanascent@anonymised.com> wrote:
Hello Jonathan,
I’m scratching my head. How did you get advertised to change? I’m trying to do this via Rest API.
Thanks,
Roger
On Mon, Oct 7, 2013 at 12:41 PM, Jonathan Moules <jonathanmoules@anonymised.com> wrote:
Hi List,
Just a curiousity - why are.
true
false
Both declared in both the featuretype.xml file and the layer.xml file for each layer? Shouldn’t it just be declared in one fo them? Changing the featureType advertised did nothing which left me scratching my head for a while.
Thanks,
Jonathan
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.
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users