European Commission logo
INSPIRE Community Forum

EF address element

  • General

    The INSPIRE Community Forum is now part of the INSPIRE helpdesk system, based on GitHub (, so please start there any new discussions.

    The current platform will remain available in read only mode in its current form and URL address until 31/01/2021, then its content will be archived and then published in a different URL which will be announced when it becomes available.

Dear all,

a short post dedicated to ef:responsibleParty element in EF schema.

In particular EF adopted base2, ad and gn namespaces for archive address information (base2:address). All elements are mandatory (e.g. gn:language, gn:nativeness, gn:pronunciation, gn:spelling, etc.) but they are so difficult to provide.

base2:address element provides also the attribute psi:nil, but in this case cannot have character.

My question for the group is easily how to put in address in EF, without use this crazy schemas?

For example in SensorML the element address within sml:ResponsibleParty contains deliveryPoint, postalCode, city, and country.

Has anyone had the same problem?

Best regards


  • Katharina SCHLEIDT

    By Katharina SCHLEIDT

    Dear Alessandro,

    First off, to shift the glass from half-empty to half-full, we did manage to avoid the complexity of GN in the facility name by arguing that our EM-Facilities can also be mobile and this non-geographic (try putting an address on a satellite! ;) )

    We're very much aware of the RelatedParty dilemma, and at least I'd welcome feedback from users requesting a simplification (Annex II & III are being discussed for simplification, but a great deal of this complexity stems from the underlying Annex I data models). If this type could be revisited, I'd also vote for upgrading to a featureType, so that we could reuse and reference (at least in the datasets I've been working on, the same handful of responsibles are repeated again and again and...)

    But, from a handling perspective, it hasn't been as bad as I'd feared :) Most of the stuff that seems superfluous to us ends up as constants in the configuration file. At the end of the day, all you need to provide are the basic values as described by you above (example below):

    • IndividualName
    • OrganisationName
    • City
    • Address
    • PostCode
    • E-Mail
    • Phone
    • URL

    The rest I've come to see as necessary fluffy packaging and just get on with more interesting stuff!



                                    <gn:nativeness xsi:nil="true" nilReason="Unpopulated"/>
                                    <gn:nameStatus xsi:nil="true" nilReason="Unpopulated"/>
                                    <gn:sourceOfName xsi:nil="true" nilReason="Unpopulated"/>
                                    <gn:pronunciation xsi:nil="true" nilReason="Unpopulated"/>


  • klimeto

    Dear all,

    I wanna share the way we implemented the address information in EML encoding from the data collected using Dynamic Ecological Information Management System (DEIMS). For the sake of simplicity we did not use the base2:address, but instead base2:contactInstructions concatenating street, number, city and country from the system database. Example:

    <gco:CharacterString>Largo Tonolli, 50 Verbania Pallanza IT</gco:CharacterString>
    In this way we don't link to other INSPIRE themes ad->gn and do not need to list tons of "Unpopulated" elements that must appear in order to be valid.
    On the other hand, the information encoded in this way fulfil basic use case to geolocate the contact data using e.g. Google geocoding API:
    ‚ÄčFor more EMF data examples feel free to visit:

This discussion is closed.

This discussion is closed and is not accepting new comments.

Environmental Monitoring & Observations

Environmental Monitoring & Observations

Environmental Monitoring Facilities, Observations and Measurements