Mapinfo universal translator headers all caps

I'm guessing your postcodes are defined using the OS National Grid of Great Britain, which, by default, should be imported into SQL Server using the geometry datatype and SRID 27700. You're absolutely correct - geography is for lat/long data. In fact, I'd say from your description of the problem that your understanding of spatial concepts is pretty good, actually :) In principle then, do I need to convert each point in the geometry polygon to lat/long, then convert the geometry polygon to geography? And if this is the case, what is the best tool for doing this? I am assuming that the geography datatype can only store polygons where the points are stored as lat / long even with my limited understanding, this would make sense - eastings and northings are 'flat', and geography is 'round'. However, when I examined the content of the gemetry field by CONVERTing it to text, I could see the polygon was made up of I was a bit puzzled, but loaded the data into a geometry field, thinking I could then convert geometry to geography with no problem. The conversion to shapefiles worked fine, but when I went to use Shape2SQL to load the shapefile into SQL, I could only load into a geometry - when I tried to load into geography, it gave me a warning about the points being out of range. I've done this a few times with otherВ polygon datasets, and it's worked well. I managed to use the MapInfo universal translator to convert the files to shapefiles, knowing that I could then use Shape2SQL to import them into a SQL geography field. Obviously, there are going to be some conversion hoops to jump through.

I want to store the polygonsВ in aВ SQL geography field. I have a UK OS dataset which contains a polygon for each postcode in the UK. First off, my understanding of Spatial concepts is pretty poor, so plesae excuse me if this question is fundamentally dumb.

Mapinfo universal translator headers all caps