Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
FME Talk
Home
About this group
Contact owner to join
GML application schema (.xsd)
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Daniel@cits  
View profile  
 More options Feb 21 2012, 9:34 am
From: "Daniel@cits" <dbe...@nrcan.gc.ca>
Date: Tue, 21 Feb 2012 06:34:01 -0800 (PST)
Local: Tues, Feb 21 2012 9:34 am
Subject: GML application schema (.xsd)
Print | Individual message | Show original | Report this message | Find messages by this author
Hi all,
I wrote a sample .gml file few months ago and I just find out that the
feature definition produced (.xsd) is odd!

The .xsd file used to have all input dataset feature types defined,
even if only one feature type was written. For instance, a source
dataset having Roads and Rivers would have produced a .xsd file
containing both even if only the Rivers feature was written. The .xsd
looked like

...
<element name="Roads" type="fme:RoadsType"
substitutionGroup="gml:_Feature"/>
<complexType name="RoadsType">
<element name="Rivers" type="fme:RiversType"
substitutionGroup="gml:_Feature"/>
<complexType name="RiversType">
...

Now, only the feature type written in the sample is right (Roads), all
others have the following pattern in the .xsd file
...
<element name="XyZzY##" type="fme:XyZzYType"
substitutionGroup="gml:_Feature"/>
<complexType name="XyZzY##Type">
...

where ## is sequential numbers corresponding to the number of feature
in the source dataset that were not written in the output .gml file.

Any ideas on what have caused that or what I can do to get the
original schema?

Daniel


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Juan Chu Chow  
View profile  
 More options Feb 21 2012, 1:44 pm
From: Juan Chu Chow <juan.chuc...@safe.com>
Date: Tue, 21 Feb 2012 10:44:04 -0800
Local: Tues, Feb 21 2012 1:44 pm
Subject: RE: [fme] GML application schema (.xsd)
Print | Individual message | Show original | Report this message | Find messages by this author
Hi Daniel,

It is very odd, will you be able to send your issue to supp...@safe.com.

The GML writer has a "Write All Feature Types" option, it default to "No",
if you set it to "Yes" then all feature type definitions, even the ones
without actual features should be written to the .xsd file.

Regards,

Juan


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google