sorry for being late but for some reason none of my datasets could be
transfered via fME to SQL Server.
does anyone has a small file i could upload to run tests?
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/MGOS-SQLexpress-coordinate-flip-tp4993496p4996369.html
Sent
Yes, the GEOG data type in SQL Server is fine, its just GEOM that is the
flipping (in my test anyway).
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/MGOS-SQLexpress-coordinate-flip-tp4993496p4996486.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
Does the data render properly if the column in question was a geography
instead of geometry?
- Jackie
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/MGOS-SQLexpress-coordinate-flip-tp4993496p4995271.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
i can confirm this happens with:
4997
4975
4686
4267
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/MGOS-SQLexpress-coordinate-flip-tp4993496p4994885.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
___
Does AIMS 2013 have this problem too?
- Jackie
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/MGOS-SQLexpress-coordinate-flip-tp4993496p4994038.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
___
Yes, as a matter of fact it fails (rotated sideways = SRID 4326 ) in
AIMS 2013
Map 3D 2013
MGOS 2.4
It works with
QGIS 1.7
ArcMap 10
whoa, big fail across the board with 4326 in MGOS 2.4 / Autodesk 2013
--
View this message in context:
sounds like someone got their X Ys and Lats and Longs mixed up.
I purposely make my field names X_LONG Y_LAT so my clients aren't
confused no matter what software they use
On Thu, Aug 9, 2012 at 10:29 AM, GordonL
gordon.luck...@arrowgeomatics.comwrote:
Yes, as a matter of fact it fails
Anyone wanting to see this happen with SQL Server and MGOS 2.4 or AIMS 2013,
first add the table to SQL Server:
CREATE TABLE [dbo].[COUNTRY](
[ID] [int] IDENTITY(1,1) NOT NULL,
[COUNTRY] [varchar](50) NULL,
[GEOM] [geometry] NULL,
CONSTRAINT [PK_COUNTRY] PRIMARY KEY
Ticketed: http://trac.osgeo.org/fdo/ticket/844
This is a definite show-stopper.
As an aside, whoever decided that geographic coordinates should be expressed
as lat/lon should be severely beaten up. How many people (myself included)
have fallen to this rookie mistake as a result?
- Jackie
--
Is this also happening with any SRID within the range of 4120 to 4999
(inclusive)?
- Jackie
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/MGOS-SQLexpress-coordinate-flip-tp4993496p4994293.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
Just a LL84 World SHP file.
I think I had loaded it with the
http://www.sharpgis.net/page/sql-server-2008-spatial-tools.aspx
Or perhaps the OGR2OGR, it doesn't matter which, because it happens wtih SQL
Server Spatial regardless.
SHP file here:
My datasets were loaded into SQL by simple export from Manifold. This has
worked for years and still works great with MGOS 2.2. Using the same SQL
database MGOS2.2 works fine but MGOS2.4 flips the coordinates.
--
View this message in context:
With MG 2.4 I am having the exact same result. The SQL Server FDO Provider
is flipping the coordinate system.
http://osgeo-org.1560.n6.nabble.com/file/n4993736/mgFlip.png
--
View this message in context:
as this is an FDO related question, I have forwarded this on to FDO-Users
On Wed, Aug 8, 2012 at 4:43 AM, GordonL
gordon.luck...@arrowgeomatics.com wrote:
With MG 2.4 I am having the exact same result. The SQL Server FDO Provider
is flipping the coordinate system.
That is most strange.
I'm interested in the source of that SQL Server dataset and how it was
produced.
- Jackie
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/MGOS-SQLexpress-coordinate-flip-tp4993496p4993779.html
Sent from the MapGuide Users mailing list archive at
I have setup a new server with MGOS 2.4 and SQLserver2008. I have migrated
the SQL db from another machine with MGOS2.2 and SQLserver2008 (backup -
restore). When using the MGOS 2.4 server point data that is stored in
geographic coordinates LL have the coordinates reversed when displayed in
16 matches
Mail list logo