#689 closed enhancement (fixed)
EPSG Support
| Reported by: | thomasknoell | Owned by: | brucedechant |
|---|---|---|---|
| Priority: | low | Milestone: | 2.1 |
| Component: | Feature Service | Version: | 2.0.1 |
| Severity: | trivial | Keywords: | |
| Cc: | External ID: |
Description
Changes are required wherever the WKT data from a spatial context is read as it may indicate the presence of an EPSG code in which case the WKT data has to be retrieved differently.
Change History (6)
comment:1 by , 16 years ago
| Status: | new → assigned |
|---|
comment:2 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
follow-up: 4 comment:3 by , 16 years ago
| Component: | General → Feature Service |
|---|---|
| Milestone: | → 2.1 |
comment:4 by , 16 years ago
comment:5 by , 16 years ago
That is a supported EPSG code so it should work.
Can you confirm that the exact text for the coordinate system failure you are seeing is as follows?
EPSG:27700
Note:
See TracTickets
for help on using tickets.
Replying to brucedechant:
Hi Bruce - I have been trying forever to configure a MapGuide map to a WMS server that contains layer definitions in ESPG. I am still having problems after creating a build with this new feature!
If I sent a small package with a datasource, layer and map definitions would you be able to see if there is an error in my config or there remains a bug in MapGuide - or a limitation e.g.
The coordinate system is invalid. Could not parse the OGC WKT: EPSG:27700. Internal error: Exception occurred in method MgCoordinateSystem.CCoordinateSystem at line 596 in file ..\CoordinateSystem\CoordSys.cpp