« Return to Thread: Changing featuretype datastore using REST
Re: Changing featuretype datastore using REST
by Justin Deoliveira-6
::
Rate this Message:
Ok, my apologies, I did not know that this was a feature, makes sense
though with our current model for configuration.
That said, I don't believe the REST api will complain if you add
multiple feature types to a single datastore. So should work, if not let
us know.
-Justin
ajayr wrote:
> Yeah just as Andrea pointed out, we are using it as a single datastore for
> multiple layers that we display, where each layer is shown differently based
> on the style.
>
> Though I am not sure if it is a good "REST practise", but unfortunately I
> have to implement it that way (due to project requirements).
>
> Thanks for all the help
>
> Ajay
>
>
> Andrea Aime-4 wrote:
>> Justin Deoliveira ha scritto:
>>> Hi Ajay,
>>>
>>> Well in general multiple feature types for a shapefile datastore does
>>> not make much sense. Although you are right, the UI does allow you to
>>> create a second feature type for a shapefile ds, it seems to mostly
>>> override the first though. I would call this a bug.
>> Nope, it's a feature (a sponsored one, too, it was added
>> along with the ability to set an alias for a layer).
>> The reasoning is to allow a service to publish the same layer
>> multiple times with different setups:
>> - different default style
>> - different "reproject to" projection
>>
>> In particular the second was required so that WFS 1.0 clients
>> (ESRI Arc*) could access the data reprojected in various
>> ways without knowing anything about WFS 1.1
>>
>> Cheers
>> Andrea
>>
>> --
>> Andrea Aime
>> OpenGeo - http://opengeo.org
>> Expert service straight from the developers.
>>
>> ------------------------------------------------------------------------------
>> Enter the BlackBerry Developer Challenge
>> This is your chance to win up to $100,000 in prizes! For a limited time,
>> vendors submitting new applications to BlackBerry App World(TM) will have
>> the opportunity to enter the BlackBerry Developer Challenge. See full
>> prize
>> details at: http://p.sf.net/sfu/Challenge
>> _______________________________________________
>> Geoserver-users mailing list
>> Geoserver-users@...
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>>
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Geoserver-users mailing list
Geoserver-users@...
https://lists.sourceforge.net/lists/listinfo/geoserver-users
though with our current model for configuration.
That said, I don't believe the REST api will complain if you add
multiple feature types to a single datastore. So should work, if not let
us know.
-Justin
ajayr wrote:
> Yeah just as Andrea pointed out, we are using it as a single datastore for
> multiple layers that we display, where each layer is shown differently based
> on the style.
>
> Though I am not sure if it is a good "REST practise", but unfortunately I
> have to implement it that way (due to project requirements).
>
> Thanks for all the help
>
> Ajay
>
>
> Andrea Aime-4 wrote:
>> Justin Deoliveira ha scritto:
>>> Hi Ajay,
>>>
>>> Well in general multiple feature types for a shapefile datastore does
>>> not make much sense. Although you are right, the UI does allow you to
>>> create a second feature type for a shapefile ds, it seems to mostly
>>> override the first though. I would call this a bug.
>> Nope, it's a feature (a sponsored one, too, it was added
>> along with the ability to set an alias for a layer).
>> The reasoning is to allow a service to publish the same layer
>> multiple times with different setups:
>> - different default style
>> - different "reproject to" projection
>>
>> In particular the second was required so that WFS 1.0 clients
>> (ESRI Arc*) could access the data reprojected in various
>> ways without knowing anything about WFS 1.1
>>
>> Cheers
>> Andrea
>>
>> --
>> Andrea Aime
>> OpenGeo - http://opengeo.org
>> Expert service straight from the developers.
>>
>> ------------------------------------------------------------------------------
>> Enter the BlackBerry Developer Challenge
>> This is your chance to win up to $100,000 in prizes! For a limited time,
>> vendors submitting new applications to BlackBerry App World(TM) will have
>> the opportunity to enter the BlackBerry Developer Challenge. See full
>> prize
>> details at: http://p.sf.net/sfu/Challenge
>> _______________________________________________
>> Geoserver-users mailing list
>> Geoserver-users@...
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>>
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Geoserver-users mailing list
Geoserver-users@...
https://lists.sourceforge.net/lists/listinfo/geoserver-users
« Return to Thread: Changing featuretype datastore using REST
| Free embeddable forum powered by Nabble | Forum Help |
