OpenLayers/PHP/JavaScript coding working with PostGIS/PostgreSQL & GeoServer

-------------------------------------------
JOB SUMMARY: 7 TASK ITEMS
-------------------------------------------

-------------------------------------------
NOTES:
THIS PROJECT REQUIRES;
1. Editing & adding code of existing website PHP documents. It requires working with PostGIS enabled PostgreSQL database tables. It requires working with GeoServer. It requires working with OpenLayers/JavaScript.
---
2. Freelancer must add comments to the code s/he edits, e.g.- --Edited/Added/Rem\'d by Freelancer name & time/date stamp & reference to PPH job# & specific task #.
---
3. Freelancer must engage in pre-bidding chat sessions with me for the purposes of discovery and understanding of each task individually in detail, so both parties have full clarification of the expected end result(s). I will compensate pre-bidding chat time at $10 pounds per hour to the winning bidder only. This pre-bidding rate will be billed by every 1/4 hour, so if you spend 15 minutes in pre-bidding chat sessions with me, winning bidder will be compensated $2.5 pounds, or if you spend 3 hours in pre-bidding chat sessions with me, winning bidder will be compensated $30 pounds. This pre-bidding compensation will be paid \'after\' successful completion of the project, as apart of the final payment. Any bidder who engages in pre-bidding chat sessions with me will not be compensated if they are not awarded the project! If additional clarification is needed by the bidder, after the project has been assigned to a bidder, this will chat time will not be billable. Chat transcripts will be copied and pasted into the PPH clarification board for historical reference.
---
4. This job to be completed on or before April 15th, 2011.
-------------------------------------------


-------------------------------------------
JOB TASKS:
1. Display SINGLE property polygon from gis_properties ala GeoServer that match the respective clave number record on the CLAVE page. This is it\'s own layer, is at the foreground/top of the map stack, and is named in the overlay layer list using it\'s clave number. *These do not need to be editable. They should be colored according to their distinction as follows:
A. ASSIGNED=GREEN
B. UNASSIGNED=ORANGE
C. INCOMPLETE=RED <<--these represent polygons that do not have clave numbers, or that use invalid clave numbers like 402, 401001, etc.
D. ASSIGNED/UNASSIGNED PREVIOUS=BLUE

2. Clave numbers that are ASSIGNED/UNASSIGNED that have more then one property polygon, are to be displayed in BLUE as mentioned in the above list item D. These would appear in the overlay section of the layer list, using the clave number as their name, appended with their order number, and located below the main polygon on the map stack in terms of it\'s order. We need to be able to designate their order from newest to oldest, therefore we\'ll need to use the PREV/NEXT button to cycle through them, and will need to be able to assign an order value to them, along with time/date stamp. Initially, none will have an order number assigned, they they will just display in the order you make them, and over time I will correct them manually, adding their order number, and when possible, their time/date stamp.

3. Display ALL property polygons from gis_properties ala GeoServer on CLAVE page in map stack as as backdrop to item 1(and 2 when applicable), so user can view all the surrounding properties in relation to the property polygon specific for that clave record. Currently loscabos:p map is serving this purpose, but user is unable to mouse-over property polygons to see clave number and owner name. Thus, when user mouses-over the top of these property polygons it needs to display their clave number, owner name, and condominium or subdivision name(if they are part of one). ASSIGNED properties should be displayed as GREEN, and UNASSIGNED properties should display as ORANGE, and INCOMPLETE should be displayed as RED. In this layer, the BLUE polygons should not be displayed.

Note; After setting up the above, we may notice some issues, problems, etc., that may require some things be changed or handled differently. One that comes to mind is; When a single ASSIGNED/UNASSIGNED clave has multiple polygons, which property will be the one initially displayed in GREEN, when at this point we do not know. So this issue, and others like it will need to be worked out as part of this project, so please take note of this.

4. Because will not EDIT any of the polygons that are in shp:gis_properties, we will instead continue to use dmp:map and the existing code you wrote as the means of creating new points and polygons. However, we will need to add functionality that allows us to \'promote\' a polygon from the dmp:map table over to the shp:gis_properties table. Additionally, right now we are only able to add/edit polygons by clicking on the map and adding vertices in this manner, however, we need to also be able to add UTM coordinates and Lat/Lon coordinates to create a new polygon. the reason for this is we receive topographical drawings that contain the property lines in either of these two numerical forms, which of course are exact, and are thus preferred. So in addition to using the mouse to create polygons, we need to be able to create them with text. Below are some examples:

WKT:
GEOMETRY = POLYGON((490604.092548 5459038.062777,490582.682615 5459059.302692,490610.782362 5459087.653579,490632.192296 5459066.423664,490604.092548 5459038.062777))

Google:
Polygon><outerBoundaryIs><LinearRing><coordinates>-123.14169,49.281027,0.0 -123.140811,49.28161,0.0 -123.140279,49.281961,0.0 -123.142049,49.283107,0.0 -123.14298,49.284549,0.0 -123.142488,49.287012,0.0 -123.142594,49.288109,0.0 -123.142944,49.288493,0.0 -123.145712,49.290288,0.0 -123.146314,49.289886,0.0 -123.146253,49.289857,0.0 -123.146192,49.289841,0.0 -123.146134,49.289822,0.0 -123.146077,49.289804,0.0 -123.146039,49.289793,0.0 -123.146005,49.289782,0.0 -123.145933,49.289774,0.0 -123.145879,49.289768,0.0 -123.145809,49.289766,0.0 -123.145676,49.289781,0.0 -123.145595,49.289778,0.0 -123.145576,49.289779,0.0 -123.145785,49.289641,0.0 -123.145393,49.289386,0.0 -123.145852,49.289081,0.0 -123.145754,49.289017,0.0 -123.146613,49.288449,0.0 -123.144943,49.287365,0.0 -123.145455,49.284666,0.0 -123.144284,49.283432,0.0 -123.14208,49.281284,0.0 -123.14169,49.281027,0.0</coordinates></LinearRing></outerBoundaryIs></Polygon>

GeoJSON:
{ \"type\": \"Polygon\",
\"coordinates\": [
[ [100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0] ],
[ [100.2, 0.2], [100.8, 0.2], [100.8, 0.8], [100.2, 0.8], [100.2, 0.2] ]
]
}

GML, GML2, GML3:
<INWATERA_1M.GEOMETRY>
<gml:Polygon srsName=\"EPSG:4326\">
<gml:exterior>
<gml:LinearRing srsName=\"EPSG:4326\">
<gml:coordinates decimal=\".\" cs=\",\"
ts=\"\">119.593002319336,-31.6695003509522 119.595306396484,
31.6650276184082 119.600944519043,-31.6658897399902
119.603385925293,-31.669527053833
119.60050201416,-31.6739158630371
119.595664978027,-31.6728610992432 119.593002319336,
31.6695003509522</gml:coordinates>
</gml:LinearRing>
</gml:exterior>
</gml:Polygon>
</INWATERA_1M.GEOMETRY>

So, I think the best route would be to select the format type in a pull-down menu, and paste the text into a text field, and press submit to create the polygon.


5. Put opacity adjuster for these overlay layers so we can make them solid or transparent or some state in-between. We will decide how their opacity should load by default once we have had an opportunity to see them atop the base maps, each in their respective colors.


6. On the CLAVES page, need to add OpenLayers map stack that allows user to select multiple claves by clicking their polygons on the map. User can also select claves by selecting polygons on other layers like; CONDOMINIUM, SUBDIVISION, and NEIGHBORHOOD polygons, in which case all clave property polygons inside or touching these larger polygons are added to the SEARCH RESULTS list. Again, these selected polygons will then be submitted and will then appear as normal in the SEARCH RESULTS list.

7. At the present time, geospatial edits that are being made to the shp:gis_properties data, are being done on my desktop using an OS X GIS application. As such, the data in shp:gis_properties is subject to constant constant changes, thus, it is important the website is constantly aware of these changes. If I add a new property polygon to a clave number that had an existing polygon, or had multiple existing polygons, then the website needs to handle this correctly.
-------------------------------------------

========================
END OF TASK ITEMS
========================