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

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.

Frequently asked questions

Does a postal code identify a municipality?

It is used for postal routing and should not replace the administrative code to link datasets.

View data viewed this year as current?

The consultation and the vintage are distinct. Display the year specific to the data when it is available.

Do you need one page per municipality?

only if a distinct and verifiable content justifies it. An index and groupings can better cover a territory without repetitions.

resources to deepen

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 files