-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feedback on Location Entity Attributes #133
Comments
location.addressPosition: |
location.adressRepresentationType: |
Thank you very much for commenting on location.addressPosition and location.adressRepresentationType, @VPiersonSWDE. location.addressPosition was added due to the fact that some water companies had attributes such as "Left", "Right" or "In front" in their data models which should refer to the position of a hydrant in relationship to a hydrant.signage or other object in the vicinity of a particular hydrant. Please let us know if this attribute should be removed from the model due to irrelevance or if you agree that it is included. location.adressRepresentationType, this attribute would provide more information regarding the area in which a hydrant is located (e.g., a "commercial area", which might indicate that there will be a lot of civilians in the vicinity of the hydrants in this area). How it should be filled in is to be decided by all group members, in case it has been decided to keep this attribute. As this is merely a suggestion, please let us know if you believe this attribute should be removed from the model due to irrelevance. |
Bonsoir, Sur ce point, vous pouvez déjà remarquer que mise à part le ou les tuyaux, l'intervenant ne doit pas prendre le même matériel pour se raccorder à une bouche ou à une borne. location.addressPosition: Pour moi ce n'est pas utile. Quand j'ai développé CAOPS pour les zones VHP et WAL, j'ai privilégié l'image à la lecture d'une géo donnée. Il est plus facile de transmettre des infos en les regardant qu'en les lisant. En résumé, les données les plus importantes sont pour moi:
|
Dear @Freddy-Theis-Zone-VHP , thank you for your contribution.
We noted down the differences between above- and below ground hydrants and we refer you to this comment, where it's addressed #132 (comment) In regards to the list of most important attributes for cartography that you provided, we would like to confirm with with you that they are already included in the model. Here is a brief summary;
In the Hydrant Entity #132, you can also already find the following:
|
Apart from the input we received from Vivaqua regarding #132, we also received attributes concerning location:
Furthermore, Vivaqua has the following attributes, which are not in our model:
|
Through Zone VHP, we received the following insights:
We kindly ask the working group whether they agree with these insights. |
We have initiated the public review of the ICEG Hydrants model. We appreciate all the feedback we received within this conversation and want to notify that everything has been addressed in the model, which can be accessed via the following link: https://belgif.github.io/thematic/models/hydrants/index_en.html We advise you to review the model internally and welcome any final adjustment requests or suggestions you may have. Kind regards, |
We would like to request feedback from the community on the Location entity attributes in the ICEG Data Model. Specifically, we would like to know if the following attributes for this entity are sufficient to cater for various use cases or if there are any attributes that are missing:
Attributes:
Attributes originating from BeST Address:
In addition, we would like to know if the community would prefer any of these attributes to be optional or mandatory and what the cardinalities should be. We would also like to know if the community would be able to provide all the mandatory information, and with data minimization in mind, or if some of the entities and/or attributes should be stripped off.
Please share your feedback and suggestions so that we can improve the ICEG Data Model. Thank you in advance for your valuable input!
The text was updated successfully, but these errors were encountered: