A new version of the desktop validator test/beta version, 2.0.5, has been released. It brings the following changes:
Validation for files with gpkg extension has been introduced, you can select the geopackage file in the same way as the zip archive is selected.
The texts appearing in the interface have been modified:
- "Validate zip archive" -> "Validate geopackage or zip archive files"
- "Choose zip archive:" -> "Choose geopackage file or zip archive:"
- "Choose document type:" -> "Choose plan type:"
- "Validate zip archive:" -> "Validate geopackage file or zip archive:"
The process by which rules are validated has been modified so that:
- Rules that validate a single column or something specific (e.g., if geometries contain elevation) a list of ids that is limited to 250 ids will be displayed in the "Verify" column of the validation report. If the number of ids that are affected or wrong exceeds 250, the text "The first 250 affected records are:" followed by 250 affected ids is added.
- Rules that validate multiple columns or something more generic (e.g. if in layer x the columns contain the correct data) will display a list of ids in the "Check" column of the validation report that is limited to 100 ids. If the number of ids that are affected or wrong exceeds 100, the text 'The first 100 affected records for column x are' followed by 100 affected ids is added.
- For all rules that used to display a list of ids in the "Check" column of the validation report, ids are now checked and the uniqueness of each id is ensured.
These changes affected the following rules:
For the validation of the PUG:
- Rules that validate whether in the gpkg file layer its columns contain the correct data (rules with numbers 113 - 123).
- The rules that validate if the date on which the documentation is validated is within the range of the temporal dates inside the layers (rules with numbers 124 - 129)
- Rules that validate if the correlation of the hilucs in the layers ZFExisting/ZFPused is correct (rule numbers 130 and 131)
- Rules that validate whether the codes match in the layers specified for the rule (rule numbers 132 to 135)
- Rules that validate if the value of the geometries is NULL (rule numbers 146 to 154)
- Rules that validate if geometries are valid (rules with numbers 164 - 172)
- Rules validating if layers are in PlanSpatial (rules with numbers 175, 176, 216 - 221)
- Rules that validate if the geometries in the layers ZFExisting/ZFPPlayers overlap (rules with numbers 179, 180)
- Rules that validate whether the geometries in the ZFExistence/ZFPropusa layers are sliver polygons (rules with numbers 181, 182)
- Rules validating whether the columns ZF_Code - ZF_Type and ZF_Code - ZF_Type have identical values in the layers ZFPFropused and ZFExisting (rules with numbers 185 - 188)
- Rules validating whether the columns ZZF_Code - ZZF_Type and ZZF_Code - ZZF_Type in the layers PFAAtypology, ExistingAtypology and AdditionalRegulationArea match the typology (rules with numbers 189 - 191)
- Rules that validate if the values of type Date From are the same throughout the column of the specified layer (rule numbers 192, 193)
- Rules that validate that the geometries contain the correct coordinates (rule numbers 194 - 202)
- Rules that validate if the geometries have the same area or length as specified in the area or length column of the layer (rules with numbers 203 - 210)
- Rules that validate whether the combination of Code and Type in one layer conforms to the data coming from another layer (rule numbers 212 - 215)
- Rules that validate whether the time data in one layer matches the time data in another layer (rules numbers 222 - 225)
- Rules that validate whether the time periods in the layers ZFPropuse and ZFExistence are correct (rules with numbers 226, 227)
- Rules validating whether diacritics are correct in the specified layer (rules with numbers 228 - 232)
To validate the PUZ:
- Rules that validate whether in the layer the gpkg file's columns contain the correct data (rules with numbers 113 - 123).
- Rules that validate if the date on which the documentation is validated is within the range of the temporal dates inside the layers (rules with numbers 124 - 129)
- The rules that validate whether the correlation of hilucs in the ZFExisting/ZFPropused layers is correct (rule numbers 130 and 131)
- Rules that validate whether the codes match in the layers specified for the rule (rule numbers 132 to 135)
- Rules that validate if the value of the geometries is NULL (rule numbers 146 to 154)
- Rules that validate if geometries are valid (rules with numbers 164 - 172)
- Rules validating if layers are in PlanSpatial (rules with numbers 175, 176, 216 - 221)
- Rules that validate if the geometries in the layers ZFExisting/ZFPPlayers overlap (rules with numbers 179, 180)
- Rules that validate whether the geometries in the ZFExistence/ZFPropusa layers are sliver polygons (rules with numbers 181, 182)
- Rules that validate whether codes are unique in the Code_ZF_ZRS_ZRS Code/Cod_SZF_ZRS_D columns of the RLU/RLUD layers (rules with numbers 183, 184)
- Rules validating whether the columns ZZF_Code - ZZF_Type and ZZF_Code - ZZF_Type in the layers PFAAtypology, ExistingAtypology and AdditionalRegulationArea match the typology (rules with numbers 189 - 191)
- Rules that validate if the values of type Date From are the same throughout the column of the specified layer (rule numbers 192, 193)
- Rules that validate that the geometries contain the correct coordinates (rule numbers 194 - 202)
- Rules that validate if the geometries have the same area or length as specified in the area or length column of the layer (rules with numbers 203 - 210)
- Rules that validate whether the combination of Code and Type in one layer conforms to the data coming from another layer (rule numbers 212 - 215)
- Rules that validate whether the time data in one layer matches the time data in another layer (rules numbers 222 - 225)
- Rules that validate whether the time periods in the layers ZFPropuse and ZFExistence are correct (rules with numbers 226, 227)
- Rules validating if diacritics are correct in the specified layer (rules with numbers 228 - 232)
The use Local Data platform, hereinafter referred to as the "Platform" implies full acceptance of the terms and conditions set out below.
The Terms and Conditions may be modified at any time by the administrator of the platform, hereinafter referred to as the "Administrator", without prior notice to the persons using the platform, hereinafter referred to as "Users". The Administrator of the Local Data platform is the Ministry of Development, Public Works and Administration (MDLPA), which may act for the management of the platform through one or more economic operators, on the basis of a contractual relationship.
Account means a personalized profile created on the Platform that allows access to its functionalities according to the role of each user. "User" can be any person who requests access for himself/herself or as a representative or proxy on behalf of a public authority and who has an account activated on the Platform and uses its services. By accessing and using the Local Data Platform, Users implicitly accept the terms of use described below. The term "Data" refers to all information collected, stored and processed through the Platform.
Users will have permanent access to the terms and conditions for the use of the services so that they can consult them at any time. If they do not agree with the terms and conditions imposed, users must cease accessing this platform.
These terms and conditions govern the use of the Local Data platform and are governed by and construed in accordance with the laws of Romania.
a) The National Register for Spatial Planning and Urban Planning Documents (PLANURB), realized on the basis of the provisions of Law no. 350/2001 on Spatial Planning and Urban Planning, with subsequent amendments and additions.
b) Participatory planning tool, which facilitates the information and consultation of citizens on spatial planning and urban planning documents, pursuant to the methodology for informing and consulting the public on the development or revision of spatial planning and urban planning plans, approved by MDRT Order no. 2701/2010, as amended and supplemented.
c) Register with the situation of the local transportation network (MDRET), containing the inventory and the state of the roads, based on the provisions of H.G. no. 540/2000 on the approval of the classification into functional categories of public roads and private roads open to public circulation, with subsequent amendments and additions.
For more information on the functionalities of the Local Data platform, please consult the About.
a) We are committed to protecting users privacy and complying with all applicable data protection laws.
b) For detailed information on how we collect and use data, please see our privacy policy.
a) We take reasonable steps to protect user data against unauthorized access, use or disclosure.
b) However, Users understand and accept that no data transmission over the Internet is completely secure and that the Administrator cannot guarantee the absolute security of data transmitted through the Platform.
c) The administrator shall implement appropriate technical and organizational measures to protect data against unauthorized access, loss, alteration or destruction.
d) Users are obliged to comply with all privacy and security policies of the Platform and not to disclose confidential information to third parties without the prior consent of the Administrator.
a) Users are responsible for maintaining the confidentiality of their login information and for all activities conducted under their account.
b) The data collected through the Platform will be used exclusively for the stated purposes, for activity logging and aggregated statistics.
c) The administrator will take appropriate measures to ensure the confidentiality and security of the data collected, in accordance with applicable law.
d) Users agree not to use the data collected through the Platform for purposes other than those authorized by the Administrator.
a) User accounts are created and managed by the Platform Administrator. Each user will receive a specific role that determines access rights and permissions within the Platform. Roles are assigned based on operational needs as determined by the Administrator. Users must provide correct and complete information when creating their account and update it whenever it changes.
b) It is prohibited to use access to the Platform in any way that causes or may cause damage to the Platform or affects its availability or accessibility, in any way that is unlawful, fraudulent or harmful or in connection with any unlawful, fraudulent or harmful purposes.
c) Users are prohibited from reproducing, duplicating, copying or exploiting material or information on the Platform for a commercial purpose (unless the content is specifically made available for redistribution).
d) It is forbidden to use the Platform to copy, store, host, transmit, send, use, publish or distribute any material or information consisting of (or related to) any software products (spyware, computer virus, Trojan horse, worm, keylogger, rootkit, etc.) that may cause partial or total destruction or alteration of the organization or content.
e) All intellectual property rights relating to the Platform and its content belong to the Administrator and are protected by copyright and other relevant laws.
f) Users may not copy, distribute, modify or create derivative works based on the Platform or its content without the prior written consent of the Administrator.
g) Access to the Platform is restricted and based on authentication through secure credentials. Users are obliged to keep these credentials confidential.
h) Users are responsible for all activities conducted under their accounts and for maintaining their security.
i) The Platform is intended for both internal and external use by Authorized Users with accounts created and roles assigned according to the operational needs determined by the Administrator.
a) Access to certain computer resources provided by the Administrator may be restricted. The Administrator reserves the right to restrict Users access to the Platform at any time and without prior notice.
b) For Users who have username and password-based access to the Platform for access to restricted or confidential IT resources and services, they are responsible for ensuring that the password is confidential. Users shall notify the Administrator in writing as soon as possible after becoming aware of any unauthorized use of their account.
c) The User is responsible for any activity associated with the use of the Platform arising from a failure to keep access credentials confidential and may be held liable for any losses resulting from such failure.
a) The Administrator may suspend or terminate a User access to the Platform at any time, without notice, if it believes that the User has violated these terms and conditions or if the User is conducting unauthorized activities.
b) Users can request to close their account at any time and the associated data will be handled in accordance with the Data Privacy Policy.
The platform administrator declares the following:
a) will use all reasonable efforts to achieve the stated purposes of the Platform.
b) will make every effort, technical or otherwise, to ensure the smooth operation of the Platform. However, depending on various foreseen or unforeseen circumstances, there may be interruptions in the operation of the Platform for an indefinite period of time for any reason.
c) the Administrator may amend the terms and conditions of use of the Platform as and when new situations of any kind arise that so require.
d) Users are entitled to access and use the Platform in accordance with these Terms and their assigned roles.
e) The Administrator is not responsible for errors, omissions or other problems resulting from the use of data collected through the Platform, to the extent permitted by law.
Users are obliged to:
a) Use the Platform in accordance with applicable law and these Terms.
b) Do not take actions that could compromise the security and integrity of the Platform.
c) Immediately notify the Administrator of any unauthorized use of their account or other identified security breaches.
d) Users are responsible for the accuracy and integrity of data entered and for complying with all applicable rules and regulations.
Our website uses essential cookies that are necessary for the proper functioning of the site. These cookies ensure basic functionalities and security features, such as maintaining your session and enabling you to navigate through the website. Without these cookies, the website may not perform as smoothly as intended.
What are cookies?Cookies are small text files that your web browser stores on your device to save information about your online preferences and activities. They make navigating the site easier and give you a more personalized experience.
How do we use cookies?We use cookies to understand how you interact with our website and to provide you with a better experience. These may include session cookies (which are automatically deleted when you close your browser) and persistent cookies (which remain on your device until they are manually deleted or expire).
How can you manage cookies?You can manage your cookie preferences through your browser settings. Most browsers allow you to block or delete cookies. However, please note that blocking cookies may affect your experience on the site.
We would like to inform you that the Regulation 2016/679/EU on the protection of individuals with regard to the processing of personal data and on the free movement of such data (GDPR) has entered into force and has been adopted, in a unitary manner, by all the EU Member States, as of May 25, 2018 .
In accordance with Article 13, Information and access to personal data, of the GDPR, we wish to inform you about the purposes for which we process your personal data and about your rights regarding the protection of personal data.
Personal data, namely name, surname, e-mail address and telephone number (users - legal or appointed representatives of local public authorities, national public), are used exclusively for the fulfillment of the MDLPA (DGDRI) tasks regarding the retrieval of spatial planning and urban planning documents in the Local Data platform (part of the Territorial Observatory), respectively for ensuring the necessary conditions for the implementation of the methodology for informing and consulting the public on the development or revision of spatial planning and urban planning plans, in compliance with the legislation in force, strictly for the fulfillment of the intended purpose.
Taking into account the provisions of Law no. 350/2001 on spatial planning and urbanism, with subsequent amendments and additions,
In accordance with the provisions of OMDRAP no. 233/2016 for the approval of the Methodological Norms for the implementation of Law no. 350/2001 on spatial planning and urbanism and for the elaboration and updating of urban planning documents, with subsequent amendments and additions,
Taking into account the provisions of OMDRT no. 2701/2010 for the approval of the Methodology for informing and consulting the public on the elaboration or revision of spatial planning and urban development plans, with subsequent amendments and additions.
MDLPA will process your personal data such as: name and surname, e-mail address, telephone number, etc., mentioning that that we do not process this data for any purpose other than that provided by law and mentioned above.
We would like to inform you that MDLPA does not transfer this data to any other European Union country or to a third state.
You also have the "right to be forgotten", the right to delete your data, by notifying us 30 days before the legal retention period expires.
At the same time, your data will be stored in our database for a maximum period of 5 years, in accordance with the legislation in force.
According to the General Data Protection Regulation 679/2016, you have the following rights:
All these rights can be exercised by sending a notification to one of the following e-mail addresses: datelocale@mdlpa.gov.ro or observator@mdlpa.gov.ro, or directly at our headquarters in: 16 Libertății Boulevard, North Side, sector 5, Bucharest, postal code 050706.
In addition, for any information related to the processing of your personal data by the MDLPA, you can contact the Data Protection Officer at the email address: datepersonale@mdlpa.gov.ro, or at the address Bulevardul Libertății, nr.16, Latura Nord, sector 5, Bucharest, postal code 050706.
Complaints about the processing of personal data can be addressed to National Supervisory Authority for Personal Data Processing.