search
Enter at least two characters without personal information.

    LibraryArticles and FAQs Your projectRequest a quote
    LanguageEN ▾
    Sector content and pathways

    Local information: publish verifiable territorial data

    A local page answers a specific question on a territory. Its value depends on identifiable sources, useful dates and an announced scope, rather than automatically adding a common name to a generic text.

    These files describe preparation methods. They do not present customer achievements and do not replace the validation of information by the organization concerned.

    All sectoral files
    Map, notebook, magnifying glass and camera on a table
    AI-generated illustration

    Explore all 28 review cases — A namesake leads to the wrong town

    Identify the right territory

    Use a stable administrative code in addition to the name and check the relationship between municipality, department and region. A postal code is not a unique identifier of a municipality. When a perimeter changes, keep track of the source and the validity date instead of mixing multiple cuts.

    Separate facts and services offered

    a geographical data describes a territory; It does not prove an on-site agency, a partner or a past intervention. Explain the actual support method offered. An example of a local project remains a scenario as long as no documented realization allows it to be presented otherwise.

    Contextualize numbers

    For a population or a number of establishments, indicate the vintage, the perimeter and the source. The date of consultation of a file does not replace the year of the data. A comparison requires compatible definitions; An unknown number should be reported, not estimated to complete a box.

    Organize territorial routes

    A regional then departmental index avoids exposing a very long list of similar pages. Give links to truly useful additional information. When a municipality page does not bring anything distinct, a grouping into the relevant territory can better serve the visitor.

    Prepare for the next check

    Assign a data manager and another, if necessary, to the editorial text. Control Codes, Attachments, Duplicates, and Source Links in each import. Document preserved fields and exclusions so that the scope is not interpreted as comprehensive coverage.

    Information to gather before writing

    • Stable code and verified attachment
    • Announced coverage scope
    • vintage of each number
    • Sources and date of consultation
    • Distinction between scenario and production

    For each item, keep the source, the person validating it and the language versions concerned. Missing information must become a question to solve, never a value invented to fill the page.

    A case for preparing the content

    Publish the exact scope of local information

    Fictional case: a collection notice covers DEMO-NORD. DEMO-SUD belongs to the territory presented on the website but is not served by this notice.

    Fictional teaching exercise: these texts and values describe no real business, course or product.

    Path to check

    1. Identify the service
    2. Read the area
    3. Check the source
    4. Publish the scope

    Compare the wording

    Avoid in this example

    Collection covers the whole territory.

    More precise wording

    Confirmed scope: DEMO-NORD included; DEMO-SUD excluded. Other areas: unverified.

    Scroll the table horizontally if needed. With a keyboard, focus the table and use the arrow keys.

    Three checks based on the supplied information
    Starting informationWhat it establishesWhat still needs checking
    Website territoryGeneral publication areaIs it confused with the service area?
    DEMO-NORD in the noticeArea covered by this collectionAre the source and its date accessible?
    DEMO-SUD outside the noticeArea excluded in this scenarioDo the title and summary preserve that exclusion?

    A publication’s coverage area does not automatically become a service’s operating area.

    Separate exclusion from missing information

    Fictional example: the website presents four areas. The notice confirms DEMO-NORD and excludes DEMO-SUD. The supplied file does not establish the status of DEMO-EST or DEMO-OUEST.

    The snapshot contains one inclusion, one exclusion and two unresolved areas. Missing information is not a confirmed exclusion. Keep an “unverified” label until an applicable dated source is available. These reading cards are not a geographical map.

    This workshop uses its own fictional snapshot. Do not combine its figures with those of another example on the page.

    Three different statuses across four fictional areas: included, excluded and unverified. No real local service is described.
    1. Area DEMO-NORD
      Notice coverage
      Included
    2. Area DEMO-SUD
      Notice coverage
      Excluded
    3. Area DEMO-EST
      Notice coverage
      Unverified
    4. Area DEMO-OUEST
      Notice coverage
      Unverified

    The diagram values are listed below with their labels.

    Find the values behind the diagram
    MeasureValue
    Areas presented4
    Areas included in the notice1
    Areas excluded in the notice1
    Areas to verify2
    A person reads a noticeboard in a fictional community space.

    Keep the information consistent

    When to review
    Source or boundary changes
    Who validates
    The editor checks service, area and source date.
    Journey to replay
    Read the notice from an included area, an excluded area and an unverified area; compare the summaries.

    Check an information source →

    Understand an indicator

    Make correction handling visible

    Fictional teaching example: these figures are neither market statistics nor measured client results. They illustrate a calculation and its limits.

    A fictional local newsroom confirms eight necessary corrections during a defined period. Six are published at the reporting time; two still need processing or verification before publication.

    The proportion in this example

    75%6 / 8 × 100

    Corrections published by the reporting time
    6
    Corrections confirmed as necessary
    8

    What this figure means

    75% of corrections recognised as necessary have been published. This does not mean 25% of articles are false or every report received was justified.

    Define the count before comparing

    Distinguish reports, verification, agreed corrections and publication. Record the page and dates without counting the same defect twice.

    The 8 agreed corrections could comprise 6 publications, 1 drafted correction awaiting approval and 1 item still needing verification. Two further unconfirmed reports remain outside this denominator; that does not classify them as unfounded.

    A practical check on the website

    Provide a clear correction notice and update places that repeat the information. Check headlines, article text and links still spreading the old version.

    What the calculation cannot establish

    This rate describes handling at one moment, not the overall reliability of a publisher. Verification delays and error severity need separate review.

    Try with your own counts

    Use two counts from the same group and period, with the same unit. The selected cases must belong to the reference total. Leave unknown values blank.

    Whole counts only, up to one billion. Formula: selected cases ÷ reference total × 100. The displayed percentage is rounded to one decimal place.

    These values stay in this page without being sent or saved. The calculation provides no benchmark, prediction or quality score.

    To document real data, keep its origin, scope and quality limitations clear. Method reference : W3C · Data on the Web Best Practices (in English) · Consulted on . This source does not supply the fictional figures above.

    A content model to maintain

    Connect local information with an identified territory and verified place before reuse. For the exercise, reconcile similarly named places in different municipalities. The administrative boundaries API helps identify municipalities; it does not validate opening hours, a building entrance or a third-party announcement.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    A content model to maintain
    InformationContent to retainConsistency check
    Identified territoryRetain municipality code, name and administrative association from the chosen source with retrieval date. Handle administrative changes before reconciliation.Compare identically named municipalities and a postcode search. Resolve ambiguity without treating a postcode as a unique municipality identifier.
    Place and operatorAssociate a place identifier with a validated address, operator contact and provenance of displayed coordinates. Identify information still awaiting confirmation.Import a place under its full name and an abbreviation: check the match before merging, then ensure the address does not belong to a namesake.
    InformationPrimary source, event date and publication date.An editorial update does not artificially change the event date.
    RevisionCorrection, reason and superseded information.A material correction reaches lists that reuse the information.
    Corrected informationIdentify the responsible organisation, effective date and channels repeating the information.Correct an exceptional opening time, then check the venue page, calendar and internal search result.

    A focused next step

    Prepare a small fictional dataset containing a namesake, possible duplicate and unknown value. Check matches individually, then follow a correction into the page, calendar and search. Keep event date, statistical reference year and collection date separate: each fact requires an appropriate confirming source.

    Public API: municipality data and identifiers — a reference for describing information, not evidence of a particular business or a guarantee of search features. · Source consulted

    A review case to reproduce

    A namesake leads to the wrong town

    Situation to examine
    A town search returns a namesake in another department. The name alone does not distinguish the destination.
    Proposed check
    Test two towns with the same name. Display useful department and administrative identifiers and verify each parent relationship. Do not confuse postal codes with municipality identifiers; document source and date.
    Evidence to retain
    Keep both compared results, identifiers and selection rule. Territorial links reach the selected town rather than a record sharing only its name.
    Fictional finding example
    Search scenario: Saint-Denis in Seine-Saint-Denis has INSEE code 93066; Saint-Denis in Aude has 11339. Their names alone are identical.
    Interpret this outcome
    Show department and identifier before selection. These real commune codes differ from postal codes; the selection error described here is fictional.

    Method reference : W3C — Data on the Web Best Practices · Source consulted

    Method reference : INSEE · Saint-Denis · 11339 · Source consulted

    Method reference : INSEE · Saint-Denis · 93066 · Source consulted

    Learning scenario

    A scenario for planning the user journey

    Preparation exercise: A reader is looking for information for a municipality, consults its source and then compares with the neighboring territory. Use dated public data and keep the administrative identifier, not just the name. Test two homonymous locations and one item missing from the dataset. An absence of data should not be rendered as a certain zero value. The page should explain the actual coverage and offer a link to the source when the reader wants to verify a change.

    Documents and information to prepare

    • Stable administrative identifiers and official names
    • Public source and recovery date
    • Relations between municipality, department and region
    • Definition of fields and units used
    • List of missing or uncovered information

    Acceptance criteria

    These criteria are a working basis to adapt to the context. For each, note the action taken, the expected result, the observed result and the information remaining to be confirmed.

    1. two homonymous municipalities remain distinguishable.
    2. A territorial relationship comes from the dataset and not from the name.
    3. An absent field differs explicitly from the zero value.
    4. The source and recovery date are accessible.
    5. A name change maintains a consistent link strategy.
    6. A page indicates the coverage limits of its data.

    Understand pre-launch checks

    Ongoing management and handover

    Document the import: source, version, number of entries and discarded anomalies. Check credentials before merging similar records. When cutting changes, update the relationships, mesh and old URLs. Local content must remain proportionate to the information available; Adding a generic paragraph to each municipality does not replace a useful and verified data.

    Organize site maintenance

    Compare two approaches

    Local content depends on its scope and updates. Compare a verified editorial selection with a larger database before multiplying pages by town.

    Selection of verified services

    When to choose it
    Suitable when a team can verify a limited set of services. Explain selection criteria and information still awaiting confirmation.
    What to plan for
    Assign a source and owner to each entry. Allow corrections to be reported without automatic publication.

    Structured territorial directory

    When to choose it
    Useful for places with identifiers, categories and usable sources. Link each entry to the territory it actually concerns.
    What to plan for
    Plan how to handle duplicates, closures and address changes. Distinguish administrative data from practical information verified with the service.

    A risk to anticipate

    A municipality name does not prove a business presence there. Specify the services actually covered and avoid unverified contact details or place photographs.

    How to decide

    Choose a pilot territory and check entries end to end. Observe missing information and correction time before extending coverage.

    Explore this decision further

    Compare scope and costs

    Setup
    Compare sources, fields, identifiers and geographical scope before counting pages. A documented import with coherent relationships differs from a set of local texts.
    Recurring operation
    Plan review frequency, change handling and unavailable-source validation. Entry count does not establish checking effort; unknown information must not become invented data.
    Exit and handover
    Request data, provenance and identifier mappings. Check reuse rights and page regeneration; HTML file transfer alone does not restore the update process.

    Compare the costs of three web solutions

    Frequently asked questions

    What if two sources show different population figures?

    First compare reference year, definition, geographic scope and update date. Keep the chosen measure’s label and source. A recent reading date does not make different reference years comparable; explain the difference rather than choose the larger figure.

    How can a postcode be used without confusing it with a municipality?

    Keep postcode, municipality name and administrative code separate when available. A postcode may correspond to multiple municipalities; a form should allow the correct place to be selected before applying service coverage. Preserve leading zeros and check the result’s source and scope.

    How should uncertain practical information be signalled?

    Identify the affected fact and person or source to consult. Correct confirmed closures or changes, and distinguish pending verification from certainty. For hours or access that may change quickly, give readers a relevant way to confirm the situation before travelling.

    Is a public source enough to publish a venue’s opening hours?

    Check what the dataset describes and when it was updated. Seek the venue or service’s own source for practical opening hours. Missing data should remain unconfirmed rather than be inferred from a neighbouring establishment.

    Further reading

    Additional reference: Administrative cutting public API. The sectoral recommendations of this sheet are an editorial method; This reference does not certify the information specific to an establishment.

    Browse other resources