Hi
I was wondering why only the LatLonBounding box is available in the
GetCapabilities in the Wms-server (and wfs-server).
The output from the wms would be something like this:
<SRS>EPSG:27395</SRS>
<LatLonBoundingBox minx="16.693730214391707" miny="59.452884144807726"
maxx="19.77848899378803" maxy="61.13406737803451"/>
This is fine and of course correct.
The problem is that I use the default bounding box to calculate the
correct ratio between width and height on the GetMap request sent to the
wms server. Since the map in fact has a different projection than the
lat lon box, the image gets stretched.
In the dtd it is possible to have more than LatLonBoundingBox available.
It would good to be able to get a output like this:
<SRS>EPSG:27395</SRS>
<LatLonBoundingBox minx="16.693730214391707" miny="59.452884144807726"
maxx="19.77848899378803" maxy="61.13406737803451"/>
<BoundingBox SRS="EPSG:27395" minx="-10257.6588869"
miny="164922.82288386" maxx="156062.68376291" maxy="349019.58779708"/>
The GetFeature of the wfs returns the projection bounding box, but I
would prefer to have my code to work with the wms only, as there might
be cascading wfs datastores.
Currently I take the lat lon bounding box and use geotools to calculate
the projection bounding box. This works just fine, but it just seems a
bit unnecessary as the information is already present in the system.
Any thoughts?
Magne
The only reason that the lat/long is the only one available is because it was the easiest to code and the only one required. If you were to code up a way to add an alternative, we'd certainly be happy to accept the contribution. The biggest concern is probably the user interface, to not clutter the featureType editor too much. Perhaps a pop-up like the SLD stuff might work, and then it could just report what the bounding boxes are. The code is obviously pretty easy to do, since we already do the transform in to lat/long. It'd just have to transform in to the selected epsg.
Chris
Magne Skjeret wrote:
Hi
I was wondering why only the LatLonBounding box is available in the
GetCapabilities in the Wms-server (and wfs-server).
The output from the wms would be something like this:
<SRS>EPSG:27395</SRS>
<LatLonBoundingBox minx="16.693730214391707" miny="59.452884144807726"
maxx="19.77848899378803" maxy="61.13406737803451"/>
This is fine and of course correct.
The problem is that I use the default bounding box to calculate the
correct ratio between width and height on the GetMap request sent to the
wms server. Since the map in fact has a different projection than the
lat lon box, the image gets stretched.
In the dtd it is possible to have more than LatLonBoundingBox available.
It would good to be able to get a output like this:
<SRS>EPSG:27395</SRS>
<LatLonBoundingBox minx="16.693730214391707" miny="59.452884144807726"
maxx="19.77848899378803" maxy="61.13406737803451"/>
<BoundingBox SRS="EPSG:27395" minx="-10257.6588869"
miny="164922.82288386" maxx="156062.68376291" maxy="349019.58779708"/>
The GetFeature of the wfs returns the projection bounding box, but I
would prefer to have my code to work with the wms only, as there might
be cascading wfs datastores.
Currently I take the lat lon bounding box and use geotools to calculate
the projection bounding box. This works just fine, but it just seems a
bit unnecessary as the information is already present in the system.
Any thoughts?
Magne
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-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
!DSPAM:1003,44a443d138041336712104!
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org
Chris Holmes wrote:
Hi
The only reason that the lat/long is the only one available is because
it was the easiest to code and the only one required.
True.
If you were to
code up a way to add an alternative, we'd certainly be happy to accept
the contribution. The biggest concern is probably the user interface,
to not clutter the featureType editor too much.
Does it even have to be in the editor? You already type in the srs the
points of the featureType is coded in, and press generate to create the
lat lon bounding box from these points using the given srs. It is the
source of this calculation I am interested in; the point used to
calculate the lat lon.
Not sure why this needs to be a item in the user interface, but for sure
it could be printed if needed. It should not be a problem to store the
points and srs used to calculate the lat lon bounding box from.
Perhaps a pop-up like
the SLD stuff might work, and then it could just report what the
bounding boxes are. The code is obviously pretty easy to do, since we
already do the transform in to lat/long. It'd just have to transform in
to the selected epsg.
The selected epsg is what we calculate the lat lon from. I do not
understand why the user needs to select anything.
I am no gis expert, so please educate me if I got this wrong.
Magne
Chris
Magne Skjeret wrote:
Hi
I was wondering why only the LatLonBounding box is available in the
GetCapabilities in the Wms-server (and wfs-server).
The output from the wms would be something like this:
<SRS>EPSG:27395</SRS>
<LatLonBoundingBox minx="16.693730214391707" miny="59.452884144807726"
maxx="19.77848899378803" maxy="61.13406737803451"/>
This is fine and of course correct.
The problem is that I use the default bounding box to calculate the
correct ratio between width and height on the GetMap request sent to the
wms server. Since the map in fact has a different projection than the
lat lon box, the image gets stretched.
In the dtd it is possible to have more than LatLonBoundingBox available.
It would good to be able to get a output like this:
<SRS>EPSG:27395</SRS>
<LatLonBoundingBox minx="16.693730214391707" miny="59.452884144807726"
maxx="19.77848899378803" maxy="61.13406737803451"/>
<BoundingBox SRS="EPSG:27395" minx="-10257.6588869"
miny="164922.82288386" maxx="156062.68376291" maxy="349019.58779708"/>
The GetFeature of the wfs returns the projection bounding box, but I
would prefer to have my code to work with the wms only, as there might
be cascading wfs datastores.
Currently I take the lat lon bounding box and use geotools to calculate
the projection bounding box. This works just fine, but it just seems a
bit unnecessary as the information is already present in the system.
Any thoughts?
Magne
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-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
!DSPAM:1003,44a443d138041336712104!
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-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Magne Skjeret wrote:
Chris Holmes wrote:
Hi
The only reason that the lat/long is the only one available is because
it was the easiest to code and the only one required.
True.
If you were to
code up a way to add an alternative, we'd certainly be happy to accept
the contribution. The biggest concern is probably the user interface,
to not clutter the featureType editor too much.
Does it even have to be in the editor? You already type in the srs the
points of the featureType is coded in, and press generate to create the
lat lon bounding box from these points using the given srs. It is the
source of this calculation I am interested in; the point used to
calculate the lat lon.
Not sure why this needs to be a item in the user interface, but for sure
it could be printed if needed. It should not be a problem to store the
points and srs used to calculate the lat lon bounding box from.
I'm just saying you need _somewhere_ to say what other SRS's you want it available in. I could concede that you could do it with very little user feedback, the only 'generate' that is shown is the lat/long, and the others are hidden and just reported. But at the very least you'll need a box or a pop-up or drop-down to select what other SRS's you want the bounding box available in. I guess the _easiest_ possible route would be a checkbox that says 'also make available in native bbox'.
I suppose I could even be open to just a configuration button in the 'server' section that sets a global variable that says 'I want two bounding boxes - the lat/long _and_ whatever the native srs is - for all layers'. But then you'd have to check it too for the edge case when someone's data is already lat/long.
Perhaps a pop-up like
the SLD stuff might work, and then it could just report what the
bounding boxes are. The code is obviously pretty easy to do, since we
already do the transform in to lat/long. It'd just have to transform in
to the selected epsg.
The selected epsg is what we calculate the lat lon from. I do not
understand why the user needs to select anything.
I am no gis expert, so please educate me if I got this wrong.
No, not a GIS problem, just a problem of where you put the selection in for the user to select if they want their bboxes as other SRS's, and if so, what projections they want it in. I'm open to a very simple one, the one thing I'd be against is a solution that just assumes everyone wants multiple boxes. There needs to be an option to turn the new feature on/off _somewhere_ in the gui. Even if it's a global variable.
best regards,
Chris
Magne
Chris
Magne Skjeret wrote:
Hi
I was wondering why only the LatLonBounding box is available in the
GetCapabilities in the Wms-server (and wfs-server).
The output from the wms would be something like this:
<SRS>EPSG:27395</SRS>
<LatLonBoundingBox minx="16.693730214391707" miny="59.452884144807726"
maxx="19.77848899378803" maxy="61.13406737803451"/>
This is fine and of course correct.
The problem is that I use the default bounding box to calculate the
correct ratio between width and height on the GetMap request sent to the
wms server. Since the map in fact has a different projection than the
lat lon box, the image gets stretched.
In the dtd it is possible to have more than LatLonBoundingBox available.
It would good to be able to get a output like this:
<SRS>EPSG:27395</SRS>
<LatLonBoundingBox minx="16.693730214391707" miny="59.452884144807726"
maxx="19.77848899378803" maxy="61.13406737803451"/>
<BoundingBox SRS="EPSG:27395" minx="-10257.6588869"
miny="164922.82288386" maxx="156062.68376291" maxy="349019.58779708"/>
The GetFeature of the wfs returns the projection bounding box, but I
would prefer to have my code to work with the wms only, as there might
be cascading wfs datastores.
Currently I take the lat lon bounding box and use geotools to calculate
the projection bounding box. This works just fine, but it just seems a
bit unnecessary as the information is already present in the system.
Any thoughts?
Magne
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-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
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-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
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-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
!DSPAM:1003,44a456b854761425493344!
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org