Opened 16 years ago

Closed 8 years ago

#768 closed enhancement (duplicate)

Maestro: Auto generate bounds for WMS/WFS based on the items reported spatial context

Reported by: ksgeograf Owned by: jng
Priority: medium Milestone: Maestro-5.1
Component: Maestro Version:
Severity: minor Keywords:
Cc: External ID:

Description

Before layers can be served as WMS they must have the bounds info applied. Since the bounds info should be in EPSG:4326, it is non-trivial for the user to calculate these.

Since MapGuide exposes coordinate transformation functions, Maestro should be able to convert the boundsing coordinates from the layer/featuresource and create the corresponding EPSG:4326 coordinates.

Change History (12)

comment:1 by tomfukushima, 16 years ago

I remember asking for this when this feature was first developed. I believe the argument against doing this was that these values would get stale if the data was updated. Then of course, there was the issue of having enough time to do it in the first place.

comment:2 by ksgeograf, 16 years ago

Good point. Since the data is the item gettings stale, there is no way to detect when it gets updated. The button I would add would just insert the correct values, so there should be minimal confusion for the user that they have to manually update it.

comment:3 by tomfukushima, 16 years ago

Sorry, I misread this ticket and didn't realize that you were putting this in the Maestro UI as a button, that makes perfect sense. I had mistakenly thought that this was a request to have the bounds automatically calculated by the server and that was what my first response was about. (I need to read these tickets more closely.) In case you don't know, the SpatialExtents aggregate function should be used to get the bounds of the data; there are extents in the "SpatialContext" response but those are typically incorrect.

comment:4 by ksgeograf, 16 years ago

I did not know about the SpatialExtents function, I will try to use that instead.

I think your previous comment is valid for #769 then :).

comment:5 by ksgeograf, 16 years ago

Milestone: Maestro-2.0
Status: newassigned

comment:6 by ksgeograf, 16 years ago

I have made some progress on this issue, but I am missing http functions to convert the bounding box to the required projection. I will create tickets for this.

comment:7 by ksgeograf, 15 years ago

Milestone: Maestro-2.0

I'm stuck, needing some projection functions exposed by MapGuide. There are some in the Topology framework, but they do not work with eg. XY-M.

comment:8 by ksgeograf, 15 years ago

Milestone: Maestro-2.1

comment:9 by jng, 15 years ago

Milestone: Maestro-2.1Maestro-2.5
Owner: changed from ksgeograf to jng
Status: assignednew

comment:10 by jng, 14 years ago

Milestone: Maestro-3.0Maestro-4.0

comment:11 by jng, 13 years ago

Milestone: Maestro-4.0Maestro-4.1

comment:12 by jng, 8 years ago

Resolution: duplicate
Status: newclosed
Note: See TracTickets for help on using tickets.