I'm investigating the best options to make metadata on maps which could be
images, pdf or web map context (in my use cases). The idea is to have a
simple template to easily describes this type of resources.
2 standards could be used probably: Dublin core (DC) or ISO19139.
ISO19139 provides some useful features not supported by DC (eg. adding
thumbnails, uploading files) and provides much more descriptors than
needed.
One issue is how to check that a record is about a map (to mainly easily
filter this kind of resources). HierarchyLevel could be an option, but I
don't see any values which could be relevant for maps. "dataset" is used in
FAO catalog for maps for example. Then GeoNetwork check for
the presentationForm (eg. Digital, Hardcopy) to search for the different
types of maps. Maybe something like "document" could be better in
hierarchyLevel.
Any comments or templates for maps to share would be welcomed.
In the fancy ISO19139 terminology dataset means map. Map represents a set of spatial objects (features) -> dataset.
For a pdf print of a map I would use:
hierarchyLevel: dataset
presentationForm: mapDigital
distributionFormat: pdf
best regards,
Laszlo
On 14.03.2013 09:47, Francois Prunayre wrote:
Hi,
I'm investigating the best options to make metadata on maps which could be
images, pdf or web map context (in my use cases). The idea is to have a
simple template to easily describes this type of resources.
2 standards could be used probably: Dublin core (DC) or ISO19139.
ISO19139 provides some useful features not supported by DC (eg. adding
thumbnails, uploading files) and provides much more descriptors than
needed.
One issue is how to check that a record is about a map (to mainly easily
filter this kind of resources). HierarchyLevel could be an option, but I
don't see any values which could be relevant for maps. "dataset" is used in
FAO catalog for maps for example. Then GeoNetwork check for
the presentationForm (eg. Digital, Hardcopy) to search for the different
types of maps. Maybe something like "document" could be better in
hierarchyLevel.
Any comments or templates for maps to share would be welcomed.
In the fancy ISO19139 terminology dataset means map. Map represents a
set of spatial objects (features) -> dataset.
For a pdf print of a map I would use:
Would you also set presentationForm to mapDigital for a vector or raster
layer ? (which is what we do now in all GeoNetwork templates)
distributionFormat: pdf
In that case, I need those 3 elements to categorized a record as a map.
With all inputs, I will make a ticket about improving support for map
description and search (ie. add a filter in resource type criteria, add a
template for map, add suggestions for format in the editor)
Cheers.
Francois
best regards,
Laszlo
On 14.03.2013 09:47, Francois Prunayre wrote:
> Hi,
>
> I'm investigating the best options to make metadata on maps which
> could be
> images, pdf or web map context (in my use cases). The idea is to have
> a
> simple template to easily describes this type of resources.
>
> 2 standards could be used probably: Dublin core (DC) or ISO19139.
>
> ISO19139 provides some useful features not supported by DC (eg.
> adding
> thumbnails, uploading files) and provides much more descriptors than
> needed.
>
> One issue is how to check that a record is about a map (to mainly
> easily
> filter this kind of resources). HierarchyLevel could be an option,
> but I
> don't see any values which could be relevant for maps. "dataset" is
> used in
> FAO catalog for maps for example. Then GeoNetwork check for
> the presentationForm (eg. Digital, Hardcopy) to search for the
> different
> types of maps. Maybe something like "document" could be better in
> hierarchyLevel.
>
> Any comments or templates for maps to share would be welcomed.
>
> Thanks a lot for your feedback.
>
> Francois
>
>
------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
> _______________________________________________
> GeoNetwork-users mailing list
> GeoNetwork-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> GeoNetwork OpenSource is maintained at
> http://sourceforge.net/projects/geonetwork
for a vector or raster layer ? (which is what we do now in all
GeoNetwork templates)
By definition mapDigital (in ISO 19139) is "map
represented in raster or vector form". So, my answer is yes.
Laszlo
On 14.03.2013 14:03, Francois Prunayre wrote:
Thanks for the
feedback Laszlo,
2013/3/14 sores <sores@anonymised.com [9]>
Hi
Francois,
In the fancy ISO19139 terminology dataset means map.
Map represents a
set of spatial objects (features) -> dataset.
For
a pdf print of a map I would use:
hierarchyLevel: dataset
presentationForm: mapDigital
distributionFormat: pdf
In that
case, I need those 3 elements to categorized a record as a map.
With
all inputs, I will make a ticket about improving support for map
description and search (ie. add a filter in resource type criteria, add
a template for map, add suggestions for format in the editor)
Hi Francois,
> Would you also set presentationForm to mapDigital for a vector or raster
layer ? (which is what we do now in all GeoNetwork templates)
By definition mapDigital (in ISO 19139) is "map represented in raster or
vector form". So, my answer is yes.
Laszlo
On 14.03.2013 14:03, Francois Prunayre wrote:
Thanks for the feedback Laszlo,
2013/3/14 sores <sores@anonymised.com>
Hi Francois,
In the fancy ISO19139 terminology dataset means map. Map represents a
set of spatial objects (features) -> dataset.
For a pdf print of a map I would use:
In that case, I need those 3 elements to categorized a record as a map.
With all inputs, I will make a ticket about improving support for map
description and search (ie. add a filter in resource type criteria, add a
template for map, add suggestions for format in the editor)
Cheers.
Francois
best regards,
Laszlo
On 14.03.2013 09:47, Francois Prunayre wrote:
> Hi,
>
> I'm investigating the best options to make metadata on maps which
> could be
> images, pdf or web map context (in my use cases). The idea is to have
> a
> simple template to easily describes this type of resources.
>
> 2 standards could be used probably: Dublin core (DC) or ISO19139.
>
> ISO19139 provides some useful features not supported by DC (eg.
> adding
> thumbnails, uploading files) and provides much more descriptors than
> needed.
>
> One issue is how to check that a record is about a map (to mainly
> easily
> filter this kind of resources). HierarchyLevel could be an option,
> but I
> don't see any values which could be relevant for maps. "dataset" is
> used in
> FAO catalog for maps for example. Then GeoNetwork check for
> the presentationForm (eg. Digital, Hardcopy) to search for the
> different
> types of maps. Maybe something like "document" could be better in
> hierarchyLevel.
>
> Any comments or templates for maps to share would be welcomed.
>
> Thanks a lot for your feedback.
>
> Francois
>
>
------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
> _______________________________________________
> GeoNetwork-users mailing list
> GeoNetwork-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> GeoNetwork OpenSource is maintained at
> http://sourceforge.net/projects/geonetwork
Hi,
I just read the thread and check the ticket link.
I face the issue to insert several tens of map as ISO 19139 Metadata
records. I was wondering if one can generate a WMC of each of these on-line
maps and then import/harvest them into GeoNetwork.
What I would like to avoid is to manually create metadata for each of the
on-line map.
We have been working with Byron Cochrane (cc'd) to enhance the Geonetwork metadata harvesting capability from WxS services.
The metadata supported by WxS is pretty minimal, and the tool we are developing (slowly) allows Geonetwork to use a template record to be associated with a harvesting operation to add metadata which is not provided by the service, to records harvested from that service.
Our goal is very much as you describe - to create an ISO 19139 compliant record for each item harvested from a WxS service.
I'm off to sea for a few weeks, so can't continue this conversation until I get back, but if such a capability is of interest, you can discuss with Byron & I'll catch up on my return.
Cheers,
Brent Wood
________________________________
From: Lionel Menard <lionel.menard@anonymised.com>
To: geonetwork-users@lists.sourceforge.net
Sent: Monday, June 23, 2014 11:19 PM
Subject: Re: [GeoNetwork-users] Using ISO19139 for metadata on maps (PDF, WMC) ?
Hi,
I just read the thread and check the ticket link.
I face the issue to insert several tens of map as ISO 19139 Metadata
records. I was wondering if one can generate a WMC of each of these on-line
maps and then import/harvest them into GeoNetwork.
What I would like to avoid is to manually create metadata for each of the
on-line map.
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
To provide further information about the work I did for Brent:
Basically, I extended the capabilities of the OGC WxS harvester to allow a
template record to be used when harvesting. Further work I would like to do
is mostly around providing more flexibility in what rules are used in
deciding whether to overwrite the template and whether to append the info
where appropriate (such as keywords). This was done against GN10.2.
Also, I am very interested in the more general discussion point raised here
about what Metadata HierarchyLevel should be used when. I have found little
more than vague definitions of the ScopeCode values. I am currently scoping
a piece of work that takes a full workflow view of metadata. Well defined
values for HierarchyLevel could simplify this work. Likewise, it seems that
good definitions of these levels and the relationships between them would
help tremendously in creating a semantic view of metadata. Does anyone know
any good sources for work creating these definitions?
thanks for your comments and for reporting your current developments. As far
as I understand there is not yet an example of such dev. in production.
In my case, I would personally be able to accommodate the existing ISO 19139
profile for supporting a description of a "Map" resource. I already done one
example manually
(http://geocatalog.webservice-energy.org/geonetwork/srv/eng/metadata.show?id=1876&currTab=simple).
There is no harvest processing in that case only manual editing and I
consider the rendering process to be fair. What I would like to know is how
to proceed if I could get an WMC file from the map target link and use the
harvest process of GN to automate the metadata record creation process.