ChronoCity

by gouzouni JavaScript Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions Vulnerabilities Install Support

kandi X-RAY | ChronoCity Summary

ChronoCity is a JavaScript library. ChronoCity has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

The application can be divided in three main parts: the viewport, sidebar and overview-map. The viewport is where the actual data is shown and where you should use your mouse or arrow-keys to navigate around. The sidebar is where you can find all settings and information. The sidebar is hidden by default, you can show it by clicking the menu-icon on the top-left. Below the menu-icon is the map-toggle. By clicking this, the overview-map is shown on which you can see the current orientation of the camera.

Support

Quality

Security

License

Reuse

Support

ChronoCity has a low active ecosystem.

It has 0 star(s) with 0 fork(s). There are 1 watchers for this library.

It had no major release in the last 6 months.

ChronoCity has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of ChronoCity is current.

Quality

ChronoCity has no bugs reported.

Security

ChronoCity has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

ChronoCity does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

ChronoCity releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of ChronoCity

Get all kandi verified functions for this library.

ChronoCity Key Features

No Key Features are available at this moment for ChronoCity.

ChronoCity Examples and Code Snippets

No Code Snippets are available at this moment for ChronoCity.

Community Discussions

No Community Discussions are available at this moment for ChronoCity.Refer to stack overflow page for discussions.

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install ChronoCity

For the server-side running correctly, you should also make sure you have the following dependencies installed on your Python interpreter;. All important interactions can be done within the GUI. There are also some other usefull command for more control. You can use these in your browser's webconsole;.
Install a (local) webserver. E.g. Apache Tomcat
Install all Python dependencies (see next section)
Download this entire repositery as .zip
Extract the zip into your webserver-webapps directory. Make sure the paths look like: webapps/OPCM/chronocity-engine/.. and webapps/OPCM/chronocity-viewer/..
Download the AHN datasets in potree-structure here: https://wvanopstal.stackstorage.com/s/n4FTmxSEaJ6avrp
Extract the two folders AHN2 and AHN3 and put them both under chronocity-viewer/pointclouds/
Download the pre-processed difference-layers here: https://wvanopstal.stackstorage.com/s/qEvkj1lgwUksYEK
Extract AHN2-AHN3, AHN3-AHN2 and Clips
Put both AHN2-AHN3, AHN3-AHN2 under chronocity-viewer/pointclouds/. (next to AHN2 and AHN3)
Download and extract the Clips folder here: https://wvanopstal.stackstorage.com/s/DhTwM4Fm6Di5yWw
Put the contents in Clips under chronocity-engine/Clips. It should now contain 4 files.
Get a LAStools license-file (.txt) and save it under chronocity-engine/Tools/LAS_tools
The ChronoCity-viewer is ready to view. You can access it through your webserver and browse to domain:port/OPCM/
fiona
laspy
flask
copy
os
json
multiprocessing
time
shutil
shapely
In /OPCM/chronocity-engine/server_service.py at the bottom you should replace the two paths serv_path and potree_path with the path to the two installations folders like below. Be aware of the double '\' ! The server listens to port 12839 by default, but you can specify it yourself if needed. port = 12839 serv_path = "C:\\geo1007\\apache-tomcat-8.5.14\\webapps\\OPCM\\chronocity-engine\\" potree_path = "C:\\geo1007\\apache-tomcat-8.5.14\\webapps\\OPCM\\chronocity-viewer\\"
Run the server_service.py to start the server. You can test if it is running correctly by browsing to localhost:12839/test in your browser. It will return the message ACTIVE if it is running.
The viewer runs on port 8080 by default and relies on the default value for the server-side. If you have changed the default port, you should edit OPCM/chronocity-viewer/build/potree/potree.js and search for localhost:. Replace the entries with your custom ports.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: