Open Data Madrid

• Search datasetsSearch the whole Madrid catalogue by words in a dataset's title, description or tags, and narrow it by category, tag, file format or publishing body. Picking several values for one filter widens the result (any of them matches); filling in different filters narrows it (all of them must match). Leave the words blank to browse a filter on its own - every dataset tagged 'movilidad', say. Each result comes back with its files, formats, licence and when it was last updated.
• List datasetsList the names of the datasets in the catalogue, in the portal's own order. Names only, which is the cheap way to see everything the portal holds - each one goes straight into 'Get a dataset'. Use 'Search datasets' instead when you want the records themselves.
• Get a datasetRead one dataset in full: what it covers, who publishes it, the licence it is released under, when it was last updated, and every file it offers with that file's format, size and download link. Takes the dataset's name, its id, or a link to its page copied from a browser.
• Get related datasetsRead the datasets the portal records as related to one dataset - a parent it derives from, a version it supersedes, or one it links to - together with the kind of relationship and any note the publisher left on it.
• Get a dataset's historyRead one dataset's change history, most recent first: when it was created and each time it has been updated since. This is what a workflow watches to notice that a dataset it depends on has new data.
• List recently updated datasetsRead what has changed across the whole catalogue lately, most recent first, each entry naming the dataset it touched and when. Run it on a schedule to find out what Madrid has published or refreshed since the last time you looked.
• Get a changeRead one entry from a change history by its id, as returned by 'Get a dataset's history' or 'List recently updated datasets': what kind of change it was, which dataset it touched and exactly when.
• Get a fileRead one file's details: its format, its size, whether the portal hosts it or links out to it, and the link to download it. Takes the id 'Get a dataset' returns for each of a dataset's files, or a link to the file's page.
• Search filesFind files across the whole catalogue by one of their own fields rather than by their dataset - every file whose name mentions 'padrón', or every GeoJSON the portal publishes. Pick the field to look in and give the term to look for; one field is matched at a time, which is all the portal offers here.
• List a file's previewsList the previews the portal has configured on one file - a data table, a chart, a map or an embedded viewer - each with its own id and kind. A file with no preview is not an error: it simply comes back empty.
• Get a previewRead one preview on its own by its id, as returned by 'List a file's previews': its title, its description and which kind of viewer it is.
• List categoriesRead every category the portal files its datasets under - transport, environment, population, urban planning and the rest - each with its title, its description and how many datasets it holds. This is the vocabulary the search filter runs on, so it is what a workflow reads to decide which category to follow.
• Get a categoryRead one category's own record: its title, what it covers and how many datasets are filed under it. Takes the category's name or a link to its page.
• Get a category's datasetsRead the datasets filed under one category, each in full with its files and licence. Use 'Search datasets' with a category filter instead when you also want to search within it or to page through a large category.
• Get the category treeRead the categories as a tree rather than a flat list, each one carrying the categories nested beneath it. Use it to show the catalogue's own structure, or to walk from a broad heading down to the narrower ones inside it.
• List tagsRead every tag used across the catalogue, alphabetically. Tags are finer-grained than categories and are what the search filter matches on, so this is how a workflow finds the exact word the portal files something under.
• Get a tagRead one tag by name, with how many datasets carry it. Use it to check that a tag a workflow filters on still exists before searching with it.
• Search tagsFind the tags whose names contain a word, rather than reading the whole list. Useful when you know roughly what the portal calls something - 'bici', 'aire' - but not the exact tag.
• List licencesRead the licences datasets in the catalogue are published under, each with its name, its full text online and whether it is an open licence. This is what a workflow checks against a dataset's licence before reusing its data.
• Suggest namesComplete a partly-typed name against the portal's own vocabulary: dataset names, categories, tags or file formats. Every kind comes back as the same value-and-label pair, so this is what a workflow uses to turn something a person typed into a name the other actions will accept.
• Get follower countCount the people following one dataset or one category on the portal - a rough measure of how much interest it attracts, which is how a workflow picks the datasets worth reporting on.

No actions match that.