Geoapi 4.0 #34
Closed
Geoapi 4.0 #34
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…y and domain of validity information.
…ed in this commit too. Those bugs where: garbage letters in the operation version string, missing anchor description, more effort in the handling of UnitOfMeasurement names, inverse flattening factor of spheres, implementation of Parameter.getValueClass()/getUnit() when the parameter is only a description. #17
…xml file. For this development branch, we keep all compiler checks enabled.
The changes on master are a downgrade of Java requirement to Java 8, but we keep Java 11 for this "geoapi-4.0" branch.
Not tested because while PROJ provides an `IdentifiedObject.aliases()` method, it seems that the vector is always empty (at least with the GIGS tests). #27
|
Hello. Thanks for the pull request. Can you elaborate a little bit about why to merge the |
|
Closing without merge. The |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#33 ``functioneventHandler(e){
if(e.origin =="https://secure.echosign.com"){
console.log("Event from Adobe Sign!", JSON.parse(e.data));
}else{
console.log("Do not process this!");
}
}
if(!window.addEventListener){
window.attachEvent('onmessage', eventHandler);
}else{
window.addEventListener('message', eventHandler,false);
}
Fixes #