bcgov / databc-web-map-services

Other
1 stars 2 forks source link

GeoServer Enhancement: Roving Point #3

Open ghost opened 7 years ago

ghost commented 7 years ago

Paid Opportunity

We are offering a fixed price of $2,500, to complete the work described in this issue, according to the terms of the BC Developers’ Exchange’s experimental procurement model, Code-with-us.

Here is how payment works

Background

In GeoServer WMS requests for KML output, you can specify that if more than a given number of features are to be returned, render them in a single GroundOverlay plus a point placemark for each feature. In the case of polygonal features, the placemark is located at the centroid of each polygon. These centroids can easily be beyond the BBOX specified in the WMS request in which case the returned placemarks are out of the current map view, leaving Google Earth and Cesium users with no way of seeing the non-spatial attributes of a polygon in the GroundOverlay.

Enhance GeoServer WMS KML output so that Point placemarks associated with a GroundOverlay are positioned within the BBOX of the WMS request. This could be implemented as a new KM option (e.g., kmplacemarkLocation:centroid or kmplacemarkLocation:roving) subject to approval by the GeoServer community.

The solution will also avoid duplicate labels where features appear in multiple adjacent tiles when creating tiled maps.

For more details of the work required, please visit the following GeoServer ticket:

https://osgeo-org.atlassian.net/browse/GEOS-8033

Acceptance Criteria

  1. New KML output must match current, mapserver-based, physical address viewer (http://openmaps.gov.bc.ca/kml/bcgov_physical_address_viewer.kml).

    • Start up new, geoserver-based, physical address viewer.
    • Turn on Property Lines.ICF – Private Ownership Details layer in both viewers.
    • Turn on Site Addresses layer in both viewers.
    • Using Find an Address, zoom to 6621 Oldfield Rd, Central Saanich, bc.
    • Zoom around the associated parcel (e.g., PID 2845857) and confirm that the parcel details placemark is always in view as per the screenshots attached at https://osgeo-org.atlassian.net/browse/GEOS-8033
    • Find other large parcels and confirm that the two versions of the physical address viewer work the same.
  2. The solution will also avoid duplicate labels where features appear in multiple adjacent tiles when creating tiled maps.

  3. The code must be submitted to the GeoServer project on GitHub and accepted into the core GeoServer product.

How to Contribute (How to Apply)

To apply for this work, please email a proposal to michelle.douville@gov.bc.ca by 16:00 PST, Thursday, March 23, 2017. Please reference the issue name "Help Wanted - GeoServer Enhancement: Roving Point".

What to Include in your Proposal (Evaluation Criteria)

We will evaluate and score the proposals we receive by the following criteria. If we are satisfied with the proposals we receive, we will assign the work by 16:00 PST, Tuesday, March 28, 2017 with work proposed to commence on Wednesday, April 5, 2017.

Proposals will be evaluated based on the following:

Knowledge and experience with Java (30 points)

Knowledge and experience with GeoServer source code (30 points)

Knowledge and experience with KML output source code within GeoServer (40 points)

mraross commented 7 years ago

Thank you for the proposals. We've selected JUSTIN DEOLIVEIRA CONSULTING LTD to work on the roving point enhancement to GeoServer. Should you require feedback on your proposal please contact Michelle Douville (Michelle.Douville@gov.bc.ca)

jdeolive commented 7 years ago

I am happy to report that the code for this proposal has been merged into the core GeoServer codebase, via this pull request: https://github.com/geoserver/geoserver/pull/2443