Hi Jukka Given a WFS can also output OSM format, there is not necessarily an additional component needed.
The concept of GML contains two features among others: It is based on a user defined schema and it allows user defined response data formats (where GML is mandatory). Being based on a user defined schema means that somebody needs to configure a mapping to the OSM format. OSM has some mandatory attributes like an id, a user_id and a version number. Allowing user defined response data formats means that OSM XML could be such an alternate format. See our POI-Service (temporary and prototype) for such a WFS implementation: http://152.96.56.32/poiservice/ Yours, Stefan 2011/8/24 Jukka Rahkonen <[email protected]>: > Hi, > > How about adding one more component between the external database and the > related OSM API for converting data coming from WFS service or GML file > into OSM format? There will be hundreds of Inspire download services out > there rather soon and many of them will probably be public. Some reading > about the download services > http://inspire.jrc.ec.europa.eu/documents/Network_Services/INSPIRE%20Draft%20Technical%20Guidance%20Download%20%28Version%202.0%29.pdf > > Member states must make available the compulsory datasets described in the > Inspire directive but member states will naturally use the same > infrastructure for delivering other spatial data as well. > > I do not know if it is easy or not to convert GML data that comes from WFS > server into OSM.xml. Somebody interested can have a try. Some municipality > border data is here > http://188.64.1.61/cgi-bin/tinyows?service=WFS&version=1.1.0&request=GetFeature&typeName=lv:municipalities&srsName=EPSG:4326 > > and the corresponding schema comes with this request > http://188.64.1.61/cgi-bin/tinyows?service=WFS&version=1.1.0&request=DescribeFeatureType&typeName=lv:municipalities > > -Jukka Rahkonen- > > > Jaak Laineste wrote: >> Hello, >> >> Based on my own long-time thinking and small talk in WhereCamp Berlin >> I created request for comments on kind of different approach to >> imports called meta-mapping. >> >> Core of the idea is to avoid external data imports and reserve OSM >> database for what was meant for: community-sourced (manual) mapping. But > it is not plain "banning imports", it is to provide alternative tool (I > call it OpenMetaMap) which enables to link various external data sources > with OSM data, with much better flexibility than with current import > approach. >> >> My proposal is in http://wiki.openstreetmap.org/wiki/OpenMetaMap , >> any positive and negative comments (especially help to actually >> implement it) is most welcome. >> >> >> JaakL >> >> _______________________________________________ >> dev mailing list >> [email protected] >> http://lists.openstreetmap.org/listinfo/dev >> > > > > > > _______________________________________________ > dev mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/dev > _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
