1. HALE APPLICATION: THE USECASE OF THE PLU OF THE PROVINCE OF TRENTO ing. Silvia Franceschi ing. Andrea Antonello Inspire conference, Firenze 24th June 2013

2. THE USECASE This use case shows a real example of mapping and transformation of the data of a regional plan of land use between the original (national) and the requested Insprire format. 3. THE DATA The plan is the PGUAP plan of the Province of Trento, approved in February 2006. Two different updates of the geometries of land use are considered for the same plan. Considered data: shapefile of land use: two different updates of this layer are considered, one is the most recent one, approved with a regional decree of February 2013 and the other one was the previous one, approved in July 2011 shapefile of hydro-geomorphological risk maps: only the geometries of the last update main official documentation 4. PLU Province of Trento 5. PLU Province of Trento The attribute table shows the list of attribute and some example of content. The real meaning of the attributes is: AREA: contains the information of the area of each polygon PERIMETER: contains the information of the perimeter of each polygon USO_POL_: contains an ID of the polygons did for old databases USO_POL_ID: contains an ID of the polygons did for old databases COD_TOT: contains the land use classification code PESOPOL: contains the information of the importance of the object for the evaluation of the hydro-geomorphological risk maps PLAN_FROM: contains the date of the approval of the general plan AGGIORN_6: contains the date of the update of the geometries PLAN_NAME: contains the name of the plan 6. PLU Province of Trento 7. PLU TARGET SCHEMA Inspire PLU conceptual schema corresponds to a dataset that corresponds to a spatial planning document. Geographic information as well as the informative or descriptive parts contained in a spatial planning documents are taken into consideration in the LandUse data application schema. Only the spatial planning documents that are or have to be legally adopted by an authority and are opposable to third parties are considered within INSPIRE. 8. PLU TARGET SCHEMA 9. PLU TARGET SCHEMA A spatial planning document corresponds to the featureType SpatialPlan. The Spatial plan has specific attributes related to the name, date of the legal documents, and the level of the administrative hierarchy that has been adopted. 10. PLU TARGET SCHEMA The zoning is composed of polygons that are mutually exclusive. Zoning provide regulations on how LandUse can evolve. The featureType ZoningElement has several specific attributes (nature of regulation, dimension, rules, ) and contains the land use classification in the attribute hilucslanduse. 11. PLU TARGET SCHEMA Supplementary information delimits locations where a specific regulation applies and supplements the regulations of the zoning. Supplementary information is implemented in the featureType SupplementaryRegulation. 12. PLU TARGET SCHEMA Official documentation is in the featureType OfficialDocumentation. 13. HILUCS CLASSIFICATION Inspire requires to classify PLU data following the categories of the HILUCS classification (Hierarchical Inspire Land Use Classification). PLU of the Province of Trento is classified with a local classification. We did the reclassification of all the local (specific) land use classes to hilucs and stored this classification in a CSV file. A classification operation in HALE can be done manually on the flight or loading a CSV file containing the correspondence between the original and the HILUCS classes. 14. HILUCS CLASSIFICATION COD_TOT DESCRIPTION HILUCS CLASSIFICATION 1 Aree Residenziali 5_1_PermanentResidentialUse 2 Aree Produttive 2_SecondaryProduction 3 Aree Ricreative 3_4_4_OpenAirRecreationalArea 4 Aree Agricole 1_1_1_CommercialAgriculturalProduction 5 Improduttivo 6_3_1_LandAreasNotInOtherEconomicUse 6 Campeggi 5_3_OtherResidentialUse 7 Depuratori e Discariche 4_3_3_WasteTreatment 8 Aree Sciabili 3_4_3_SportsInfrastructure 9 Aree a bosco, prato e prateria alpina 1_2_Forestry 101 Strade di importanza primaria 4_1_1_RoadTransport 102 Ferrovie 4_1_2_RailwayTransport 103 Strade di importanza secondaria 4_1_1_RoadTransport 15. DOCUMENTATION Another preliminary operation that would help us during the mapping is the creation of a library of information and links for the documentation of the plan. This information is stored in a CSV file containing the basic properties requested in the Insprire schema for OfficialDocumentation: an identifier legislationCitation: reference to the document that contains the text of the regulation DocumentCitation: citation of scanned plans and structural drawings being sometimes georeferenced and sometimes not (raster images, vector drawings or scanned text). 16. DOCUMENTATION ID DOCUMENTCITATION LEGISLATIONCITATION Doc_1 http://pguap.provincia.tn.it/GIS/tiff/ uso.html http://www.delibere.provincia.tn.it/CercaSpecifi ca.asp? Modalita=Delibere&anno=2013&numero=228 Doc_2 http://www.delibere.provincia.tn.it/CercaSpecifi ca.asp? Modalita=Delibere&anno=2011&numero=1551 Doc_3 http://pguap.provincia.tn.it/pdf/Piano/0IndiceG enerale.pdf 17. MAPPING Now we are ready to start mapping with HALE... 18. ALIGNMENT AND MAPPING The very first operation to do in HALE is to load the source schema, the source data and the target schema. This operation is very easy, select the correspondent element to import from the menu File Import HALE can load source schema from different sources and in particular from shapefiles and CSV files. Considering the source data and the target schema there are different FeatureType that has to be considered in this example, in particular: ZoningElement: contains the information of the geometries of the Land Use SpatialPlan: contains all the information related to the official plan OfficialDocumentation: contains the links and reference for the available documentation SupplementaryRegulation: contains the information of additional regulation which supplement the zoning. 19. ALIGNMENT AND MAPPING 20. ALIGNMENT AND MAPPING The starting Type to map is the LandUse shapefile which contains the basic information for both the ZoningElement and the SpatialPlan. All the mapping is based on the retype operation. Retype function espresses that a source and a target type are semantically equal: for each instance of the source type, an instance of the target type is created. Property relation only take effect in the context of a type relation. First a type relation must be defined, then property relations between the involved types can be specified. 21. ZoningElement do a retype mapping between uso_pol_part and ZoningElement do a rename mapping between the_geom and geometry (choose structural rename) do a date extraction between attribute AGGIORN_6 and validFrom do a rename between COD_TOT and specificLandUse create an Inspire Identifier using the information in USO_POL_ID to generate inspireId 22. ZoningElement assign the other mandatory properties: add assigns to regulationNature (definedInLegislation) add the generate unique ID for id in ZoningElement add assing to hilucsLandUse.codeSpace to http://inspire.ec.europa.eu/codeList/HILUCSValue add reclassification using the CSV list between COD_TOT and hilucsLandUse: since hilucslanduse is a mandatory property it can not be null, so it is important to set the to use for unmapped source values a fixed value, for example 6_6_NotKnownUse add a Groovy script to assign the validTo property to the features of the two different updates: the validTo property is defined as the date before the date of the new update, so it is based on AGGIORN_6 attribute field of the land use shapefile and the syntax is the following: if(AGGIORN_6.equals("2011-07-18")) { return "2013-02-26"; } else { return null;} 23. DateExtraction 24. InspireIdentifier 25. GroovyScript 26. ZoningElement 27. SpatialPlan Considering the same source type it is possible to map the SpatialPlan. In this case a merge operation has to be used to set a relation between the types. Merge function merges multiple instances of the source type into one instance of the target type based on one or more matching properties. 28. SpatialPlan do a merge mapping between land use shapefile uso_pol_part and SpatialPlan using PLAN_NAME use a date extraction to associate the attribute PLAN_FROM to the property validFrom create an Inspire Identifier using PLAN_NAME as reference to generate inspireId do a rename between PLAN_NAME and officialTitle do a rename between PLAN_NAME and id of SpatialPlan do a compute extent of the geometry of the shapefile the_geom to extent in SpatialPlan (boundingbox) add some additional assignment for the mandatory fields of SpatialPlan add assing to levelOfSpatialPlan (regional) add assing to planTypeName (PianoRegionale) 29. ZoningElement 30. OfficialDocumentation A very important request in the Inspire schema for PLU is the link and reference to the official documentatin of the plan. The basic operation to start with here is retype. do a retype between documents and OfficialDocumentation do a rename between documentationCitation and planDocument DocumentCitation DocumentCitation link (choose structural rename) create an Inspire identifier using the information contained in INSPIREID to generate inspireId do a rename between INSPIREID and id of OfficialDocumentation do a rename between legislationCitation and LegislationCitation LegislationCitation link (choose structural rename) add the assignment to the missing mandatory properties add assign to legislationCitation level (SubNational) add the generate unique ID for id in LegislationCitation add the generate sequential ID for name in LegislationCitation (Official_Document_) add the generate unique ID for id in DocumentCitation add assign to name in DocumentCitation (Trentino Planned Land Use) 31. GenerateSequentialID 32. OfficialDocumentation 33. LINK BETWEEN TYPES Link between ZoningElement and SpatialPlan Since all land use polygons are part of one plan we can use directly assign operation to assign to plan href in ZoningElement the name of the reference plan. Link between SpatialPlan and OfficialDocumentation Since all the documents included in the OfficialDocumentation are related to the plan it is necessary to link all of them to SpatialPlan officialDocumentation href. In this case we have to create two other new instances of the same property officialDocumentation and assign to each of them the link to the documents using the # before the name of the document (i.e. #Doc_3) 34. LINK BETWEEN TYPES Link between ZoningElement and OfficialDocumentation Use a groovy script to assign the reference to the officialDocumentation of the features in ZoningElement, since ZoningElement contains two different update of the land use polygons, the official documentation will be different for the two and it is based on the date of the update contained in the attribute AGGIORN_6. The two entities are AGGIORN_6 and officialDocument href of ZoningElement, the script is: if(AGGIORN_6.equals("2011-07-18")) { return "#Doc_2"; } else { return "#Doc_1";} where #Doc_1 and #Doc_2 are the reference to the ID of the two documents as inserted in the OfficialDocumentation. 35. OfficialDocumentation 36. SupplementaryRegulation The last information to be mapped is the additional regulation on hydro- geomorphological risk mapping. This information is stored in an other shapefile and the retype operations is used to map the contained elements to SupplementaryRegulation. do a retype mapping between rispol_part and SupplementaryRegulation do a rename mapping between the_geom and geometry (choose structural rename) create an Inspire Identifier using RISPOL_ID as reference to generate inspireId do a rename between RISPOL_ID and id of SupplementaryRegulation do a date extraction between attribute UPDATE and validFrom do a rename between CLASSE and specificSupplementaryRegulation codeSpace add some additional assignment for the mandatory fields of SupplementaryRegulation add assign to regulationNature (generallyBinding) add assign to supplementaryRegulation (2_1_2_FloodRiskManagementZone) add assign to supplementaryRegulation codeSpace http://inspire.ec.europa.eu/codeList/SupplementaryRegulationValue 37. LINK BETWEEN TYPES Link between SupplementaryRegulation and SpatialPlan Since all risk zones polygons are part of one plan we can use directly assign operation to assign to plan href in SupplementaryRegulation the name of the reference plan. Link between SupplementaryRegulation and OfficialDocumentation Since all risk zones polygons are part of the same update of the land use plan we can use directly assign operation to assign to officialDocument href in SupplementaryRegulation the name of the reference documentation (#Doc_1). 38. SupplementaryRegulation 39. SupplementaryRegulation 40. silvia.franceschi@hydrologis.eu