Commit 5f591661 authored by Myriam Guedey's avatar Myriam Guedey
Browse files

Clone UGL website

parent 24612f40
Pipeline #8563 canceled with stage
image: alpine:latest
pages:
stage: deploy
script:
- echo "Deploying to https://transfer.hft-stuttgart.de/pages/$CI_PROJECT_PATH/"
artifacts:
paths:
- public
only:
- master
# website # Urban Geoinformatics Lab @HFT Stuttgart Web Page
Website for Geoinformatic Research Group (Prof. Coors)
#### URL (1): https://ugl.hft-stuttgart.de/
#### URL (2): https://transfer.hft-stuttgart.de/pages/ugl/website/
## Getting started
# How to Add contents?
To make it easy for you to get started with GitLab, here's a list of recommended next steps. 1. Contact admin (Joe/Sven/Habib) to get developer access.
2. Add content following this [instruction](https://transfer.hft-stuttgart.de/gitlab/ugl/website/-/wikis/home).
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! 3. Commit/Push changes.
## Add your files ## Team
- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files | Member | Responisble |
- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command: | ------------- | ------------- |
| Joe | Web Dev.: Merger / Overall/ Debugging |
``` | Patrick | Web Dev.: |
cd existing_repo | Sabo | Web Dev.: EXCEL to JSON/BIBTEX |
git remote add origin https://transfer.hft-stuttgart.de/gitlab/zedflow/website.git | Habib | Legal right, Contact point, Domain and SubDomain |
git branch -M master | Sven | QC & Tutoring |
git push -uf origin master
``` ## Meeting Note 27-04-2021
## Integrate with your tools ### Tasks for Patrick:
- [ ] In the current "add_paper.js", all BIBTEX buttons share the same ID and not work yet. I will hide this feature for now and add it back when the BIBTEX is read made. (for later)
- [ ] [Set up project integrations](https://transfer.hft-stuttgart.de/gitlab/zedflow/website/-/settings/integrations) - [x] Currently, I have set in the public/js/config.js the max number of the paper lists. We have to implement the "show more"/ "Pagination" feature. (Patrick)
- [x] Make sure the Search feature works. (Patrick)
## Collaborate with your team - [ ] Currently, the "public\js\language.js" only translate some part of the webpage.(later..)
- [ ] Bug: in English version, it starts with German text in some part.
- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) ### Tasks for Joe:
- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) - [x] fixing the Callback Logic on the Publication Section
- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/) - [ ] Documentation on how to add contents to the web.
- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html) - [x] Upgrade the `public/js/add_paper.js` to support the `URL` and `PDF` link.
- [x] Team Section
## Test and Deploy - [ ] Combine all scripts together + maintaining the GIT.
Use the built-in continuous integration in GitLab.
### Tasks for Sabo:
- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html) - [x] Citation Sheet to BIBTEX. [public/js/parse_json_to_bib.js](public/js/parse_json_to_bib.js)
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/) - [ ] Get in touch with Sushant regarding the issue you found on the citation sheet.
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html) - [ ] After Sushant had updated and added the "PDF_Link" to the citation sheet, you would have to update the script to convert "Sheet1.xlsx to the paper.json format" and correct the "pdf" key pair.
- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html) ### Tasks for Sven:
- [ ] Draft for sub-title in all sections.
***
### Tasks for Sushant
# Editing this README - [ ] Final Citation Sheet + Images
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template. ## Issue
- [x] The GitLab Page does not load the image under the img folder correctly e.g. https://ugl.hft-stuttgart.de/img/Schneider_2018_02.jpg which is stored at as Schneider_2018_02.JPG (Fixed by saving as either .jpg or .JPG everywhere) [03-05-2021]
## Suggestions for a good README - [ ] The flag still does not work yet. May be we can use this feature: https://mojoaxel.github.io/bootstrap-select-country/index.html (To be observed)
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
## Name
Choose a self-explaining name for your project.
## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
ugl.hft-stuttgart.de§https://transfer.hft-stuttgart.de/pages/ugl/website/
\ No newline at end of file
{
"liveServer.settings.port": 5501
}
\ No newline at end of file
viewer.resolutionScale = window.devicePixelRatio;
viewer.scene.postProcessStages.fxaa.enabled = false;
viewer.entities.add({
position: Cesium.Cartesian3.fromDegrees(100, 15),
name: 'Joe T.S.',
billboard: {
image: "../imgs/avatar/JoeSquare.png",
width: 75, // default: undefined
height: 75, // default: undefined
},
});
viewer.entities.add({
position: Cesium.Cartesian3.fromDegrees(10.4515, 51.1657),
billboard: {
image: "../imgs/avatar/PatrickSquare.jpg",
width: 75, // default: undefined
height: 75, // default: undefined
},
});
viewer.entities.add({
position: Cesium.Cartesian3.fromDegrees(22.4062122, 38.9034077),
billboard: {
image: "../imgs/avatar/sakis1.png",
width: 75, // default: undefined
height: 75, // default: undefined
},
});
viewer.entities.add({
position: Cesium.Cartesian3.fromDegrees(113.9213, 0.7893),
billboard: {
image: "../imgs/avatar/rosanny.jpg",
width: 75, // default: undefined
height: 75, // default: undefined
},
});
viewer.entities.add({
position: Cesium.Cartesian3.fromDegrees(13.483476, 10.554910),
billboard: {
image: "../imgs/avatar/sabo.jpg",
width: 75, // default: undefined
height: 75, // default: undefined
},
});
viewer.entities.add({
position: Cesium.Cartesian3.fromDegrees(78.9629, 20.5937),
billboard: {
image: "../imgs/avatar/preston.jpg",
width: 75, // default: undefined
height: 75, // default: undefined
},
});
viewer.entities.add({
position: Cesium.Cartesian3.fromDegrees(67.7100, 33.9391),
billboard: {
image: "../imgs/avatar/Habib.png",
width: 50, // default: undefined
height: 75, // default: undefined
},
});
\ No newline at end of file
/* Remove Cesium Clock and Credit */
.cesium-credit-textContainer {
display: none!important;
}
.cesium-credit-expand-link {
display: none!important;
}
.cesium-viewer-animationContainer {
display: none!important;
}
.cesium-viewer-bottom {
display: none!important;
}
.form-group-inmenu {
padding-left: 45px!important;
}
.aside .aside-primary {
background-color: #39405f;
}
\ No newline at end of file
<html lang="en">
<head>
<meta charset="utf-8">
<script src="https://cesium.com/downloads/cesiumjs/releases/1.80/Build/Cesium/Cesium.js"></script>
<link href="https://cesium.com/downloads/cesiumjs/releases/1.80/Build/Cesium/Widgets/widgets.css" rel="stylesheet">
<link href="./globe.css" rel="stylesheet">
</head>
<body>
<div id="cesiumContainer" style="width: 100%; height:100%"></div>
<script>
var viewer = new Cesium.Viewer('cesiumContainer', {
baseLayerPicker: false,
vrButton: false,
geocoder: false,
navigationHelpButton: false,
selectionIndicator: true,
// shadows: true,
timeline: false,
sceneModePicker: false,
homeButton: false,
fullscreenButton: false,
backgroundColor: Cesium.Color.WHITE,
// infoBox: false,
// terrainExaggeration: 1.5,
});
var scene = viewer.scene;
var clock = viewer.clock;
var referenceFramePrimitive;
var rotatioSpeed;
var lastNow;
var spinRate = 0.5;
viewer.scene.skyBox.destroy();
viewer.scene.skyBox = undefined;
viewer.scene.sun.destroy();
viewer.scene.sun = undefined;
viewer.scene.skyAtmosphere.destroy();
viewer.scene.skyAtmosphere = undefined;
viewer.scene.backgroundColor = new Cesium.Color(255, 255, 255);
function spinIt(scene, time) {
var now = Date.now();
var spinRate = 0.01;
var delta = (now - lastNow) / 1000;
lastNow = now;
viewer.scene.camera.rotate(Cesium.Cartesian3.UNIT_Z, spinRate * delta);
}
function spinGlobe(viewer, spin_rate) {
lastNow = Date.now();
viewer.scene.postRender.addEventListener(spinIt);
}
spinGlobe(viewer);
</script>
<script src="add_avartar_billboard.js"></script>
</body>
</html>
\ No newline at end of file
This diff is collapsed.
- work from Justin was already removed from the Gitlab Pages....
```
{
"item": {
"title": "Outdoor Mobile Augmented Reality in Urban Planning",
"project": "Master Thesis",
"author": {
"firstName": "Justin ",
"lastName": "Jing Hui",
"hftURL": "#"
},
"project_year_start": "2020",
"project_year_end": "2021",
"project_is_on_going": false,
"imageLink":"https://transfer.hft-stuttgart.de/pages/huijustinjing/justin-hui_ar-visualization/home/ezgif.com-gif-maker.gif",
"keywords":["Augmented Reality","Urban Planning"],
"description_en":"This thesis aims to develop an outdoor mobile AR application that visualizes the urban environment using the mentioned grayscale masking filters.",
"description_de":"Ziel dieser Arbeit ist es, eine mobile AR-Anwendung für den Außenbereich zu entwickeln, die die urbane Umgebung mithilfe von Graustufen-Maskierungsfiltern visualisiert."
},
"refIndex": 5,
"links": {
"demo": "https://transfer.hft-stuttgart.de/pages/huijustinjing/justin-hui_ar-visualization/home/",
"publication": "https://transfer.hft-stuttgart.de/pages/huijustinjing/justin-hui_ar-visualization/home/thesis.pdf"
}
}
{
"item": {
"title": "3D Portrayal Service Example",
"project": "SmartVillages",
"author": {
"firstName": "Patrick",
"lastName": "Würstle",
"hftURL": "https://www.hft-stuttgart.de/p/patrick-wuerstle"
},
"project_year_start": "2018",
"project_year_end": "2020",
"project_is_on_going": false,
"imageLink": "imgs/thumbnails/3DPSExampleNiedernhall.PNG",
"keywords": ["CityGML", "3D Visualization", "3D Portrayal Service"],
"description_en": "This Example Application shows the visualization of 3D Tiles content such as Buildings and trees served over a 3D Portrayal Service.",
"description_de": "Diese Beispielanwendung zeigt die Visualisierung von 3D-Tiles-Inhalten wie Gebäuden und Bäumen, die über einen 3D-Portrayal Service bereitgestellt werden."
},
"links": {
"demo": "http://81.169.203.126:8092/service/v1?service=3DPS&acceptversions=1.0&request=GetScene&boundingbox=9.400871,49.059661,9.513287,49.101145&lod=2&layer=building&format=application/json&mime=3dtiles",
"project": "https://www.hft-stuttgart.de/forschung/projekte/aktuell/smart-villages",
"repo": "https://transfer.hft-stuttgart.de/gitlab/ogc/node-3dps"
},
"refIndex": 3
},
{
"item": {
"title": "BW Christmas Market 2021",
"project": "Hobby Project",
"author": {
"firstName": "Joe",
"lastName": "T. Santhanavanich",
"hftURL": "https://www.hft-stuttgart.de/p/thunyathep-santhanavanich"
},
"project_year_start": "2019",
"project_year_end": "2021",
"project_is_on_going": false,
"imageLink": "imgs/thumbnails/ch_bw_2021.jpg",
"keywords": ["Christmas Market"],
"description_en": "The lightweight web map of Christmas markets in BW 2021 with updated Corona Rules, opening hours, link to the official website, etc is developed to help people plan to visit the Christmas market during this Covid situation - fast-changing regulation.",
"description_de": "Die leichtgewichtige Webkarte der Weihnachtsmärkte in BW 2021 mit aktualisierten Corona-Regeln, Öffnungszeiten, Link zur offiziellen Website usw. wurde entwickelt, um den Menschen zu helfen, den Besuch des Weihnachtsmarktes während dieser Covid-Situation zu planen - sich schnell ändernde Vorschriften. "
},
"links": {
"demo": "https://icity.hft-stuttgart.de/christmas_market_2021",
"project": "https://www.hft-stuttgart.de/forschung/i-city"
},
"refIndex": 6
},
```
\ No newline at end of file
{
"item": {
"title": "Test",
"project": "",
"author": {
"firstName": "...",
"lastName": "...",
"hftURL": "..."
},
"project_year_start": "2021",
"project_year_end": "2022",
"project_is_on_going": true,
"imageLink": "imgs/hft.jpg",
"keywords": ["..."],
"description_en": "...",
"description_de": "...",
"internal":true
},
"links": {
"demo": "...",
"publication": "...",
"youtube": "...",
"project": "..."
},
"refIndex": 15
}
\ No newline at end of file
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment