Skip to main content
Question

Hi, i am trying to convert my access template into an gml compliant with an xsd. Is there any tutorial taht could guide me through this process?


Forum|alt.badge.img

This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

13 replies

danilo_fme
Evangelist
Forum|alt.badge.img+51
  • Evangelist
  • July 24, 2017

Hi @valantistsiakos, the best way is Generate Workspace:

Reader and Writer configuration:

And now in Parameter Writer Option, you choose the GML Application Schema: and click in your XSD file in your machine.

Thanks,

Danilo


Forum|alt.badge.img

Hi Danilo,

I tried this approach but still the output GML is not compliant with the xsd. I ran the produced GML and still an error occurs (https://www.freeformatter.com/xml-validator-xsd.html).

Are there any other parameters that i have to consider or any other suggestions for the transformation ?

 

Thanks,

Valantis


danilo_fme
Evangelist
Forum|alt.badge.img+51
  • Evangelist
  • July 24, 2017

@valantistsiakos, what kind of error is showing in the LOG FME Desktop?


Forum|alt.badge.img

log-file.txtworkflow-mapping.png

Hi I am attaching the log message and a screenshot of the mapping.


danilo_fme
Evangelist
Forum|alt.badge.img+51
  • Evangelist
  • July 24, 2017

Thanks your information log file @valantistsiakos.

Really has a problem with feature types.

The following feature types were not written, they did not match any feature types from the GML Application Schema:

Could you send the template file ( . FMWT )?

Thanks,

Danilo


danilo_fme
Evangelist
Forum|alt.badge.img+51
  • Evangelist
  • July 24, 2017

Has a message in LOg that the feature types from GML Application Schema are not the same the feature types:

The feature types determined from the GML Application Schema are: 'AccessRestriction, ActivityComplex, Address, AddressAreaName, AdminUnitName, AdministrativeBoundary, AdministrativeUnit, BasicPropertyUnit, Building, BuildingPart, CadastralBoundary, CadastralParcel, CadastralZoning, ConditionOfFacility, Condominium, CrossReference, GradeSeparatedCrossing, MaintenanceAuthority, MarkerPost, NamedPlace, Network, NetworkConnection, OwnerAuthority, PostalDescriptor, ProductionBuilding, ProductionFacility, ProductionInstallation, ProductionInstallationPart, ProductionPlot, ProductionSite, ReportData, RestrictionForVehicles, SpatialDataSet, ThoroughfareName, TrafficFlowDirection, TransportNetwork, VerticalPosition


Forum|alt.badge.img

danilo_fme
Evangelist
Forum|alt.badge.img+51
  • Evangelist
  • July 24, 2017

Hi @valantistsiakos,

thanks your files. I tested here to import the XSD.

Writers - Import Writer Feature Types - Parameters:

  • Feature Types -

And OK. The Schema from XSD is showing:

Now you need to mapping the feature types in your Workspace.

I didnt execute the Workspace because the Reader is other version from mine.

Thanks,

Danilo


Forum|alt.badge.img

Thanks for your answer. However, the feature type list contains various features that are not provided by the reader. In addition some of the features of the reader cannot be mapped with the writer feature types.

Thanks,

Valantis


Forum|alt.badge.img

Hi Danilo @danilo_inovacao,

I managed to advance the mapping. The only issue that i am encountering lies with the coordinates. In the feature type i am trying to map the latitude and longitude attributes with pointGeometry attribute in the writer. I've tried various things (i.e. StringConcatenator, etc) but i cannot find something to actually working.

Could you please be so kind and let me me know if you have any thoughts on hte matter ?

I attach also the fmw and microsoft access files for your kind review.

Thanks you in advance,

Valantis mdb-ado2gml-new.fmweu-registry-ek-04-07-2017-dummy-data-final.zip


danilo_fme
Evangelist
Forum|alt.badge.img+51
  • Evangelist
  • July 26, 2017
valantistsiakos wrote:

Hi Danilo @danilo_inovacao,

I managed to advance the mapping. The only issue that i am encountering lies with the coordinates. In the feature type i am trying to map the latitude and longitude attributes with pointGeometry attribute in the writer. I've tried various things (i.e. StringConcatenator, etc) but i cannot find something to actually working.

Could you please be so kind and let me me know if you have any thoughts on hte matter ?

I attach also the fmw and microsoft access files for your kind review.

Thanks you in advance,

Valantis mdb-ado2gml-new.fmweu-registry-ek-04-07-2017-dummy-data-final.zip

 

Hi @valantistsiakos, i opened your reader ProductionInstallationPart and doens't have geometry.

 

So, i used the transformer VertexCreator:

 

And now i have points. I believe that is the reason now.

 

Thanks,

 

 

Danilo

Forum|alt.badge.img
danilo_fme wrote:

 

Hi @valantistsiakos, i opened your reader ProductionInstallationPart and doens't have geometry.

 

So, i used the transformer VertexCreator:

 

And now i have points. I believe that is the reason now.

 

Thanks,

 

 

Danilo
Hi Danilo @danilo_inovacao,

 

 

I've used the Vertex Creator. Then, how can I map thsese points with the writer ?

 

 

Thanks again,

 

Valantis

 

 

 


danilo_fme
Evangelist
Forum|alt.badge.img+51
  • Evangelist
  • July 28, 2017
valantistsiakos wrote:

Thanks for your answer. However, the feature type list contains various features that are not provided by the reader. In addition some of the features of the reader cannot be mapped with the writer feature types.

Thanks,

Valantis

 

Hi , i used the transformer vertexcreator and execute the Workspace.

 

The message in LOG file was showed the parameter to setter : about the coordinate. I configurated to EPSG: 4326 .

 

But not sucess. Anyone some help with us with this case.

 

 

 

Thanks Danilo

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings