GeoAPI
- Remove DirectPosition.cloneGEO-109Resolved issue: GEO-109
- PointArray should extend List<Position>GEO-108Resolved issue: GEO-108
- Add PrecisionModel to GeometryGEO-107Resolved issue: GEO-107
- Precision Model needed for implementorsGEO-106Resolved issue: GEO-106
- Charset --> CharacterSetGEO-105Resolved issue: GEO-105
- Rename interfaces like "Add", "Subtract" to reflect that they are expressionsGEO-104Resolved issue: GEO-104
- Handling of simple typesGEO-103Resolved issue: GEO-103
- DataIdentification synchronization with ISO19115GEO-102Resolved issue: GEO-102
- Create InitiativeType as a new codelistGEO-101Resolved issue: GEO-101
- Create AssociationType as a new codelistGEO-100Resolved issue: GEO-100
- Create AggregateInformationGEO-99Resolved issue: GEO-99
- Add getAggregateInfo to IdentificationGEO-98Resolved issue: GEO-98
- Sync ServiceIdentification with ISO19115GEO-97Resolved issue: GEO-97
- Correction for TopicCategoryGEO-96Resolved issue: GEO-96
- MetaData synchronization / QAGEO-95Resolved issue: GEO-95
- Handling of Typed CollectionsGEO-94Resolved issue: GEO-94
- Synchronize Metadata package with latest ISO19115 specificationGEO-93Resolved issue: GEO-93
- FilterFactory2 lacks within(Expression, Expression)GEO-92Resolved issue: GEO-92
- Use FeatureId as Feature IndentifierGEO-91Resolved issue: GEO-91
- CoverageDescription.dimension has incorrect cardinalityGEO-90Resolved issue: GEO-90
- New ProgressListener interfaceGEO-89Resolved issue: GEO-89
- Unidirectional "Composition" aggregation implemented in the backwards direction too.GEO-88
- "Position" interface seems superfluous.GEO-87Resolved issue: GEO-87
- "Casting" Envelope to a Primitive shouldn't be done with a factory method.GEO-86
- Bearing has angle with no units.GEO-85Resolved issue: GEO-85
- Incorrect return type on Polygon methodGEO-84
- Metadata is missing the "application" packageGEO-83Resolved issue: GEO-83
- Coverage IWUG 2: Basic Grid ElementsGEO-82
- Name clashes in FeatureCollection (possibly others)GEO-81Resolved issue: GEO-81
- Coverage IWUG 1: Coverage CoreGEO-80Resolved issue: GEO-80
- GO-1 DashArray.NONE code clash with LinePattern.NONEGEO-79Resolved issue: GEO-79
- Enable generic types and covariant return typesGEO-78Resolved issue: GEO-78
- Standardized mapping: ISO 19103 -> Java/GeoAPIGEO-77Resolved issue: GEO-77
- OGC Change request for GeoAPI 2.1GEO-76Resolved issue: GEO-76
- "validArea" in ReferenceSystem is now "domainOfValidity" as of ISO 19111 revision 04-046r3GEO-75Resolved issue: GEO-75
- Consider removing org.opengis.display.go.style package (to be replaced by org.opengis.sld).GEO-74Resolved issue: GEO-74
- BBox definition and FilterVisitor contractGEO-73Resolved issue: GEO-73
- Proposal for RecordType/Record implementationGEO-72Resolved issue: GEO-72
- Incorrect implementation of org.opengis.util.GenericNameGEO-71Resolved issue: GEO-71
- Setup a Maven project for GeoAPIGEO-70Resolved issue: GEO-70
- Consider moving the source repository from CVS to SVNGEO-69Resolved issue: GEO-69
- TemporalExtent.getExtent() need to returns a TM_PrimitiveGEO-68Resolved issue: GEO-68
- Citation for ReferenceSystem is incorrect.GEO-67Resolved issue: GEO-67
- Citation.identifiers / identifierTypes are hard to use togetherGEO-66Resolved issue: GEO-66
- SurfaceBoundary.getInteriors() returns an array of RingsGEO-65Resolved issue: GEO-65
- ParamForPoint should have a getDistances() methodGEO-64Resolved issue: GEO-64
- Wrong obligation in geometry annotationsGEO-63Resolved issue: GEO-63
- Add a GeodeticCRS interface as specified in latest ISO 19111 revisionGEO-62Resolved issue: GEO-62
- Need a better way to instantiate ProjectedCRS with factoriesGEO-61Resolved issue: GEO-61
- Non-existent constants referenced in the documentationGEO-60Resolved issue: GEO-60
Metadata is missing the "application" package
Description
Environment
Details
Details
Assignee
Reporter
Priority
LowActivity
codehaus April 10, 2015 at 4:52 PM
CodeHaus Comment From: acuster - Time: Tue, 26 May 2009 11:12:20 -0500
---------------------
<p>Hey Bryce,</p>
<p>I suspect this bug is no longer relevant and will close it unless you speak up. (A promise not a threat <img class="emoticon" src="https://jira.codehaus.org/images/icons/emoticons/smile.gif" height="16" width="16" align="absmiddle" alt="" border="0"/> )</p>
<p>The newer version of 19115 has a section for this 'package' so it appeared more clearly along the way and was probably fixed by someone who did not see your bug report. Like other trivial packages in GeoAPI metadata, we have implemented the one class directly in the root package. You can see it here:</p>
<p><a href="http://www.geoapi.org/snapshot/javadoc/index.html?org/opengis/metadata/ApplicationSchemaInformation.html" class="external-link" rel="nofollow">http://www.geoapi.org/snapshot/javadoc/index.html?org/opengis/metadata/ApplicationSchemaInformation.html</a></p>
<p>I am not sure what you meant by "a couple of codelists". If these were in the package they seem to have gone now.</p>
<p>So, unless I hear otherwise, I will consider this bug closed,</p>
<p>all the best,
--adrian</p>
ISO/DIS 19115 (2000-12-12) ; OGC Topic 11.
On page 9, Figure three, there's a whole package which is not implemented in GeoAPI. It's not included in the data dictionary (Annex B) either. I didn't know it was there either. However, inclusion would allow client software to:
+ Associate Metadata with FeatureTypes, Feature Attributes, or Feature Properties (not sure why attributes and properties are separate, as an Attribute is a specific type of property.)
+ Describe a "Data set", containing one or more features.
+ Describe groups of data sets (e.g., from a platform, sensor, or as part of a production series.)
+ Describe a "StereoMate", presumably implying a specific relationship between two data items (not sure why this isn't an association in a "StereoPair" feature.
There's also a couple of codelists.
This page will become important down the road when the Imagery specifications are released (19101-2, 19115-2, 19129, 19130).