Séminaire Services publiques
•Transferir como PPT, PDF•
1 gostou•702 visualizações
Présentation du projet de spécifications du thème de l'annexe III de la directive INSPIRE - septembre 2011
![Le plan ,[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Recomendados
Mais conteúdo relacionado
Semelhante a Séminaire Services publiques
Semelhante a Séminaire Services publiques (20)
Mais de Marc Leobet
Mais de Marc Leobet (18)
Séminaire Services publiques
- 1. MEDDTL-IGN Séminaire thématique Services d'utilité publique et services publics
- 10. Avertissement A partir de cette diapositive, les éléments sont des propositions de la Commission européenne et n’induisent pas l’accord du ministère
- 18. MEDDTL/ONEMA/OIEAU Revue des questions ouvertes et des propositions d’obligations
- 19. Question ouverte n°1 Examen des autres réseaux Jusqu'ici, les réseaux de chauffage urbain sont considérés comme un type spécifique de réseau d'eau; Selon les différents commentaires qui pourront être reçus avant la version 2.9, il serait possible d'ajouter un type distinct de réseau pour de telles installations (type basé sur les spécificités techniques qui sont pas utilisé par d'autres types de réseaux).
Notas do Editor
- De nombreux pays apportent des remarques de forme Les français apportent plutôt des remarques de fond
- Et vise le leadership mondial : prise en compte des décisions européennes par les éditeurs américains, reprise par des pays tiers (Brésil)…
- Explication des SDIC/LMO Partie 1 derrière nous Sommes en partie 2 Printemps 2012 : spec. V3 projet de règlement; demande de relecture par les SDIC/LMO; avis de la France sur le projet. Juin 2012 : vote au Comité de réglementation.
- Parler du rôle de lobbying
- Les spécifications doivent rester simples car les compétences sont rares et les coûts doivent rester contrôler. Seules les directives thématiques peuvent aller plus loin que le minimum.
- De nombreux pays apportent des remarques de forme Les français apportent plutôt des remarques de fond
- basé sur un type d'entité unique, "GovernmentalService". Sa référence géométrique peut être un autre objet pré-existant (adresse, de construction ou de «facilité») ou un objet créé (POI = Point of Interest). La valeur de type GovernmentalService est choisi parmi une liste de codes de plus de 200 articles, organisés en une structure hiérarchique, basé sur la «Classification des fonctions de gouvernement», ou COFOG, utilisée par Eurostat.
- Where the scopes of other INSPIRE spatial data themes require including their domain specific management or regulated areas or reporting units within those themes, than those topics stay out of the scope of the theme AM. For example: bio-geographical regions are defined within the INSPIRE theme Bio-geographical regions , INSPIRE theme Protected sites includes theme specific protected areas, etc. On the other hand, some duplications might be necessary, because of the different views (and scope) on the same geographical / natural phenomena, for example: the sea regions might be defined in the INSPIRE theme Sea regions on the basis of physical or chemical characteristics, while the sea/marine regions defined for the management purpose are included in the theme AM.
- Open issue 1: Consideration of other networks So far, District heating networks are considered as a specific type of Water network; According to the different comments that may be received before version 2.9, it would be possible to add a separate type of network for such utility (based on technical specificity that are not used by other types of networks).
- Open issue 2: For all Annex II+III themes for which placeholders and candidate types were specified in an Annex I data specification, it should be clearly indicated in the data specification, how the placeholder and candidate types were taken into account. If the proposed solution would require any changes to an Annex I data specification (and the corresponding section in the IR for interoperability of spatial data sets and services), this should also be clearly indicated. A thorough investigation of the implications of the proposed changes of candidate types (in particular related to requirements of Annex I maintenance) will have to be performed for v3.0 of the data specifications. Open issue 3: Use of standards for legal reference or contact information A specific feature “ LegislationReference ” has been recently developed for referring to any legal document in the AM theme. This could be integrated in the US model further versions for some elements, instead of the CI_Citation current proposal. Same approach will be developed within US or externally with other themes for providing specific information to several actors of the “ Utility and governmental services » theme (owner, maintainer, operator), since the CI_ResponsibleParty is more dedicated to data and metadata providers than services.
- Open issue 3: Use of standards for legal reference or contact information A specific feature “ LegislationReference ” has been recently developed for referring to any legal document in the AM theme. This could be integrated in the US model further versions for some elements, instead of the CI_Citation current proposal. Same approach will be developed within US or externally with other themes for providing specific information to several actors of the “ Utility and governmental services » theme (owner, maintainer, operator), since the CI_ResponsibleParty is more dedicated to data and metadata providers than services.
- Open issue 4: Harmonization of the temporal information Currently, the model proposes 2 expressions to describe opening hours of the services: PT_FreeText (cf. Administrative and social governmental services submodel) and ServiceHoursType (cf. Waste Management submodel). According to the comments received during the testing phase, it should be likely that these types will be harmonized one way or another.
- COM : est-ce un besoin pour les acteurs? Open issue 5: Requirement to provide 3D information The upper Note should be considered with the constraint to keep the possibility to host 3D information within the model (noticed by several use cases). So if the restriction to use only the Simple Feature spatial schema prevents to host such 3D data, another schema should be developed for the tri-dimensional information (at least for utility networks submodel).
- Open issue 6: The recommendation of providing an identifier / number as part of the codes to indicate the hierarchy has not been taken into account for the current specifications. Such transformation of the codelist values could be done for version 3.0, if required, but could become rather complex or long, e.g. “HEA_04_03_07_13_otorhinolaryngology”. The clearance of the codelist should be the main priority; its format may evolve later. The hierarchical structure is provided in Annex D.
- Open issue 7: In the ongoing revision of ISO 19115 and development of new ISO 19157 standard (Geographic Information – Data quality), a new element is introduced (DQ_DescriptiveResult). This element enables to describe and report qualitative results of the data quality evaluation and could be used instead of DQ_QuantitativeResult. Once the new (version of the) standards are approved, these guidelines will be revisited and be updated if necessary.
- Open issue 8: For reporting compliance with minimum data quality requirements and recommendations specified in section 7, the INSPIRE conformity metadata element should be used. However, since this issue is part of the larger discussion on the Abstract Test Suite and the definition of conformance classes for the data specification, detailed instructions on how to provide metadata on compliance with minimum data quality requirements and recommendations will only be provided for v3.0.
- Open issue 9: Conformance testing is still an open issue under discussion. Instructions on conformance testing and a common abstract test suite (including detailed instructions on how to test specific requirements) will be added at a later stage. This may also lead to an update of the recommendations on how to fill the conformity metadata element.
- Recommendation 20 To describe the transformation steps and related source data, it is recommended to use the following sub-elements of LI_Lineage: - For the description of the transformation process of the local to the common INSPIRE data structures, the LI_ProcessStep sub-element should be used. - For the description of the source data the LI_Source sub-element should be used. NOTE 1 This recommendation is based on the conclusions of the INSPIRE Data Quality Working Group to avoid overloading of the overall lineage statement element with information on the transformation steps and related source data. NOTE 2 In order to improve the interoperability, domain templates and instructions for filling these free text elements (descriptions) may be specified in an Annex of this data specification. Open issue 10: The suggested use of the LI_Lineage sub-elements needs to be discussed as part of the maintenance of the INSPIRE metadata Technical Guidelines.