[Geoserver-users] isDynamic in info.xml

Hey there

A short question.
What is the function of the parameter isDynamic in info.xml?

Thank you.
Regards,
Thomas
--
View this message in context: http://www.nabble.com/isDynamic-in-info.xml-tf3154161.html#a8746284
Sent from the GeoServer - User mailing list archive at Nabble.com.

I'm not sure. I don't have that parameter in any of my info.xml files.
Does your file contain a custom schema, or anything out of the ordinary?

Is it causing issues for you or are you just curious as to what it is doing?

Brent Owens
(The Open Planning Project)

Zubi wrote:

Hey there

A short question. What is the function of the parameter isDynamic in info.xml?

Thank you.
Regards,
Thomas
  

Brent, thank you. That is correct, there are no isDynamic in this file. I
wrote it false and meant the parameter "dynamic". Sorry.

I try to analyze the info.xml file. What is the function of "dynamic" and
"numDecimals"?

Regards,
Thomas

<featureType datastore = "DS_tiger_roads" >
<name>tiger_roads</name>
<!--
native wich EPGS code for the FeatureTypeInfoDTO
-->
<SRS>4326</SRS>
<title>tiger_roads_Type</title>
<abstract>Generated from DS_tiger_roads</abstract>
<numDecimals value = "8" />
<keywords>tiger_roads DS_tiger_roads</keywords>
<latLonBoundingBox dynamic = "false" miny = "40.684221" maxy = "40.878178"
maxx = "-73.907005" minx = "-74.02722" />
<!--
the default style this FeatureTypeInfoDTO can be represented by.
at least must contain the "default" attribute
-->
<styles default = "tiger_roads" />
</featureType>
--
View this message in context: http://www.nabble.com/isDynamic-in-info.xml-tf3154161.html#a8753475
Sent from the GeoServer - User mailing list archive at Nabble.com.

Dynamic is no longer used at all. I didn't realize we still had it in the sample files. It was to auto-generate the bbox, but we realized it's better to do it with the 'generate' button.

numDecimals is just for the WFS. It's not necessary, as there is a global variable that sets it. And I'm not even sure that the featureType level successfully sets numDecimals. So basically don't worry about it, it shouldn't break anything.

Chris

Thomas Zuberbühler wrote:

Brent, thank you. That is correct, there are no isDynamic in this file. I
wrote it false and meant the parameter "dynamic". Sorry.

I try to analyze the info.xml file. What is the function of "dynamic" and
"numDecimals"?

Regards,
Thomas

<featureType datastore = "DS_tiger_roads" >
<name>tiger_roads</name>
<!--
native wich EPGS code for the FeatureTypeInfoDTO
-->
<SRS>4326</SRS>
<title>tiger_roads_Type</title>
<abstract>Generated from DS_tiger_roads</abstract>
<numDecimals value = "8" />
<keywords>tiger_roads DS_tiger_roads</keywords>
<latLonBoundingBox dynamic = "false" miny = "40.684221" maxy = "40.878178"
maxx = "-73.907005" minx = "-74.02722" />
<!--
the default style this FeatureTypeInfoDTO can be represented by.
at least must contain the "default" attribute -->
<styles default = "tiger_roads" />
</featureType>

--
Chris Holmes
The Open Planning Project
http://topp.openplans.org

ah,
The numDecimals value is the number of significant figures that the data set will use. So anything beyond 8 decimal places will be rounded off.

The 'dynamic' attribute for the bounding box has always been false in the files I have seen. I will look into the code and see where it is used, but I wouldn't worry about it for now.

Brent Owens
(The Open Planning Project)

Thomas Zuberbühler wrote:

Brent, thank you. That is correct, there are no isDynamic in this file. I
wrote it false and meant the parameter "dynamic". Sorry.

I try to analyze the info.xml file. What is the function of "dynamic" and
"numDecimals"?

Regards,
Thomas

<featureType datastore = "DS_tiger_roads" >
<name>tiger_roads</name>
<!--
native wich EPGS code for the FeatureTypeInfoDTO
-->
<SRS>4326</SRS>
<title>tiger_roads_Type</title>
<abstract>Generated from DS_tiger_roads</abstract>
<numDecimals value = "8" />
<keywords>tiger_roads DS_tiger_roads</keywords>
<latLonBoundingBox dynamic = "false" miny = "40.684221" maxy = "40.878178"
maxx = "-73.907005" minx = "-74.02722" />
<!--
the default style this FeatureTypeInfoDTO can be represented by.
at least must contain the "default" attribute -->
<styles default = "tiger_roads" />
</featureType>
  

Yeh I think Chris is right in that the numDecimals value in the feature type is not used, and a global value is used instead.

Chris, should we remove those attributes from the config to avoid confusion? It's a toss up of whether to do it now while we are thinking about it, or do it later when we re-do our config system.

Brent Owens
(The Open Planning Project)

Chris Holmes wrote:

Dynamic is no longer used at all. I didn't realize we still had it in the sample files. It was to auto-generate the bbox, but we realized it's better to do it with the 'generate' button.

numDecimals is just for the WFS. It's not necessary, as there is a global variable that sets it. And I'm not even sure that the featureType level successfully sets numDecimals. So basically don't worry about it, it shouldn't break anything.

Chris

Thomas Zuberbühler wrote:

Brent, thank you. That is correct, there are no isDynamic in this file. I
wrote it false and meant the parameter "dynamic". Sorry.
I try to analyze the info.xml file. What is the function of "dynamic" and
"numDecimals"?

Regards,
Thomas

<featureType datastore = "DS_tiger_roads" >
<name>tiger_roads</name>
<!--
native wich EPGS code for the FeatureTypeInfoDTO
-->
<SRS>4326</SRS>
<title>tiger_roads_Type</title>
<abstract>Generated from DS_tiger_roads</abstract>
<numDecimals value = "8" />
<keywords>tiger_roads DS_tiger_roads</keywords>
<latLonBoundingBox dynamic = "false" miny = "40.684221" maxy = "40.878178"
maxx = "-73.907005" minx = "-74.02722" />
<!--
the default style this FeatureTypeInfoDTO can be represented by.
at least must contain the "default" attribute -->
<styles default = "tiger_roads" />
</featureType>

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
------------------------------------------------------------------------

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

catching up on email

numDecimals were used to round off coordintates when encoding to xml (at least
on the SVG output). I'm sure once upon a time it was used for per feature
type rounding off on the WFS too. Guess WFS only uses a global value now?

anyhow, I think it's more valuable as a per feature type setting overriding
the global value?

Gabriel

On Thursday 01 February 2007 20:41, Brent Owens wrote:

ah,
The numDecimals value is the number of significant figures that the data
set will use. So anything beyond 8 decimal places will be rounded off.

The 'dynamic' attribute for the bounding box has always been false in
the files I have seen. I will look into the code and see where it is
used, but I wouldn't worry about it for now.

Brent Owens
(The Open Planning Project)

Thomas Zuberbühler wrote:
> Brent, thank you. That is correct, there are no isDynamic in this file. I
> wrote it false and meant the parameter "dynamic". Sorry.
>
> I try to analyze the info.xml file. What is the function of "dynamic" and
> "numDecimals"?
>
> Regards,
> Thomas
>
> <featureType datastore = "DS_tiger_roads" >
> <name>tiger_roads</name>
> <!--
> native wich EPGS code for the FeatureTypeInfoDTO
> -->
> <SRS>4326</SRS>
> <title>tiger_roads_Type</title>
> <abstract>Generated from DS_tiger_roads</abstract>
> <numDecimals value = "8" />
> <keywords>tiger_roads DS_tiger_roads</keywords>
> <latLonBoundingBox dynamic = "false" miny = "40.684221" maxy =
> "40.878178" maxx = "-73.907005" minx = "-74.02722" />
> <!--
> the default style this FeatureTypeInfoDTO can be represented by.
> at least must contain the "default" attribute
> -->
> <styles default = "tiger_roads" />
> </featureType>

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Gabriel Roldán (groldan@anonymised.com)
Axios Engineering (http://www.axios.es)
Tel. +34 944 41 63 84
Fax. +34 944 41 64 90

Thank you to all of you for your great help!

I think I set default values to this parameters. There can be a xml schema
(for info.xml) useful, can't it?

Regards,
Thomas

--
View this message in context: http://www.nabble.com/isDynamic-in-info.xml-tf3154161.html#a8763924
Sent from the GeoServer - User mailing list archive at Nabble.com.

I agree it should probably be assigned to each individual feature type. We will have to include it in the UI if we are going to use in instead of the global value however. Except it isn't even in the UI...

I will open a jira task to re-visit this for 1.6

Brent Owens
(The Open Planning Project)

Gabriel Roldán wrote:

catching up on email

numDecimals were used to round off coordintates when encoding to xml (at least on the SVG output). I'm sure once upon a time it was used for per feature type rounding off on the WFS too. Guess WFS only uses a global value now?

anyhow, I think it's more valuable as a per feature type setting overriding the global value?

Gabriel

On Thursday 01 February 2007 20:41, Brent Owens wrote:
  

ah,
The numDecimals value is the number of significant figures that the data
set will use. So anything beyond 8 decimal places will be rounded off.

The 'dynamic' attribute for the bounding box has always been false in
the files I have seen. I will look into the code and see where it is
used, but I wouldn't worry about it for now.

Brent Owens
(The Open Planning Project)

Thomas Zuberbühler wrote:
    

Brent, thank you. That is correct, there are no isDynamic in this file. I
wrote it false and meant the parameter "dynamic". Sorry.

I try to analyze the info.xml file. What is the function of "dynamic" and
"numDecimals"?

Regards,
Thomas

<featureType datastore = "DS_tiger_roads" >
<name>tiger_roads</name>
<!--
native wich EPGS code for the FeatureTypeInfoDTO
-->
<SRS>4326</SRS>
<title>tiger_roads_Type</title>
<abstract>Generated from DS_tiger_roads</abstract>
<numDecimals value = "8" />
<keywords>tiger_roads DS_tiger_roads</keywords>
<latLonBoundingBox dynamic = "false" miny = "40.684221" maxy =
"40.878178" maxx = "-73.907005" minx = "-74.02722" />
<!--
the default style this FeatureTypeInfoDTO can be represented by.
at least must contain the "default" attribute
-->
<styles default = "tiger_roads" />
</featureType>
      

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
    

I could be wrong, it may be per featureType. Just check the code and see.

Chris

Brent Owens wrote:

I agree it should probably be assigned to each individual feature type. We will have to include it in the UI if we are going to use in instead of the global value however. Except it isn't even in the UI...

I will open a jira task to re-visit this for 1.6

Brent Owens
(The Open Planning Project)

Gabriel Roldán wrote:

catching up on email

numDecimals were used to round off coordintates when encoding to xml (at least on the SVG output). I'm sure once upon a time it was used for per feature type rounding off on the WFS too. Guess WFS only uses a global value now?

anyhow, I think it's more valuable as a per feature type setting overriding the global value?

Gabriel

On Thursday 01 February 2007 20:41, Brent Owens wrote:
  

ah,
The numDecimals value is the number of significant figures that the data
set will use. So anything beyond 8 decimal places will be rounded off.

The 'dynamic' attribute for the bounding box has always been false in
the files I have seen. I will look into the code and see where it is
used, but I wouldn't worry about it for now.

Brent Owens
(The Open Planning Project)

Thomas Zuberbühler wrote:
    

Brent, thank you. That is correct, there are no isDynamic in this file. I
wrote it false and meant the parameter "dynamic". Sorry.

I try to analyze the info.xml file. What is the function of "dynamic" and
"numDecimals"?

Regards,
Thomas

<featureType datastore = "DS_tiger_roads" >
<name>tiger_roads</name>
<!--
native wich EPGS code for the FeatureTypeInfoDTO
-->
<SRS>4326</SRS>
<title>tiger_roads_Type</title>
<abstract>Generated from DS_tiger_roads</abstract>
<numDecimals value = "8" />
<keywords>tiger_roads DS_tiger_roads</keywords>
<latLonBoundingBox dynamic = "false" miny = "40.684221" maxy =
"40.878178" maxx = "-73.907005" minx = "-74.02722" />
<!--
the default style this FeatureTypeInfoDTO can be represented by.
at least must contain the "default" attribute
-->
<styles default = "tiger_roads" />
</featureType>
      

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
    
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

!DSPAM:1003,45c362867687731818748!

--
Chris Holmes
The Open Planning Project
http://topp.openplans.org