[mapguide-users] Add features to SQL Server Spatial

[Gunter Becker]

The advantage of using FDO via the MapGuide API is that you just have to
write the code one time and then it should work far all feature sources
regardless of datastore (database or file based).
Yes, I would be able to use SQL Scripts but I try to avoid using them. If I
dont't find the solution to my problem or find out that it is a bug in
mapguide code then I will use SQL Scripts.

Thanks, Gunter


Rodolfo Moreno wrote:
> 
> why don't you insert sql features using SQL spatial scripts?
> 
> Regards,
> 
> 
> Gunter Becker wrote:
>> 
>> Is there at least anyone who had successfully added features to SQL
>> Server 2008 Spatial with the MapGuide API. What could cause problems when
>> adding features to the database?
>> 
>> I think there was another thread (
>> http://n2.nabble.com/MSSqlServer-Spatial-problem-tt3148712.html#a3154109
>> MSSqlServer Spatial problem ) that describes a similar problem.
>> But this problem had to do with 3-dimensional point what is not what i am
>> using. I am using x,y-points.
>> 
>> Any ideas?
>> 
>> Gunter 
>> 
>> 
>> 
>> Gunter Becker wrote:
>>> 
>>> Hi, 
>>> 
>>> i'm trying to add features to an existing FeatureSource via MapGuide
>>> API. I've created a new schema with Autodesk Map 2010, created some
>>> polygons, created my feature source and layer in MapGuide Studio,
>>> inserted the layer in my map and it shows up fine.
>>> 
>>> OK, displaying the features works fine. But when trying to add some
>>> features via the digitize function and my serverside code nothing
>>> happens. It seemes that the code works fine, cause it is the same code
>>> that I use with sdf feature sources and the code throws no error in
>>> debug mode. The "UpdateFeatures"-Methode seems to work but when looking
>>> into the SQL Server table there is no entry and therefore no object on
>>> the map. When logging SQL-Statements with SQL Profiler no activities
>>> were logged.
>>> 
>>> Only thing that works is deleting an existing map from the
>>> featuresource. So maybe it has to do something with the
>>> coordinatesystem? But as far as I understand the geometry-column of my
>>> databasetable doesn't need a coordinatesystem assigned!
>>> 
>>> Someone who had same problem? Any ideas?
>>> 
>>> Thanks, Gunter
>>> 
>> 
>> 
> 
> 

-- 
View this message in context: http://n2.nabble.com/Add-features-to-SQL-Server-Spatial-tp3878130p3897434.html
Sent from the MapGuide Users mailing list archive at Nabble.com.