Skip to content

Commit

Permalink
Issue 39 (#40)
Browse files Browse the repository at this point in the history
* Remove idea files from repo

* Merge in urbancamo's branch pom.

* Merge in urbancamo's branch pom.

* - merge in urbancamo's branch source code to fix javadoc errors to allow release
 - update groupId in pom.xml to allow me to release via apache.

* - update groupId in pom.xml to allow me to release via apache.

* - updated docs.

* - version 3.0.6

---------

Co-authored-by: Mark Wickens <[email protected]>
  • Loading branch information
urbancamo and Mark Wickens authored Nov 21, 2023
1 parent 70b4635 commit aab2ba2
Show file tree
Hide file tree
Showing 133 changed files with 4,931 additions and 5,486 deletions.
3 changes: 2 additions & 1 deletion .gitignore
Original file line number Diff line number Diff line change
@@ -1,2 +1,3 @@
target
.metadata/
.metadata/
/.idea/
39 changes: 31 additions & 8 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,23 +5,46 @@
# Moved to [https://github.com/urbancamo/javaapiforkml](https://github.com/urbancamo/javaapiforkml)

Thank you to the Micromata for this project open sourcing this project.
Due to issues with publishing new versions, [urbancamo](mailto:[email protected]) has decided to keep his own fork up-to-date with bug fixes and pull requests.
He will endevour to keep dependencies security patched moving forward.
The repository has been transferred to [urbancamo](mailto:[email protected]) for onward maintenance.
He will endeavour to keep dependencies security patched moving forward.
Thank you to those who previously submitted pull requests.

The [forked version](https://github.com/urbancamo/javaapiforkml) supports Java 11+.
If you are currently running version 2 then you will need to change the `groupId` from
`de.micromata.jak` to `uk.m0nom` to be able to use versions from `3.0.0` onwards.

```xml
<!-- https://mvnrepository.com/artifact/uk.m0nom/javaapiforkml -->
<dependency>
<groupId>uk.m0nom</groupId>
<artifactId>javaapiforkml</artifactId>
<version>${project.version}</version>
</dependency>
```

---

The main goal of the Java API for KML (JAK) is to provide automatically generated full reference implementation of the KML object model defined by OGC’s KML standard and Google’s GX extensions. It is an object orientated API that enables the convenient and easy use of KML in existing Java environments.
The main goal of the Java API for KML (JAK) is to provide automatically generated full reference implementation of the
KML object model defined by OGC’s KML standard and Google’s GX extensions. It is an object orientated API that enables
the convenient and easy use of KML in existing Java environments.

KML is an XML-based language schema that describes and visualizes geographic data. The language is often used in 2D web based maps and 3D virtual globes. Originally developed for Google Earth as a means of maintaining and exchanging geographical data, the language was defined by the Open Geospatial Consortium (OGC) as a standard in April 2008. So far, many virtual globes, like for example NASA’s Earth Wind and Microsoft’s Virtual Earth, have adopted the KML language as their data format of choice.
KML is an XML-based language schema that describes and visualizes geographic data. The language is often used in 2D web
based maps and 3D virtual globes. Originally developed for Google Earth as a means of maintaining and exchanging
geographical data, the language was defined by the Open Geospatial Consortium (OGC) as a standard in April 2008.
So far, many virtual globes, like for example NASA’s Earth Wind and Microsoft’s Virtual Earth, have adopted the KML
language as their data format of choice.

In order to ensure convenient and easy use of KML in existing Java-systems, an object oriented API is necessary. APIs for XML dialects are implemented using two layers. The current official XML schema of KML in conjunction with the JAXB technology is used to generate Java class representations automatically. KML’s schema is a document describing the correct syntax of KML files and can, therefore, be used for validating the corresponding KML files. The semantic application layer, which is found on top of the JAXB layer, is abstracted from the raw generated classes and defines a well-shaped API.
In order to ensure convenient and easy use of KML in existing Java-systems, an object oriented API is necessary.
APIs for XML dialects are implemented using two layers. The current official XML schema of KML in conjunction with the
JAXB technology is used to generate Java class representations automatically. KML’s schema is a document describing
the correct syntax of KML files and can, therefore, be used for validating the corresponding KML files. The semantic
application layer, which is found on top of the JAXB layer, is abstracted from the raw generated classes and defines
a well-shaped API.

This API provides easy out-of-the-box access to KML for the user (resp. the developer). This project created, a Java API for KML (short: JAK) in order to enable this.
This API provides easy out-of-the-box access to KML for the user (resp. the developer). This project created, a Java
API for KML (short: JAK) in order to enable this.

A high level documentation can be found at: https://web.archive.org/web/20170316194859/http://labs.micromata.de/projects/jak.html
A high level documentation can be found at:
https://web.archive.org/web/20170316194859/http://labs.micromata.de/projects/jak.html

The current JARs can be obtained via Maven or at the Download page:

Expand Down
Loading

0 comments on commit aab2ba2

Please sign in to comment.