[mapguide-users] Spatial Data Formats Best Practice

[GISDOTNET]

Kenneth,

That's what I don't understand. The features are in an ESRI personal
geodatabase when I use OGR and the tables as they are seen don't have other
geometry types e.g. in ESRI you can't have mixed geometries in a
featureclass/table. I thought that the OGR was having trouble reading the
geometry type which is why I converted the personal geodatabase to PostGIS.
The conversion went without problem; however, it still sees each table as
having all geometries which I know is not the case.

I just downloaded Maestro and was able to set the proper geometry to
display, but there isn't a preview in Maestro? So I saved the layer and
opened Autodesk MapGuide Studio 2008 and noticed that the layer showed an
error on the "Feature Class" dropdown. It appears that Maestro sees the
feature class differently than MapGuide Studio (MapGuide Studio<Feature
class=FdoPostGIS:public~taxparcel> and
Maestro<Schema=FdoPostGIS:public-x7e-taxparcel>. Not sure why or what this
means, but I can't jump between the two environments.

In which environment does the "Preview" button that you mentioned reside?

Thanks again.

Aaron


Kenneth Skovhede, GEOGRAF A/S wrote:
> 
> GISDOTNET skrev:
>> Kenneth,
>>
>> Thanks for the response. I am using FDO which is how I got the OGR and
>> PostGIS providers configured. It's great that I don't have to convert;
>> however, I started this thread to determine which format, if any, was
>> preferred or best practice for use with MGOS from a performance,
>> functionality, usability, etc. standpoint.
>>   
> I see, I have no good advice in that direction.
> I have tested that TAB files over OGR outperforms SDF files,
> especially if I remove unused columns.
> 
> Unfortunately, it is not as stable as I would like.
> I'm guessing that SDF is the most stable one, as it was designed for FDO.
>> What do you mean by "single polygon" when you wrote "I know the OGR
>> provider
>> reports having point+line+polygon if the table contains a single
>> polygon."
>> The table is nothing but polygons, or lines, or points. Shouldn't the OGR
>> or
>> PostGIS provider be able to distinguish the geometry from the designated
>> geometry column? I'll look into MapGuide Maestro and see if that helps.
>>
>>   
> If I have a table with only points, the OGR provider reports that it 
> contains geometry of type point.
> If I add a line, it reports that it contains points and lines.
> If I make a new table and add a single polygon, it reports having 
> points, lines and polygons.
> 
> You can view what the provider reports if you press the "Preview" button 
> while
> having the Featuresource open. (on the left side).
>> I appreciate the education.
>>
>> Aaron
>>   
> Regards, Kenneth Skovhede, GEOGRAF A/S
> 
> _______________________________________________
> mapguide-users mailing list
> mapguide-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-users
> 
> 

-- 
View this message in context: http://www.nabble.com/Spatial-Data-Formats-Best-Practice-tp17944833p18122154.html
Sent from the MapGuide Users mailing list archive at Nabble.com.