Skip to content

Commit

Permalink
Gwen changes (#261)
Browse files Browse the repository at this point in the history
* Update conservation-area.md (#258)

Made tweaks to documentation-url field guidance

* Update article-4-direction.md (#259)

Tweaked cocumentation-url field guidance

* Update tree-preservation-order.md (#260)

tweaked documentation-url field guidance

---------

Co-authored-by: gwencariad <[email protected]>
  • Loading branch information
eveleighoj and gwencariad authored May 1, 2024
1 parent 667cc73 commit 24cd7e0
Show file tree
Hide file tree
Showing 3 changed files with 46 additions and 8 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -62,11 +62,23 @@ Example: `http://www.LPAwebsite.org.uk/article4direction1.pdf`

### documentation-url

The URL of the webpage citing the document.
The URL of the webpage on your website that introduces the document.

Each document should be linked to on a documentation webpage that includes a short description of the data. The website URL should be unique for each article 4 direction, either by creating a separate page or a separate anchor (fragment identifier) for each one.
Each document should be linked to from a documentation webpage that includes a short description of the data and the document you’re linking to. Each article 4 direction should have a unique URL. This means you can create a separate page for each one, or you could list several on one page. If you do that, there must be a separate anchor link (fragment identifier) for each one.

Example: `http://www.LPAwebsite.org.uk/data#article4direction`
This means each section of your page should have its own URL. Most publishing systems will allow you to use a hashtag to create the identifiers for each article 4 direction you list - as in the examples shown.

Example:

One article 4 direction per page:

`http://www.LPAwebsite.org.uk/data/article4directions/smithroad`

More than one article 4 direction per page with an anchor link for each one:

`http://www.LPAwebsite.org.uk/data/article4directions#smithroad`

`http://www.LPAwebsite.org.uk/data/article4directions#broadhousepark`

### notes

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -59,9 +59,23 @@ If you’re providing geometry in a GeoJSON, GML or Geopackage, use the associat

### documentation-url

The URL of the webpage on the local planning authority website which provides information about the conservation area.
The URL of the webpage on your website that introduces the document.

Example: `http://www.LPAwebsite.org.uk/data#conservationarea1`
Each document should be linked to from a documentation webpage that includes a short description of the data and the document you’re linking to. Each conservation area should have a unique URL. This means you can create a separate page for each one, or you could list several on one page. If you do that, there must be a separate anchor (fragment identifier) for each one.

This means each section of your page should have its own URL. Most publishing systems will allow you to use a hashtag to create the identifiers for each conservation area you list - as in the examples shown.

Examples:

One conservation area per page:

`http://www.LPAwebsite.org.uk/data/conservationareas/smithroad`

More than one conservation area per page with an anchor link for each one:

`http://www.LPAwebsite.org.uk/data/conservationareas#smithroad`

`http://www.LPAwebsite.org.uk/data/conservationareas#broadhousepark`

### notes

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -61,11 +61,23 @@ Example: `http://www.LPAwebsite.org.uk/tpo1.pdf`

### documentation-url

The URL of the webpage citing the document.
The URL of the webpage on your website that introduces the document.

Each document should be linked to on a documentation webpage that includes a short description of the data. The website URL should be unique for each tree preservation order, either by creating a separate page or a separate anchor (fragment identifier) for each one.
Each document should be linked to from a documentation webpage that includes a short description of the data and the document you’re linking to. Each tree preservation order should have a unique URL. This means you can create a separate page for each one, or you could list several on one page. If you do that, there must be a separate anchor link (fragment identifier) for each one.

Example: `http://www.LPAwebsite.org.uk/data#tpo1`
This means each section of your page should have its own URL. Most publishing systems will allow you to use a hashtag to create the identifiers for each tree preservation order you list - as in the examples shown.

Examples:

One tree preservation order per page:

`http://www.LPAwebsite.org.uk/data/treepreservationorders/smithroad`

More than one article 4 direction per page with an anchor link for each one:

`http://www.LPAwebsite.org.uk/data/treepreservationorders#smithroad`

`http://www.LPAwebsite.org.uk/data/treepreservationorders#broadhousepark`

### notes

Expand Down

0 comments on commit 24cd7e0

Please sign in to comment.