-
Notifications
You must be signed in to change notification settings - Fork 2
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
🖥Smart Maps Documentation Sub-working group #119
Comments
@albertkun Thanks your your contribution! Do you think it is a good idea to include other outreach items such as #88 and #115 to "Documentation Sub-working group", or shoud we think about them separately? |
@hfu You are welcome! Thank you for providing a positive and welcoming space! Personally, I think it depends if we want to use the Documentation as either: Under a) yes! It would make sense to pull together all outreach material, like #88 and #115, and share the process of how Smart Map does stickers and community cards. With b) the documentation would be more limited to explaining and training on how anyone can use the deliverables that the DWG7 is working on, like UNVT or the Smart Map Bazaar. We can also combine the two a) + b) but, I think a key for successful documentation is knowing who it is for, so we can target those people first. Your input as the lead on DWG7 would be extremely valuable on how you think we should proceed! |
Thank you, @albertkun. I tend to like to write documentation which only we can write like a project document. In addition, I tend to focus on developer happiness rather than capacity building. So my initial idea is a) above. On the other hand, I suppose @ubukawa is a good document writer for capacity building as in b). I see he is also a motivated writer to help and train others. Another suggestion is that we can more casually document by sharing idea sketches and work logs so that we developers can motivate each other. I named this concept 伝習 (Denshu) but I would say that this approach was not a big success. I personally like to follow a) where we write the document for existing and future DWG 7 participants. |
@hfu Thank you for your thoughtful reply! I like the idea of a) as above and would love to also include 伝習 as well for existing and future DWG 7 participants. Even by going with a) we can still make b) a sub-section of the documentation. Overall, this is a good start to focusing in on the content! |
@hfu @yuiseki For the time being, as a proof of concept, can I copy some of the content over from the Wiki and Objective 7 repository? |
@albertkun Of course, you are most welcome! Objective 7 repository is MIT License, so you can redistribute it freely! |
@albertkun Of course there is no problem to make a copy and improve the Project document. I really appreciate your effort. Meanwhile, I was thinking about using ChatGPT to summarize the Project document ;-) |
Yes, '7-docs' would be a good name. I invited @albertkun to the 'unopengis' organization with an owner role. |
@hfu Thank you very much! I'll get started just putting together existing resources so that when the Documentation sub group meets we can discuss how to improve it! 🙂 |
Dear @albertkun For your informaiton, I wrote my Qiita articles for the following audiences:
I think that the term "Smart Maps" can cover various things, and it is not practical to develop all documents for all the topics. As you already discussed, I think starting from the possible audiences and training would be a good idea. I look forward to working with you!! |
Thank you for your support and feedback @ubukawa ! No problem about your transition period! I agree that "smart maps" can mean various things, including the UN Vector Tile initiative! We should make sure to have a place to put your helpful training, so it is great that you will be helping us to work on the Documentation! Excited to be working with you!! |
For those interested, the documentation repository is: The current documentation (beta) is here:
|
I created a separate issue on the working meeting at #137. |
Thank you for creating the separate issue @hfu! Will follow-up on it! |
Forgive me for writing one-sidedly about my thoughts. What we are doing in this working group is in fact very diverse and complex, but it may be easier to understand if we divide it into the following layers, as in the OSI model, for example Layer 1: GIS data format layer
Layer 2: GIS data construction, persistence, and retrieval layer
Layer3: GIS data conversion and processing layer
Layer 4: GIS data distribution layer
Layer 5: GIS data presentation layer
The official documentation and official wiki are the most organized and complete in terms of individual documentation for each layer. I think the point of writing our own documentation is to help the reader quickly understand each layer and the connections between these layers, to see the big picture of Smat Maps, and to be able to reach existing resources and explore them on their own. In other words, a common map, a big picture map about Smat Maps are what we should be written. |
@yuiseki Thank you very much for sharing your thoughts and providing a very detailed approach! I appreciate the summary of the objectives in the big picture level and the OSI connection you showed! I agree that we shouldn't replicate what's already on official documentation, but rather (like you said) focus on how the layers are connected. The initial proposal was to create a hub for smart map related projects and use cases to show the bigger "what is smart maps" picture! I think we are in agreement, but let me know if you have any other comments or questions! I hope you can join us for our meeting on Friday #137! |
I'm obsessed with making large-scale language models contribute to humanity, so I developed something like this! Introducing TRIDENT, an UN dedicated interactive document exploration and humanity assistance system.
EDIT(2023-04-28T10:42+0900):
This system does not write texts like ChatGPT instead of having limited capacity, so the chances of lying are extremely low. I release this system as free and open source software: Although not related to GIS, apart from TRIDENT, I have developed and operate a system called OPTIMIZER, which explores and summarises the welfare programs of the Tokyo Metropolitan Government's municipalities. https://optimizer.yuiseki.net/ This means that it is technically possible to not only search existing documents, but also to have them concisely summarised, depending on the user's requirements. Key points:
|
Looks like we can close this issue because we are in the next stage. First engine cut-off. |
Purpose
Implementation
Material Mkdocs](https://squidfunk.github.io/mkdocs-material/)Existing Resources
Volunteers
Next steps
The text was updated successfully, but these errors were encountered: