This is a Linked Data resource, but we don't visualise this kind of data at the moment. You can explore the RDF for more details: see the API tab.

This is a linked data resource: it has a permanent unique uri at which both humans and machines can find it on the Internet, and which can be used an identifier in queries on our SPARQL endpoint.

Agent http://opendatacommunities.org/def/ontology/planning/pins-appeals/Agent

Mr Ilker Kilich xsd:string

Appeal Type Reason http://opendatacommunities.org/def/ontology/planning/pins-appeals/ApReType

LPA's service of an Enforcement Notice http://opendatacommunities.org/def/concept/pins/ApReType/ApReType057

Appellant http://opendatacommunities.org/def/ontology/planning/pins-appeals/Appellan

MR SEYFI BULENT BEDIRGIL xsd:string

Bespoke Indicator http://opendatacommunities.org/def/ontology/planning/pins-appeals/BespIndi

false xsd:boolean

Decision http://opendatacommunities.org/def/ontology/planning/pins-appeals/Decision

Notice upheld http://opendatacommunities.org/def/concept/pins/Decision/DecisionType009

Decision Date http://opendatacommunities.org/def/ontology/planning/pins-appeals/DeciDate

2018-02-07T00:00:00 xsd:datetime

Development Or Allegation http://opendatacommunities.org/def/ontology/planning/pins-appeals/DevOrAle

Without planning permission, the unauthorised erection of a front, side and rear boundary wall, railings and piers. xsd:string

Development Type http://opendatacommunities.org/def/ontology/planning/pins-appeals/DevoType

Householder developments http://opendatacommunities.org/def/concept/pins/DevoType/DevoType002

Enforcement Grounds http://opendatacommunities.org/def/ontology/planning/pins-appeals/EnfGrod

(a),(c),(f) xsd:string

Enforcement Grounds Count http://opendatacommunities.org/def/ontology/planning/pins-appeals/EnfGCnt

3 xsd:integer

Inspector Name http://opendatacommunities.org/def/ontology/planning/pins-appeals/InspName

Brown Stephen Mr xsd:string

Jurisdiction http://opendatacommunities.org/def/ontology/planning/pins-appeals/Jurisdic

Transferred xsd:string

Link Status http://opendatacommunities.org/def/ontology/planning/pins-appeals/LinkStat

Lead xsd:string

Number Of Residences http://opendatacommunities.org/def/ontology/planning/pins-appeals/ResCount

0 xsd:integer

ONS LPA Code http://opendatacommunities.org/def/ontology/planning/pins-appeals/LADCD

Enfield E09000010 http://opendatacommunities.org/id/geography/administration/lonb/E09000010

Procedure http://opendatacommunities.org/def/ontology/planning/pins-appeals/Procedure

Written Representations http://opendatacommunities.org/def/concept/pins/Procedure/Procedure003

Received Date http://opendatacommunities.org/def/ontology/planning/pins-appeals/RecdDate

2017-04-27T00:00:00 xsd:datetime

Reference http://opendatacommunities.org/def/ontology/planning/pins-appeals/CaseRef

3174601 xsd:integer

Site Address 1 http://opendatacommunities.org/def/ontology/planning/pins-appeals/Address1

1 Games Road xsd:string

Site Postcode http://opendatacommunities.org/def/ontology/planning/pins-appeals/Postcode

EN4 9HN xsd:string

Site Town http://opendatacommunities.org/def/ontology/planning/pins-appeals/Town

BARNET xsd:string

Start Date http://opendatacommunities.org/def/ontology/planning/pins-appeals/StarDate

2017-09-11T00:00:00 xsd:datetime

Type rdf:type http://www.w3.org/1999/02/22-rdf-syntax-ns#type

Planning Inspectorate Planning Appeal case http://opendatacommunities.org/def/ontology/planning/pins/Appeal

Type - Detail http://opendatacommunities.org/def/ontology/planning/pins-appeals/TypeDet

Unknown http://opendatacommunities.org/def/concept/pins/TypeDet/TypeDet015

Type of Appeal http://opendatacommunities.org/def/ontology/planning/pins-appeals/AppealType

Enforcement Notice http://opendatacommunities.org/def/concept/pins/AppealType/AppealType006

Valid Date http://opendatacommunities.org/def/ontology/planning/pins-appeals/ValiDate

2017-09-11T00:00:00 xsd:datetime

In addition to this bookmarkable html page, this metadata about this linked data resource is also available for our robot customers in the following machine-readable formats. Please refer to the API documentation for more details.