Source and endpoint scenarios

psd
recent  |  interesting  |  random  |  favorites  |  contacts  |  sets  |  tags:  
Source and endpoint scenarios
Source and endpoint scenarios

The source page is the place to go to check the information. This is typically the planning policy page.
There's one source for each "provision" (organisation/dataset)
Source pages aren't typically in the National Archives or internet archive. Ideally we should capture these pages for history (one for the roadmap/backlog).
The endpoint is a link to download data (resource). It has a URL and some parameters. The datasets to process the downloaded resource belong to the endpoint, not the source.
Some sources have multiple endpoints, eg when a brownfield-land register is published each year.
Some sources the endpoint provides different resources as the data is updated.
Many LPAs put the endpoint on a separate page to the source information. The source should link to this page to help people find the data, and increase the trust the data matches the information and is published by the LPA.
There are other patterns we can establish for the endpoint, including a feed as well as a snapshot (currently the most common mode for most sources)
Some LPAs have linked to a national secondary source for their authoritative local data. This is complicated and led to source and endpoint being separated and processing to extract the LPA's entities from data about other LPAs. We think this pattern might be something we can no longer support.
Some LPAs jointly publish authoritative data, eg a joint local plan or joint website. This can be allowed, but makes the model and processing much more complicated.
A source page may contain information about multiple datasets, eg Article 4 Directions and Conservation areas are often published on the same page.
An endpoint may contain data about several different datasets. TPOs often contain denormalised data about the areas or trees.
We support zipfiles containing a single file to be processed, but don't currently support processing multiple files from a zipfile.
We should keep multiple entries for changes to the source and endpoint, but only one source (dataset/organisation) and one endpoint-url should be active at any time (not have an end-date)

Attribution Some rights reserved
Taken on: May 10, 2024
Sets appears in:   • Digital Land   
Camera: Google Pixel 6a, f/1.7, 1/150 sec, 4.4mm, ISO 56 (more info) (hide info)
Camera: Google Pixel 6a
Aperture: f/1.7
Exposure Time: 0.007 sec (1/150)
Focal Length: 4.4mm
ISO: 56
Exposure Bias: 0 EV
Flash: Off, Did not fire
Exposure Program: Program AE
Exposure Mode: Auto
Metering Mode: Center-weighted average
White Balance: Auto
Color Space: sRGB
Software: Google
Show full info
Stats: 156 views