Tag Info

Hot answers tagged

5

When you import the data into SQL Server, put it into a VARBINARY(MAX) column. You should then be able to CAST this as a Geometry or Geography as required. You will need to be careful that the string 0xE6 ... is not changed during the import. Another option is to do a dynamic query to get the selection. I put a couple of conversion examples below. -- As ...


4

Building on @MickyT's answer, since you're going to have a table with your values already sitting in WKB (or whatever we're calling it), you would want to write sql that will convert all records to geometry, rather than having to declare a variable, etc. etc. So if you start off with a simple temp table that would replicate the WKB in one record, it would ...


2

Original poster here, when I tried to finish signup it didn't link the signin for the original post. Anyway.... Thanks for all the help! I'll upvote each answer once I'm able to and maybe if I can figure out how to link this account and the original one I can mark an answer. Also, after your pointers I can't believe I missed using CONVERT instead of ...


2

spatial indexing and being able to visualize your data You're absolutely right on those two counts. I would make one more point; building the geometry object is computationally expensive, especially on large or complex data sets. Performance and scaling will suffer, because the database is having to build the geometry on-the-fly. Your query will ...


2

Your data is in a projected coordinate system, and the units you're getting from STY and STX are returning values in the units of that coordinate system (probably feet). Unfortunately MSSQL Server doesn't support projecting your data on the fly like PostGIS does. So what you'll have to do - if possible - is to load a copy of your data projected to WGS84 ...


1

If you need only show graphics, publish you data via WMS and add WMS layer. For example on data at demo.opengeo.org <esri:WmsLayer ID="tasmania" Url="http://demo.opengeo.org/geoserver/topp/wms" Version="1.1.0" Layers="topp:tasmania_state_boundaries" />


1

Ok, here is my suggestions on how to do this. Depending on your situation, you may have ESRI's MapIt, which seems to do most of the hard work for you. I looked at their site, and it doesn't seem like it is available anymore. If you have it, try it. If not, here is my longer version, which @kes alluded to in the comment. Create a way to access the data ...


1

If you've got a polygon you want to use as a declared variable and intersect it with a table containing existing geometry, your query (including your polygon variable declaration) would look something like this: (MSSQL Server syntax) declare @polygon geometry = 'POLYGON((-9486683.581 4810152.256, -9282073.762 4821688.121, -9262037.786 4625578.413, ...


1

It had to do with how the AGS (ArcGIS Server) account was set up. The AGS is a local account not a AD account because of this it use db authentication not OS authentication. So because the AGS account is db authentication all accounts that are going to register data with the server have to use the same authentication mode as the AGS account when connecting ...


1

Changing feature class column names directly in SQL Server will often corrupt the feature class as SDE keeps track of column names behind the scenes. Change the column names back to to their original names in SQL Server.



Only top voted, non community-wiki answers of a minimum length are eligible