tangdiforx /
iOSPalette
Objective-C version of Google Palette algorithm in Java.A tool to extract the main color of an image.
Active repository
Objective-CNo license
⑂ 81 forks◯ 16 issuesUpdated Mar 31, 2026
Loading repository data…
Loading repository data…
urbancamo / repository
The objective of the Java API for KML is to provide Java interfaces for easy access to KML (Keyhole Markup Language) data.
The objective of the Java API for KML is to provide Java interfaces for easy access to KML (Keyhole Markup Language) data.
Thank you to the Micromata for open sourcing this project. The repository has been transferred to urbancamo for onward maintenance. He will endeavour to keep dependencies security patched moving forward. Thank you to those who previously submitted pull requests or bug reports.
If you are currently running version
2.x.xthen you will need to change thegroupIdfromde.micromata.jaktouk.m0nomto be able to use versions3.x.xonwards.
Version 3+ of the library supports Java 11+ and is built with Java 11.
<!-- https://mvnrepository.com/artifact/uk.m0nom/javaapiforkml -->
<dependency>
<groupId>uk.m0nom</groupId>
<artifactId>javaapiforkml</artifactId>
<version>${project.version}</version>
</dependency>
The maven repository entry is https://mvnrepository.com/artifact/uk.m0nom/javaapiforkml
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.
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.
An archive of high level documentation can be found at: https://web.archive.org/web/20170316194859/http://labs.micromata.de/projects/jak.html
Between version 2.x and 3.x the library migrated from javax.xml.bind to
jakarta.xml.bind and switched to the Glassfish Jakarta JAXB runtime. That runtime
honours the @XmlNs(prefix = "kml", ...) hint in package-info.java that the older
Sun/Metro JAXB RI silently ignored, so identical source code that used to emit:
<kml xmlns="http://www.opengis.net/kml/2.2">
<Document>...</Document>
</kml>
began emitting the fully-prefixed form:
<kml:kml xmlns:kml="http://www.opengis.net/kml/2.2">
<kml:Document>...</kml:Document>
</kml:kml>
Google Maps and several other consumers reject the prefixed form with INVALID_KML
even though it is technically valid XML. (Simply removing the @XmlNs hint is not
enough — the Jakarta runtime will then auto-assign a prefix like ns4:, which is
worse.)
As of this release, Kml.createMarshaller() installs a default
NamespacePrefixMapper that forces the KML namespace to be emitted as the default
(unprefixed) namespace. The gx, atom and xal extension namespaces still get
their conventional prefixes when referenced, so output now looks like:
<kml xmlns:gx="http://www.google.com/kml/ext/2.2"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:xal="urn:oasis:names:tc:ciq:xsdschema:xAL:2.0"
xmlns="http://www.opengis.net/kml/2.2">
<Document>...</Document>
</kml>
which matches the 2.x behaviour that Google Maps accepts.
kml: prefixIf you actually want the prefixed form, subclass Kml and override
decorateMarshaller(JAXBContext, Marshaller). It is called after the default
prefix mapper is installed, so your replacement wins:
import jakarta.xml.bind.JAXBContext;
import jakarta.xml.bind.Marshaller;
import org.glassfish.jaxb.runtime.marshaller.NamespacePrefixMapper;
import de.micromata.opengis.kml.v_2_2_0.Kml;
public class PrefixedKml extends Kml {
@Override
protected void decorateMarshaller(JAXBContext context, Marshaller marshaller) {
try {
marshaller.setProperty(
"org.glassfish.jaxb.namespacePrefixMapper",
new NamespacePrefixMapper() {
@Override
public String getPreferredPrefix(String namespaceUri,
String suggestion,
boolean requirePrefix) {
if ("http://www.opengis.net/kml/2.2".equals(namespaceUri)) {
return "kml";
}
return suggestion;
}
});
} catch (Exception e) {
throw new RuntimeException(e);
}
}
}
Selected from shared topics, language and repository description—not editorial ratings.
tangdiforx /
Objective-C version of Google Palette algorithm in Java.A tool to extract the main color of an image.
john-difool /
cocos2d for Android is a framework for building 2D games, demos and other graphical/interactive applications. It is based on the cocos2d-iphone design: it uses the same API, but instead of using objective-c, it uses java.
The reliable web app pattern is a set of objectives to help your web application converge on the cloud. This repo contains a reference implementation of a reliable web application for Java.
StuartLab /
MiNA (Mitochondrial Network Analysis) is a project aimed at making the analysis and characterization of mitochondrial network morphology more accurate, faster, and objective. This project currently consists of a set of Python scripts (and JAVA for the user interface) for the Fiji distribution of ImageJ.
mayurisamanta /
The main objective of this project is to cater the needs of the passenger who are traveling from one point to another. This project have contains essential modules like Customer and Administrator. User can book / reserved his ticket one day before.
Anjulcodewiz /
INTRODUCTION: The main aim of the project is the management of the database of the pharmaceutical shop. This project is insight into the design and implementation of a Pharmacy Management System. This is done by creating a database of the available medicines in the shop. The primary aim of pharmacy management system is to improve accuracy and enhance safety and efficiency in the pharmaceutical store. The aim of this project is to develop software for the effective management of a pharmaceutical store. We have developed this software for ensuring effective policing by providing statistics of the drugs in stock. Description on the topic: This program can be used in any pharmaceutical shops having a database to maintain. The software used can generate reports, as per the user’s requirements. The software can print invoices, bills, receipts etc. It can also maintain the record of supplies sent in by the supplier. Here, the admin who are handling the organization will be responsible to manage the record of the employee. Each employee will be given with a separate username and password. Problem Definition: The aim of the project is to create an effective software to help the pharmacist to maintain the records of the medicines, handle user details, generate invoice, check and renew validity and provide a scope of communication between users by using inbuilt messaging system. Pharmacy management system deals with the maintenance of drugs and consumables in the pharmacy unit. This pharmacy management system is user friendly. Objectives -> Primary objective •To gain practical experience by modeling a software based on real world problem. •To understand how to work on Front-end (Java) and Back-end (MySQL) by using server(wamp). -> Secondary objective •To develop an application that deals with the day to day requirement of any pharmacy. •To develop the easy management of the medicines (drugs). •To handle the inventory details like sales details, purchase details and stock expiry and quantity. •To provide competitive advantage to the pharmacy. •To provide details information about the stock on details necessary and help locate it in shop easily. •To make the stock manageable and simplify the use of inventory in the pharmacy. Hardware and software tools: The system services and goals are established by consultation with system user. They are then defined in details and serve as a system specification. System requirement are those on which the system runs. ⚙️ Hardware Requirements: o Computer with either Intel Pentium processor or AMD processor. o 1GB+ DDR RAM o 40GB hard disk drive 💻 Software Requirements: o Windows/ MacOS/ Linux operating system. o JRE and JDK. o MySQL server (WAMP or XAMPP or any) Chapter 2 - DESIGN Database Design is a collection of processes that facilitate the designing, development, implementation and maintenance of enterprise data management systems. It helps produce database systems: o That meet the requirements of the users o Have high performance. Architecture Description The design of a DBMS depends on its architecture. It can be centralized or decentralized or hierarchical. The architecture of a DBMS can be seen as either single tier or multi-tier. ER Diagram image.png Fig 1: ER Diagram An entity–relationship model describes interrelated things of interest in a specific domain of knowledge (Refer Fig 1). It is composed of entity types and specifies relationships that can exist between instances of those entity types. Relational Schema Diagram image_1.png Fig 2: Relational Schema Relational schema is a collection of meta-data. Database schema describes the structure and constraints of data representing in a particular domain (Refer Fig 2). Chapter 3 - IMPLEMENTATION Description on Implementation The goal of this application is to manage the medicines and various function of the pharmacy. List of modules: o Login page o Home page o Company o Purchase o Drugs o Sales o User/Settings o Messaging Chapter 4 - Result and Discussion By using MySQL commands and its database this website Pharmacy management tends to store all the data received from the users including drugs sales details and the profit made by the owners are all in this data base. This website allows the user to generate invoices for sales, check expiry and quantity remaining of the drugs. It also provides user with options to renew validity and add more drugs into the store and update the database accordingly. By using xampp server these database commands are easily initiated into the database and the ER diagram with relational schema diagrams helps us to make the structure of the database faster and it was easier to make them understand the needs of the website. Login Information id :1 password: admin CONCLUSIONS AND FUTURE SCOPE o Detailed information gathering has to be done. Without that the purpose for using the software won’t be satisfied properly. o However, it can give good profits in the long run. o Implementing the software requires change in the business practices. o Efficient organization of all knowledge is the analysis company and easy analysis access and retrieval of information is possible. o In this project we can also include BAR CODE facility using the bar code reader, which will detect the expiry date and the other information about the related medicines. o Company using this software will always be able to plan in future and always be aware of their financial position in the market. o It leads to ease in functioning of business processes. o The project can be made more robust by including biometric verification. o There is also a scope to expand by implementing newer technologies like cloud etcetera.