Has anyone dealt effectively with geo references that are a single lat/lon point versus a bounding box or polygon?
For example, we have a buoy which is at a certain location. We need to reference just the single location for that buoy for our metadata. If we do what seems to be implied by protocol, which is force a bounding box with 4 unique parameters, it blows up some other things we are doing with the metadata.
My developer is suggesting we put the same parameter in NS and in EW. That's great for the metadata, and it still makes GN search behave, but then it makes the GN map embedded in the metadata record basically display a black box which is pretty ugly.
Since having the metadata display the way the developer needs is more important than a map view, wondering if it is possible to disable the map view for certain records or even if not, if it would be possible and make sense to disable for all records (I like the ability to search by map so the mini-map is very useful, but other than giving a nice at-a-glance view of a region, it doesn't seem to offer much for the user in the metadata itself).
Thoughts? Ideas? Solutions?
Kathy
Hi Kathy,
2015-10-23 19:07 GMT+02:00 Kathy Koch <kkoch@anonymised.com>:
Has anyone dealt effectively with geo references that are a single lat/lon
point versus a bounding box or polygon?
For example, we have a buoy which is at a certain location. We need to
reference just the single location for that buoy for our metadata. If we
do what seems to be implied by protocol, which is force a bounding box with
4 unique parameters, it blows up some other things we are doing with the
metadata.
My developer is suggesting we put the same parameter in NS and in EW.
That's great for the metadata, and it still makes GN search behave, but
then it makes the GN map embedded in the metadata record basically display
a black box which is pretty ugly.
Since having the metadata display the way the developer needs is more
important than a map view, wondering if it is possible to disable the map
view for certain records or even if not, if it would be possible and make
sense to disable for all records (I like the ability to search by map so
the mini-map is very useful, but other than giving a nice at-a-glance view
of a region, it doesn't seem to offer much for the user in the metadata
itself).
Thoughts? Ideas? Solutions?
We had similar need for sensor location and added support to GN
https://github.com/geonetwork/core-geonetwork/issues/275
But I see that GN3 support in edit mode but does not properly display them.
Francois
Kathy
------------------------------------------------------------------------------
_______________________________________________
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
I don't believe the ISO 19115 standard allows for points. Bounding boxes and
bounding polygons only. So a minimum of two coordinate values are needed.
But I agree with the need.
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Geo-References-to-a-single-point-tp5232251p5232962.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.
Good to know it’s in the works anyway. This at least means that I can put in my single points and know that in the future it will work the way it needs to. Thanks for the info!
Kathy
From: Francois Prunayre [mailto:fx.prunayre@…54…]
Sent: Tuesday, October 27, 2015 3:13 AM
To: Kathy Koch <kkoch@...1164...>
Cc: geonetwork-users@lists.sourceforge.net
Subject: Re: [GeoNetwork-users] Geo References to a single point
Hi Kathy,
2015-10-23 19:07 GMT+02:00 Kathy Koch <kkoch@...1164...<mailto:kkoch@…1164…>>:
Has anyone dealt effectively with geo references that are a single lat/lon point versus a bounding box or polygon?
For example, we have a buoy which is at a certain location. We need to reference just the single location for that buoy for our metadata. If we do what seems to be implied by protocol, which is force a bounding box with 4 unique parameters, it blows up some other things we are doing with the metadata.
My developer is suggesting we put the same parameter in NS and in EW. That's great for the metadata, and it still makes GN search behave, but then it makes the GN map embedded in the metadata record basically display a black box which is pretty ugly.
Since having the metadata display the way the developer needs is more important than a map view, wondering if it is possible to disable the map view for certain records or even if not, if it would be possible and make sense to disable for all records (I like the ability to search by map so the mini-map is very useful, but other than giving a nice at-a-glance view of a region, it doesn't seem to offer much for the user in the metadata itself).
Thoughts? Ideas? Solutions?
We had similar need for sensor location and added support to GN
https://github.com/geonetwork/core-geonetwork/issues/275
But I see that GN3 support in edit mode but does not properly display them.
Francois
Kathy
------------------------------------------------------------------------------
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net<mailto:GeoNetwork-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
Actually if you look at Francois' example at https://github.com/geonetwork/core-geonetwork/issues/275 it does show a 19115 capability if north lat = south lat (northBL = northern most point). So I'm pleased that the GN community is thinking this way even if it doesn't work quite the way it needs to right now. Forward motion is always good!
Thanks!
Kathy
-----Original Message-----
From: ByronCinNZ [mailto:cochranes4@anonymised.com]
Sent: Tuesday, October 27, 2015 11:23 PM
To: geonetwork-users@lists.sourceforge.net
Subject: Re: [GeoNetwork-users] Geo References to a single point
I don't believe the ISO 19115 standard allows for points. Bounding boxes and bounding polygons only. So a minimum of two coordinate values are needed.
But I agree with the need.
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Geo-References-to-a-single-point-tp5232251p5232962.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
_______________________________________________
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